Open
Bug 264817
Opened 20 years ago
Updated 2 years ago
XML Pretty Printer loses collapsing tree functionality with JavaScript disabled
Categories
(Core :: XML, defect)
Core
XML
Tracking
()
NEW
People
(Reporter: anthony.parsons, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en; rv:1.7.3) Gecko/20040930 Firefox/0.10.1 (Nova-AVIARY: MNG) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en; rv:1.7.3) Gecko/20040930 Firefox/0.10.1 (Nova-AVIARY: MNG) On any XML page shown in the default tree view, the +/- buttons to collapse tags only work when the browser has javascript enabled. Reproducible: Always Steps to Reproduce: 1. Disable Javascript 2. Load an XML file with at least one nested tag pair 3. Try clicking the "-" next to a tag Actual Results: No reaction. Expected Results: The tag's contents should be hidden after clicking, as it does when Javascript is enabled. There are two solutions I can think of here: treat the XML pretty printer as part of the chrome (which would allow scripts to run), or temporarily enable JS while displaying raw XML. I don't know if there's any risk in doing either, am I right in guessing that any <script> tags in the XML would be ignored?
Comment 1•20 years ago
|
||
Confirming with a two day old Seamonkey Linux build. I think this should work regardless of the JavaScript setting, because this is a local feature of our application and not of a remote web-site.
Severity: trivial → normal
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Summary: XML Pretty Printer loses collapsing tree functionality with JS disabled → XML Pretty Printer loses collapsing tree functionality with JavaScript disabled
Depends on: 236839
Comment 2•20 years ago
|
||
*** Bug 290222 has been marked as a duplicate of this bug. ***
Comment 3•18 years ago
|
||
*** Bug 350828 has been marked as a duplicate of this bug. ***
Comment 4•16 years ago
|
||
I'm not sure this legitimately depends on bug 236839, because I can think of several ways for implementing this functionality without XBL and possibly even without JS. Anybody up to take on this bug?
Flags: wanted1.9.0.x?
Comment 5•16 years ago
|
||
Not "wanted" (by release-drivers) in the sense of a prospective blocker that we'll actively champion finding developers for. If a fix ever shows up we'll evaluate risk/reward if someone wants to drive it into the 1.9.0 branch. Your better approach would be to get a fix in a more recent branch first.
Flags: wanted1.9.0.x?
QA Contact: ashshbhatt → xml
Updated•15 years ago
|
Assignee: xml → nobody
Updated•12 years ago
|
Depends on: XBL-scopes
Updated•12 years ago
|
No longer depends on: XBL-scopes
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•