Closed Bug 210783 Opened 22 years ago Closed 22 years ago

xmlns atributes hidden by style sheet, making RDF unreadable

Categories

(Core :: CSS Parsing and Computation, defect)

x86
Linux
defect
Not set
minor

Tracking

()

RESOLVED DUPLICATE of bug 175946

People

(Reporter: gus.heck, Assigned: dbaron)

References

()

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030210 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030210 The style sheet for xml documents seems to be hiding the xmlns attribute. This attribute is extremely important when trying to visually inspect RDF. This is particularly true of rdf such as that in the example where they have defined xmlns a bazillion times. Reproducible: Always Steps to Reproduce: 1. Browse to the above link 2. Be very puzzled 3. View the source and sigh in exasperation Actual Results: No xmlns atributes appear when viewed with the main browser window, but view source reveals them to be present Expected Results: displayed the xmlns attribute like any other. Don't know if I go the component right but you folks should know something about this at least... I'm sure someone decided that there was no usefull information in xmlns when viewing xml and decided to pretty things up by dropping it. But this assumption assumes that the xml has sensible qnames, that have natural language meaning enough to understand or recognize them. I suspect that the example is machine generated however, and so all useful information is in the xmlns not the qname. (in this case every single name space is ns0: --- hardly enlightening) As RDF, generated RDF and generated xml of other sorts is likely to increase, I suggest that no attributes of any sort should be hidden exept perhaps on an alternate style sheet. If someone is viewing xml as collapsable trees they want to see what the xml says :)
*** This bug has been marked as a duplicate of 175946 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.