Closed
Bug 71523
Opened 24 years ago
Closed 21 years ago
The frame's x,y location should be adjusted to fall on a pixel boundary
Categories
(Core :: Layout, defect, P1)
Core
Layout
Tracking
()
RESOLVED
INVALID
Future
People
(Reporter: kmcclusk, Assigned: attinasi)
References
(Blocks 1 open bug)
Details
In the process of converting from twips to pixel's we are sometimes off by one pixel because of roundoff error. This results in calls to invalidate the frame's rect which are sometimes 1 pixel too narrow. It may make sense to condition the location of a frame so it's twip coordinates coorespond to pixel boundary. The problem is the x,y coorindate may contain a twip value that is a fraction of a pixel. When the width of the frame is added to the x coordinate the number of pixels will vary depending on the x corrdinate's sub-pixel twip coordinate.
Comment 2•23 years ago
|
||
This bug was split off of bug 63951 so that a hacky fix could be applied to that bug.
Reporter | ||
Updated•23 years ago
|
Target Milestone: --- → mozilla0.9.8
Reporter | ||
Updated•23 years ago
|
Target Milestone: mozilla0.9.8 → mozilla1.0.1
Assignee | ||
Comment 3•23 years ago
|
||
Moving Mozilla 1.01 bugs to 'future' milestone with priority P1 I will be pulling bugs from 'future' milestones when scheduling later work.
Priority: -- → P1
Target Milestone: mozilla1.0.1 → Future
No, but I disagree with the proposed solution. The real solution is for Invalidate to round out the app-units-rect when converting to pixels.
therefore, marking INVALID
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•