Open Bug 219561 Opened 21 years ago Updated 2 years ago

going back/forward to unstyled xml pages adds a "black"/corrupted area at the bottom of the display area

Categories

(Core :: XML, defect)

defect

Tracking

()

People

(Reporter: sekundes, Unassigned)

References

()

Details

Attachments

(1 file)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20030916 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20030916 the lower part of unstyled xml page is blacken while go back to that page. It displays normally after scrolling the scrollbar. Reproducible: Always Steps to Reproduce: 1.open unstyled xml pages. 2.scroll down the scrollbar to the bottom of the page. 3.go to another website. 4.go back to the unstyled xml page. Actual Results: The lower part of unstyled xml page is blacken. Expected Results: the unstyled xml page should be displayed normally.(no black screen)
Reproducible on 1.5 RC1, Windows Server 2003
yes, I also produced on 1.5 RC1, should be fixed before 1.5 is released. P.S. I don't have permission to mark as NEW.
the xml style does not work properly under this page: http://xstandard.com/xml.asp?id=700AAD69-9450-4E84-982E-1EEBA8116735 in 1.5 RC1 too.
Reproducible on 1.6a, Windows 2000
still reproducible on 1.7a, owner mark to NEW please
Severity: normal → major
Flags: blocking1.6?
[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.6b) Gecko/20031208] (W98SE) Confirmed, going back/forward between <http://forums.mozillazine.org/rdf.php> and <http://www.mozilla.org/>. 1) Actually, it's not the page content itself which goes "black": The end of the page is still displayed correctly; But the display area itself has an extra black area at its bottom. (I'll attach a picture) 2) It can also happen if near but not at the very end of the page. 3) It does not always go "black": sometimes it simply leaves some (possibly corrupted) part of the other page (when playing with tabs !?)... Updating: *(S) Major -> Minor, (easy workaround) *(S) Unconfirmed -> New
Severity: major → minor
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: black screen is shown while go back to unstyled xml pages → going back to unstyled xml pages adds a "black"/corrupted area at the bottom of the display area
Going _forward_ in new window, too.
Summary: going back to unstyled xml pages adds a "black"/corrupted area at the bottom of the display area → going back/forward to unstyled xml pages adds a "black"/corrupted area at the bottom of the display area
Re comment 5: Could this bug have been solved by bug 225854 fix ? Can you check with a v1.7a after 20040107 ? (you didn't say which one you tested) (Can someone check a v1.6branch (after 20040107) too ?)
The build I tested is Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7a) Gecko/20040108 I don't think it is fixed.
Thanks for the confirmation: bug still there. One can do the back/forward with <about:blank> too :-) (This bug might belong to Layout (or GFX) rather than XML ??) Could anyone check a non-Windows build ? Re comment 7: That page does not show the "black"/corrupted bug: Please, file a different bug for the style issue.
Component: XML → Layout
Argh :-( Restoring 'XML' Component; and the other URL/bug is in comment 3, not 7.
Component: Layout → XML
Also happens on Mac OS X (2004011005-trunk and 2004011009-1.6).
OS: Windows 2000 → All
Hardware: PC → All
Re #11: okay, that bug has been filed to http://bugzilla.mozilla.org/show_bug.cgi?id=230660
I filed comment 3 as bug 230811. I suspect the problem is that the scroll position is being restored incorrectly due to the really weird loading process I described in bug 198506 comment 22.
Component: XML → Layout
too late for 1.6. going to have to get this for 1.7
Flags: blocking1.7a+
Flags: blocking1.6?
Flags: blocking1.6-
heikki, any cycles to work on this or thoughts on who might be able to pick it up?
Flags: blocking1.7b?
Flags: blocking1.7a-
Flags: blocking1.7a+
Sorry, I don't have time for this right now. I'm giving this to Jonas for now. I took a brief look in DOM Inspector, and something strange seems to be going on. After the output from the XSLT transformation we have a *copy of the original* document in the DOM. The root of the XSLT transformed document is html:div, and it's new strange sibling is html:span, which contains a copy of the original XML document. It seems like there is some additional weirdness going on with the document in comment #3 - the transformed document is missing most of its style.
Assignee: hjtoi-bugzilla → bugmail
not going to block the release on this.
Flags: blocking1.7b? → blocking1.7b-
Flags: blocking1.8a?
The fact that we have the original dom retained was one of the designgoals of xmlprettyprinting. We don't want to change the dom since someone could have been loading the document just to get data from it using script. What prettyprinting does is to insert anonymous XBL content that displays the prettyprint, which is what you see in the DOM-Inpspector. If you configure the dominspector to not show anonymous content it'll become very clear what's happening.
Flags: blocking1.8a?
Flags: blocking1.8a-
Flags: blocking1.7a-
Flags: blocking1.6-
QA Contact: ashshbhatt → xml
Severity: minor → S4

The bug assignee is inactive on Bugzilla, so the assignee is being reset.

Assignee: jonas → nobody
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: