287
edits
XUL:Priority List: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 22: | Line 22: | ||
|Editable treecells that allow editing via a textbox or a menulist. Fairly easy to implement for non-RDF trees, except for the caret being hidden when a view is above it issue.|| | |Editable treecells that allow editing via a textbox or a menulist. Fairly easy to implement for non-RDF trees, except for the caret being hidden when a view is above it issue.|| | ||
|- | |- | ||
| | |Allow the toolkit bindings to have extra privileges in some way such that native calls and dtd handling will work when the elements are used in remote XUL. (AxelHecht) We need a good story here. There is the story that we can't/won't do a chrome registry for remote xul, that is, no fiddling of locales into URLs. Which may actually be a wise idea. Then you need to do some serverside processing to spin the DTD url into your content, which ends up in you being able to serve the DTD inline as well. But we need to iron this out, probably with a counter proposal to actually do URL munging for remote xul.|| | ||
|- | |- | ||
|There needs to be a way of parsing XUL documents and fragments. DOMParser only parses XML. (NeilRashbrook) HTML parsing, too. Currently the best you can do is document.write() (AxelHecht) We need to check for DOM LS, jst, what's the status with that?|| | |There needs to be a way of parsing XUL documents and fragments. DOMParser only parses XML. (NeilRashbrook) HTML parsing, too. Currently the best you can do is document.write() (AxelHecht) We need to check for DOM LS, jst, what's the status with that?|| | ||