diff --git a/docs/_includes/getting-started/browser-device-support.html b/docs/_includes/getting-started/browser-device-support.html index b5a2d892d2..b27099aa60 100644 --- a/docs/_includes/getting-started/browser-device-support.html +++ b/docs/_includes/getting-started/browser-device-support.html @@ -164,6 +164,9 @@ if (navigator.userAgent.match(/IEMobile\/10\.0/)) {
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.
+:hover
/:focus
on mobileEven though real hovering isn't possible on most touchscreens, most mobile browsers emulate hovering support and make :hover
"sticky". In other words, :hover
styles start applying after tapping an element and only stop applying after the user taps some other element. This can cause Bootstrap's :hover
states to become unwantedly "stuck" on such browsers. Some mobile browsers also make :focus
similarly sticky. There is currently no simple workaround for these issues other than removing such styles entirely.
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:
diff --git a/docs/_includes/nav/getting-started.html b/docs/_includes/nav/getting-started.html index b06dcce9b2..4a07fe79c7 100644 --- a/docs/_includes/nav/getting-started.html +++ b/docs/_includes/nav/getting-started.html @@ -56,6 +56,7 @@