reporter: please attach a picture, thanks.
Don't need a picture - this is a longstanding bug in layout. My guess is, the twips-to-pixels calculation is occasionally off by one pixel, leaving the "crack" in the buttons where the background image is not painted. This can also be seen in the scrollbar thumbs in modern.
BTW, I am getting this behavior in 16 and 32 bit color 800x600 resolution, and my desktop has 15x15 twips per pixel.
*** Bug 81445 has been marked as a duplicate of this bug. ***
*** Bug 81474 has been marked as a duplicate of this bug. ***
*** Bug 81459 has been marked as a duplicate of this bug. ***
Keywording. Should this be -> Skinability?
Nominating for moz0.9.1
I haven't seen this problem in a while. Has anyone else?
yes, it's still there
Where is it happening now? I may need to update the testcase.
Reassigning to savulov and moving to m0.9.3. Alex, I suspect that Hewitt's comments on 5/7/1 may be right. I have seen cases where blocks do not size frames on even pixel boundaries.
scrollbar thumb's rounding error is bug 56876.
I see the pixel cracks in spell check on new modern on todays branch build Win32 2001-07-23-06 0.9.2. They show on the right side of the "Ignore All", "Edit" and "Close" buttons
July23 commercial branch 0.9.2: Search Mail/News Messages has the problem in one of the criteria dropdowns.
On Linux 2001-07-24-05 0.9.2 Branch in New Modern, I also see this in the knock knockdialogs "block" button for IM
moving to 0.9.4
Where is the twips-to-pixels calculation being done? I'd like to see if there is some obvious error in the algorithm somewhere.
*** Bug 89426 has been marked as a duplicate of this bug. ***
pushing to 0.9.5
*** Bug 98390 has been marked as a duplicate of this bug. ***
removed target milestone
*** Bug 106367 has been marked as a duplicate of this bug. ***
Is this related to bug #80530? <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=80530">80530</a>
WFM (buildID: 2002072204). Could we close this one now ? /jc
WFM 2002072608 on Win2k. Reporter: Are you still seeing this bug?
See comment 11 for my experience.
WFM. Resolving so.