Closed
Bug 538402
Opened 15 years ago
Closed 13 years ago
'@media print' is ignored when '@media screen' present
Categories
(Core :: Printing: Output, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: list-jcr, Unassigned)
Details
(Whiteboard: [closeme 2011-06-19])
User-Agent: Mozilla/5.0 (X11; U; OpenBSD i386; en-US; rv:1.9.1.3) Gecko/20091113 whatever Build Identifier: 3.5.3 With or without the 'only' keyword, if '@media screen' defines a font via 'font-family' css, that font is used when printing regardless if there is another font defined by '@media print' Reproducible: Always Steps to Reproduce: put the following in profile_dir/chrome/userContent.css or within an included CSS file, or within 'STYLE' tags of an HTML page. ****************************************************** @media only screen { * { font-family: "terminus" !important; } } @media only print { * { font-family: "courier" !important; { } ****************************************************** Of course, the fonts names will need to be modified to whatever you happen to have installed. Actual Results: If you print the page, it is printed with the font defined in the '@media screen' style rather than the '@media print' style. Expected Results: The printed page should use the font defined in the '@media print' style.
Comment 1•13 years ago
|
||
reporter, does this still fail when using Firefox 5 *beta* http://www.mozilla.com/en-US/firefox/channel/ or Firefox 4?
Whiteboard: [closeme 2011-06-19]
Wane, I'm unable to test Firefox 4 or 5 beta since they haven't been ported to OpenBSD. The steps to reproduce should suffice to show the problem if you're able to run the newer versions.
Comment 3•13 years ago
|
||
There's a syntax error in the print rule, the 2nd "{" should be "}". Also, there's no keyword "only" allowed after @media as far as I can tell: http://www.w3.org/TR/CSS2/media.html With those corrections it seems to work fine for me, in 3.5, 3.6 and 5.0 on Linux.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•