Closed Bug 286831 Opened 20 years ago Closed 20 years ago

XML Style Treeview(for stylesheet-less xml documents) degenerates into unoragnized block text when mousescrolled

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
minor

Tracking

()

VERIFIED DUPLICATE of bug 215762

People

(Reporter: chs_peanut, Assigned: bugzilla)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1

When viewing an xml file, (i've only tested this on XML files that "This XML
file does not appear to have any style information associated with it. The
document tree is shown below.", when i attempt to scroll via mouse(i'm on a
thinkpad, so its the middle mouse button scroll), the xml tree displayed
instantly becomes a unformated clump of text; (text-nodes remain, xml tags
diappear), and the text-node tokens are only broken up by whatever spaces were
included in the original xml, and its all on one change wrapping line of text.
(the xml tree organization suddenly seems to become a bunch of tokens broken up
by spaces, not newlines or anything else.
refreshing the page un-garbles the text again. this problem was NOT observed
with scrollbars.

Reproducible: Always

Steps to Reproduce:
1.open an xml file with no style information.
2.mousescroll up or down(ITS ONLY MOUSE SCROLL, not the scrollbars - it works
fine when scrollbars ar used.


Actual Results:  
the text appeared garbled.
  all the xml tags vanished, and only the xml text-nodes remained, concatenated
together on a giant, wrapping line of text.

Expected Results:  
the xml display should not have vanished; the page should behave as it would
have if i used the scrollbars on the window instead of the mouse, to scroll.

*** This bug has been marked as a duplicate of 215762 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.