Closed
Bug 279881
Opened 20 years ago
Closed 16 years ago
Graphics become split-up and displayed on several pages in print
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 146799
People
(Reporter: Thomas.Juergensen, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a6) Gecko/20050111
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a6) Gecko/20050111
When printing the document, graphics are partially split into two parts, each
part being printed on a separate page.
This function will ensure that the grapich is printed completely; however it
becomes very hard to read the printed text if the grapic is splitted up.
It would be good if one could in some way customize that (at least for a given
page) no graphics should be splitted up. If it were too big to fit on a page,
the page output should be stopped there and the graphic and text should then be
printed on a new page instead.
See for example http://www.yomiuri.co.jp/igo_e/201.htm, diagram 2.
Reproducible: Always
Steps to Reproduce:
1. Open http://www.yomiuri.co.jp/igo_e/201.htm
2. Print the document on any printer (have tested 5 different ones)
3. Check printout
Actual Results:
Printout contains such graphics as diagram 2 which start on page 1 and will be
continued on page 2.
Expected Results:
Desirable here would be to start at the place where diagram 2 appears on page 2
Updated•20 years ago
|
Assignee: general → nobody
Component: General → Layout
Product: Mozilla Application Suite → Core
QA Contact: general → layout
Summary: Grapics become split-up and displayed on several pages in print → Graphics become split-up and displayed on several pages in print
Version: unspecified → Trunk
Comment 1•20 years ago
|
||
I think we have bugs on this already... we need a smarter image-splitting algorithm.
I'm pretty sure we don't have bugs on exposing UI for changing the algorithm on
the fly, if only because I have a hard time most users would make any sense of
that UI.
Whiteboard: DUPEME
Comment 2•19 years ago
|
||
This is an automated message, with ID "auto-resolve01".
This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.
While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.
If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.
The latest beta releases can be obtained from:
Firefox: http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 3•17 years ago
|
||
(In reply to comment #1)
> I think we have bugs on this already... we need a smarter image-splitting
> algorithm.
bz, after much effort i am unable to find such a bug. do you recall any specifics beyond "image-splitting"?
dupe candidates: (I didn't examine them all)
Bug 214305 – printing of large images produces wrong results
Bug 315694 – Printing cut/split pictures on several pages
Bug 362260 – missing and misplaced graphics (images) on multiple page printout
how do the following fit in, if at all?
Bug 384792 – Inline images no longer split when printing (WONTFIX)
Bug 254276 – XUL documents always printed on one page
Bug 146799 – Images could be printed incorrectly; images are split across pages (WONTFIX)
Comment 5•17 years ago
|
||
bug 146799 might be what I was thinking.... Or bug 214305. Not really sure.
Updated•16 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•