From f0d8894d54afbd10b43a0919383b35fdbf961b51 Mon Sep 17 00:00:00 2001 From: Chris Rebert Date: Mon, 3 Nov 2014 10:56:30 -0800 Subject: Add #14868 to the compatibility docs --- docs/_includes/getting-started/browser-device-support.html | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) (limited to 'docs/_includes/getting-started/browser-device-support.html') diff --git a/docs/_includes/getting-started/browser-device-support.html b/docs/_includes/getting-started/browser-device-support.html index a0b5ef367..fd66f54b4 100644 --- a/docs/_includes/getting-started/browser-device-support.html +++ b/docs/_includes/getting-started/browser-device-support.html @@ -165,13 +165,22 @@ if (navigator.userAgent.match(/IEMobile\/10\.0/)) {

Browser zooming

Page zooming inevitably presents rendering artifacts in some components, both in Bootstrap and the rest of the web. Depending on the issue, we may be able to fix it (search first and then open an issue if need be). However, we tend to ignore these as they often have no direct solution other than hacky workarounds.

-

Printer viewports

-

Even in some modern browsers, printing can be quirky. In particular, as of Chrome v32 and regardless of margin settings, Chrome uses a viewport width significantly narrower than the physical paper size when resolving media queries while printing a webpage. This can result in Bootstrap's extra-small grid being unexpectedly activated when printing. See #12078 for some details. Suggested workarounds:

+

Printing

+

Even in some modern browsers, printing can be quirky.

+

In particular, as of Chrome v32 and regardless of margin settings, Chrome uses a viewport width significantly narrower than the physical paper size when resolving media queries while printing a webpage. This can result in Bootstrap's extra-small grid being unexpectedly activated when printing. See #12078 for some details. Suggested workarounds:

+

Also, as of Safari v8.0, fixed-width .containers can cause Safari to use an unusually small font size when printing. See #14868 for more details. One potential workaround for this is adding the following CSS:

+ {% highlight css %} +@media print { + .container { + width: auto; + } +} + {% endhighlight %}

Android stock browser

Out of the box, Android 4.1 (and even some newer releases apparently) ship with the Browser app as the default web browser of choice (as opposed to Chrome). Unfortunately, the Browser app has lots of bugs and inconsistencies with CSS in general.

-- cgit v1.2.3 From c513f58c6a2e345da338aebe45ee422b07260017 Mon Sep 17 00:00:00 2001 From: Chris Rebert Date: Mon, 10 Nov 2014 13:14:33 -0800 Subject: Remove X-UA-Compatible caveat from Validators docs Refs #15072 --- docs/_includes/getting-started/browser-device-support.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/_includes/getting-started/browser-device-support.html') diff --git a/docs/_includes/getting-started/browser-device-support.html b/docs/_includes/getting-started/browser-device-support.html index fd66f54b4..306023d7b 100644 --- a/docs/_includes/getting-started/browser-device-support.html +++ b/docs/_includes/getting-started/browser-device-support.html @@ -202,5 +202,5 @@ $(function () {

Validators

In order to provide the best possible experience to old and buggy browsers, Bootstrap uses CSS browser hacks in several places to target special CSS to certain browser versions in order to work around bugs in the browsers themselves. These hacks understandably cause CSS validators to complain that they are invalid. In a couple places, we also use bleeding-edge CSS features that aren't yet fully standardized, but these are used purely for progressive enhancement.

These validation warnings don't matter in practice since the non-hacky portion of our CSS does fully validate and the hacky portions don't interfere with the proper functioning of the non-hacky portion, hence why we deliberately ignore these particular warnings.

-

Our HTML docs likewise have some trivial and inconsequential HTML validation warnings due to our inclusion of X-UA-Compatible <meta> tags to avoid Internet Explorer issues and our inclusion of a workaround for a certain Firefox bug.

+

Our HTML docs likewise have some trivial and inconsequential HTML validation warnings due to our inclusion of a workaround for a certain Firefox bug.

-- cgit v1.2.3 From 9391ef207ff05f28e3952afdb92639c02b5920f5 Mon Sep 17 00:00:00 2001 From: "Patrick H. Lauke" Date: Tue, 11 Nov 2014 22:41:21 +0000 Subject: aria-hidden added to some stray glyphicons plus minor tweak to customizer's generated alerts --- .../getting-started/browser-device-support.html | 46 +++++++++++----------- 1 file changed, 23 insertions(+), 23 deletions(-) (limited to 'docs/_includes/getting-started/browser-device-support.html') diff --git a/docs/_includes/getting-started/browser-device-support.html b/docs/_includes/getting-started/browser-device-support.html index 306023d7b..2f3802b84 100644 --- a/docs/_includes/getting-started/browser-device-support.html +++ b/docs/_includes/getting-started/browser-device-support.html @@ -19,33 +19,33 @@ Android - Supported - Supported + Supported + Supported N/A - Not Supported + Not Supported N/A iOS - Supported + Supported N/A - Not Supported - Supported + Not Supported + Supported Mac OS X - Supported - Supported - Supported - Supported + Supported + Supported + Supported + Supported Windows - Supported - Supported - Supported - Supported - Not Supported + Supported + Supported + Supported + Supported + Not Supported @@ -67,26 +67,26 @@ border-radius - Not supported - Supported + Not supported + Supported box-shadow - Not supported - Supported + Not supported + Supported transform - Not supported - Supported, with -ms prefix + Not supported + Supported, with -ms prefix transition - Not supported + Not supported placeholder - Not supported + Not supported -- cgit v1.2.3