Closed
Bug 23985
Opened 25 years ago
Closed 24 years ago
stopping quickly can result in unpainted scrollbars
Categories
(Core :: XUL, defect, P3)
Core
XUL
Tracking
()
VERIFIED
WORKSFORME
People
(Reporter: cmaximus, Assigned: eric)
Details
Attachments
(1 file)
29.30 KB,
image/gif
|
Details |
Overview Description: It is possible to stop the browser qickly enough such that the scrollbars begin to paint but not completely so. The scroll arrows and the little hash marks on the scroll thumb don't always show up. Steps to Reproduce: 1) Load any page that take more than a split second to reload. 2) Click reoad. 3) Immediately click stop. Actual Results: The page begins to reload in blazing fashion but when stopped all of the chrome is not there. The little images that make the complete scrollbars aren't all there. Expected Results: You shouldn't be able to catch the scrollbars mid-stream like that. The functionality is still there but it doesn't look good. Build Date & Platform info: This bug is XP and was reproduced on Mac & Linux builds from 20000113. Additional Information: I understand the chrome as content idea in the Brave New XUL World, but we should really be able to avoid glitche slike this and make it appear seamless.
Reporter | ||
Comment 1•25 years ago
|
||
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M16
Assignee | ||
Comment 2•25 years ago
|
||
targeting
Assignee | ||
Updated•24 years ago
|
Target Milestone: M16 → M17
Comment 4•24 years ago
|
||
spam, open xptoolkit qa contact moving over to jrgm
QA Contact: paulmac → jrgm
Comment 5•24 years ago
|
||
mass-moving all bugs to m21 that are not dofood+, or nsbeta2+
Target Milestone: M18 → M21
Comment 6•24 years ago
|
||
can't reproduce this on mac/linux/win32 for 20000626nn builds. Marking WFM. (But claudius knows what to do if ...)
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Comment 7•24 years ago
|
||
verified (and throws down the gauntlet to CMax).
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•