From 69523b1e041f98986d1868e57040bff9dc43c8f9 Mon Sep 17 00:00:00 2001 From: Chris Rebert Date: Wed, 20 Jan 2016 18:25:57 -0800 Subject: [PATCH] Restore workarounds for #12078 printing bug that were lost in 86af1f3 Refs #18984 [skip sauce] --- docs/getting-started/browsers-devices.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/getting-started/browsers-devices.md b/docs/getting-started/browsers-devices.md index edb0a738fc..ca38658dd7 100644 --- a/docs/getting-started/browsers-devices.md +++ b/docs/getting-started/browsers-devices.md @@ -220,6 +220,10 @@ 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.](https://github.com/twbs/bootstrap/issues/12078) Suggested workarounds: +* Embrace the extra-small grid and make sure your page looks acceptable under it. +* Customize the value of the `$grid-breakpoints` Sass variable so that your printer paper is considered larger than extra-small. +* Add custom media queries to change the grid size breakpoints for print media only. + 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 %} -- 2.47.2