Closed
Bug 476841
Opened 17 years ago
Closed 16 years ago
Zooming in Print Preview doesn't affect text, with <frameset>
Categories
(Core :: Print Preview, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: hidenosuke, Unassigned)
References
()
Details
(Keywords: fixed1.9.1, testcase)
Attachments
(3 files, 1 obsolete file)
Steps to reproduce:
1. Open above 'URL'
2. File -> Print Preview
3. Zoom by ctrl + mouse wheel in Print Preview
Actual result:
The layout of Print Preview corrupts.
Expected result:
The layout of Print Preview doesn't corrupt.
Zoom function might not have to work in Print Preview.
The original report in Japanese is http://bugzilla.mozilla.gr.jp/show_bug.cgi?id=6025 .
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2a1pre) Gecko/20090204 Minefield/3.2a1pre
Comment 1•17 years ago
|
||
Confirmed that this is broken, though I don't exactly see "corruption" per se -- instead, I see the following behavior:
(a) the graphics, page-margins, and page-headers zoom correctly
(b) the text doesn't zoom at all -- font-size stays constant
(c) the text hardly moves at all (the little that it does move is probably just due to the page margins growing and moving the page content frame a bit).
(b) and (c) are incorrect / unexpected behavior.
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2a1pre) Gecko/20090202 Minefield/3.2a1pre
Updated•17 years ago
|
Version: unspecified → Trunk
Comment 2•17 years ago
|
||
(Hideo, please comment if you're seeing a different kind of broken behavior than what I described in Comment 1)
Summary: Zooming by ctrl + mouse wheel in Print Preview causes layout corruption. → Zooming in Print Preview doesn't affect text, with <frameset>
Comment 3•17 years ago
|
||
Simplifying URL slightly. (I can reproduce this with just one <frame> -- it's not necessary to have two.)
Comment 4•17 years ago
|
||
Comment 5•17 years ago
|
||
Attachment #360494 -
Attachment is obsolete: true
Updated•17 years ago
|
Attachment #360494 -
Attachment description: testcase 1 → (broken testcase -- ignore)
Comment 6•17 years ago
|
||
This is probably the same underlying problem as bug 444448. Marking as dependency for now.
Depends on: 444448
Reporter | ||
Comment 7•17 years ago
|
||
Please use this test case.
Reporter | ||
Comment 8•17 years ago
|
||
Reporter | ||
Comment 9•17 years ago
|
||
(In reply to comment #2)
> (Hideo, please comment if you're seeing a different kind of broken behavior
> than what I described in Comment 1)
I am sorry the first test case is wrong.
Please see comment 7 and comment 8.
Comment 10•17 years ago
|
||
(In reply to comment #7)
> Please use this test case.
(FWIW, testcase 1 / attachment 360495 [details] is simpler)
(In reply to comment #8)
> Screen shot for attachment 360496 [details].
Thanks for that -- that's consistent with what I'm seeing.
Comment 11•17 years ago
|
||
Bug 425265 comment 15 indicates that that bug's patch may fix this, once it's ready. Woo-hoo!
Updated•16 years ago
|
Updated•16 years ago
|
Keywords: fixed1.9.1
You need to log in
before you can comment on or make changes to this bug.
Description
•