[Webkit-unassigned] [Bug 56263] XML Viewer: extensions can't render original XML

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Apr 1 19:05:37 PDT 2011


https://bugs.webkit.org/show_bug.cgi?id=56263





--- Comment #31 from alan.stroop at gmail.com  2011-04-01 19:05:37 PST ---
While doing some preliminary work to prepare my extension for when this new functionality makes it to the browsers, I noticed a couple of issues:

When the source xml contains a CDATA section, it gets rendered as a comment.  The "<![CDATA[...]]>" gets changed to "<!--[CDATA[...]]-->". When  extensions attempt to process the source xml in the webkit-xml-viewer-source-xml DIV, this change has already occurred. I suppose they could look for this specific type of comment and drop !-- and -- then apply their normal CDATA rendering.

Another issue I'm seeing is that regardless of the source xml's element/attribute name capitalization, I cannot seem to get it to stick. If I serialize the document to a string, the element/attribute names all get lowercased. If I replace the original document with the contents of webkit-xml-viewer-source-xml DIV and attempt to render it, the element names are UPPERCASED, attribute names are lowercased. If I serialize the replaced document, they are lowercased. For example, the source element <RooT/> will either come out as <root/> when serialized or <ROOT/> when the document is replaced. I don't encounter either of these capitalization issues in my extension in Chrome 10, which doesn't include the native webkit xml rendering, when I serialize or replace a document.

I'll attach a test HTML file that shows the CDATA and lowercasing issue and also a screenshot of how my extension renders the xml when the original document is replaced with the content of the webkit-xml-viewer-source-xml DIV.

I'm assuming the attached test HTML will be similar as far as markup is concerned as to what to extensions can expect to work with after the native webkit rendering is done. If I'm off track anywhere, let me know.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list