Closed
Bug 270658
Opened 20 years ago
Closed 17 years ago
freeze XSLT if xhtml namespace in script element
Categories
(Core :: XML, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: pascal, Unassigned)
References
Details
Attachments
(3 files, 1 obsolete file)
User-Agent: Mozilla/5.0 (X11; U; Linux alpha; en-GB; rv:1.7.3) Gecko/20040919 Build Identifier: The 3 attachemens are ment as a proof of concept. If you remove the namespace in script.xml Firefox won't crash. Reproducible: Always Steps to Reproduce: 1) download the 3 files in a single directory 2) open a.xml 3) FREEZE
Reporter | ||
Comment 1•20 years ago
|
||
Reporter | ||
Comment 2•20 years ago
|
||
Reporter | ||
Comment 3•20 years ago
|
||
Attachment #166358 -
Attachment mime type: application/xsl → text/xml
Component: General → XSLT
Product: Firefox → Core
Version: unspecified → 1.0 Branch
Actually, I don't think this is xslt related. It's probably because we're unable to deal with having <script> elements in the root of the document. nsHTMLScriptElement::MaybeProcessScript just bails if GetParent() returns null, which means that we'll never call ProcessScriptElement and no ScriptAvailable/ScriptEvaluated notification will go out to unblock the parser. We should probably change !GetParent() to !(GetParent() || GetCurrentDoc()->GetRootContent() == this) same thing in nsSVGScriptElement.
Assignee: firefox → core.xml
Component: XSLT → XML
QA Contact: firefox.general → ashshbhatt
Version: 1.0 Branch → Trunk
cc'ing some people that might have time to look at this
Comment 6•20 years ago
|
||
Note the patch in bug 88309 -- this has some content sink changes too, though I can't tell why they're needed, exactly.
Reporter | ||
Comment 7•19 years ago
|
||
For some reason a.xml is no longer available...
Reporter | ||
Comment 8•19 years ago
|
||
Attachment #166357 -
Attachment is obsolete: true
Reporter | ||
Comment 9•19 years ago
|
||
Firefox 1.0.6 still freezes...
Reporter | ||
Comment 10•17 years ago
|
||
Firefox 2.0 still freezes...
Comment 11•17 years ago
|
||
Pascal - there's nothing in this bug to indicate that it would have been fixed, so please follow the etiquette guidelines prior to posting in the future. https://bugzilla.mozilla.org/page.cgi?id=etiquette.html Also, none of the testcases above freeze me using a current win32 trunk build, so this is either Linux-only or fixed for Fx3. Can any Linux trunk users confirm?
Reporter | ||
Comment 12•17 years ago
|
||
Hello Ryan VanderMeulen, The Firefox shipped with both the latest Ubuntu and the latest OpenSUSE freeze. I just checked 2.0 RC3 to be sure and the results are the same. Is there something I can do to provide more information?
Comment 13•17 years ago
|
||
Like I said, try testing with a current trunk build (what's leading up to Fx3).
Reporter | ||
Comment 14•17 years ago
|
||
Ah, so Fx3 means Firefox 3. Those abbrevations always drive me nuts. Yes it is Fixed in "2007-02-04-04-trunk"! :) Thank you for the help.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Updated•17 years ago
|
Resolution: FIXED → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•