Open
Bug 514629
Opened 16 years ago
Updated 3 years ago
Setting "Page Style" to "No Style" in View menu has no effect on print / print preview
Categories
(Core :: Printing: Output, defect)
Core
Printing: Output
Tracking
()
NEW
People
(Reporter: mitsugu.oyama, Unassigned)
References
()
Details
Attachments
(4 files)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.3a1pre) Gecko/20090903 Minefield/3.7a1pre
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.3a1pre) Gecko/20090903 Minefield/3.7a1pre
CSS is effective at Print Preview though [View]-[Page Style]-[No Style] has been selected.
Reproducible: Always
Steps to Reproduce:
1.Open an arbitrary topic of an arbitrary forum of Ubuntu Japanese Team. (ex. https://forums.ubuntulinux.jp/viewtopic.php?id=5703 )
2.Select [View]-[Page Style]-[No Style].
3.Select [File]-[Print Preview].
Actual Results:
CSS is effective at Print Preview.
Expected Results:
CSS is not effective at Print Preview.
Problem on web site:
Web site is Invalid in DTD though is declared as xhtml1.0 Strict.
| Reporter | ||
Comment 1•16 years ago
|
||
| Reporter | ||
Comment 2•16 years ago
|
||
| Reporter | ||
Comment 3•16 years ago
|
||
| Reporter | ||
Comment 4•16 years ago
|
||
| Reporter | ||
Comment 5•16 years ago
|
||
- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.3a1pre) Gecko/20090903 Minefield/3.7a1pre
- Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.3a1pre)
Gecko/20090903 Minefield/3.7a1pre
+ User-Agent:
+ Mozilla/5.0 (X11; U; Linux i686; ja; rv:1.9.0.13) Gecko/2009073021 Firefox/3.0.13
+ Mozilla/5.0 (X11; U; Linux i686; ja; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2
+ Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2a2pre) Gecko/20090903 Namoroka/3.6a2pre
+ Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.3a1pre) Gecko/20090903 Minefield/3.7a1pre
Component: General → Print Preview
Product: Firefox → Core
QA Contact: general → printing
Version: unspecified → Trunk
Comment 6•15 years ago
|
||
I can confirm the issue as reported (on FF4.0.1 WinXP) but unsure on what is the wanted behaviour, need UX or module owner input. Also debatable whether this is a bug or a feature request.
Maybe a better summary would be:
"Changing page style to No Style doesn't affect print preview or printing"
or
"[RFE] Changing page style to No Style should affect print preview & printing"
From my testing on a Bugzilla bug page (where 2 page styles are defined), changing to a different page style does affect print preview, but changing to No Style will mean print preview will show the last selected page style.
Based on the fact that changing page styles affects print preview, a user's choice of style is honoured for printing. Therefore I believe this is a bug because when the user chooses No Style, it is not honoured for printing.
| Reporter | ||
Comment 7•15 years ago
|
||
I think this is a bug, too.
When many people see the word "No style", they will instantaneously think that CSS doesn't apply.
I think better summery would be "Changing page style to No Style doesn't affect print preview or printing".
Comment 8•15 years ago
|
||
(In reply to comment #7)
> I think better summery would be "Changing page style to No Style doesn't affect
> print preview or printing".
Updating summary to something like that, & confirming in my nightly.
Mozilla/5.0 (X11; Linux i686; rv:6.0a1) Gecko/20110501 Firefox/6.0a1
This affects printed output, too -- not just print preview.
Also: This is special to "No Style" -- the other options in the menu[1] _do_ seem to be accurately reflected in printed output.
[1] on pages where there are multiple options, e.g. Classic vs Dusk on this bugzilla page
Status: UNCONFIRMED → NEW
Component: Print Preview → Printing: Output
Ever confirmed: true
OS: Linux → All
Hardware: x86 → All
Summary: CSS is effective at Print Preview though [View]-[Page Style]-[No Style] has been selected. → Setting "Page Style" to "No Style" in View menu has no effect on print / print preview
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•