XUL:Priority List: Difference between revisions

XUL:Priority List (view source)

Revision as of 15:05, 21 August 2005

128 bytes removed , 21 August 2005

no edit summary

Enn

287

edits

@@ Line 6: / Line 6: @@
 {| border="1" cellpadding="6" valign="top"
-|a CanvasTag for customized drawing is needed. The HTML canvas is available so this pretty much done. (Enn) I still think a non-retained version would be useful though.||
+|A CanvasTag for customized drawing is needed. The HTML canvas is available so this pretty much done. (Enn) I still think a non-retained version would be useful though.||
 |-
-|templates need to log syntax errors on the JS console or elsewhere.||
+|Templates need to log syntax errors on the JS console or elsewhere.||
 |-
-| templates should have a means of matching values based on substrings, greater than a value, etc. || [https://bugzilla.mozilla.org/show_bug.cgi?id=285631 285631]
+|Templates should have a means of matching values based on substrings, greater than a value, etc. || [https://bugzilla.mozilla.org/show_bug.cgi?id=285631 285631]
 |-
-| better ways of doing databinding, for instance to XML, components, or JS objects.|| [https://bugzilla.mozilla.org/show_bug.cgi?id=285631 285631]
+|Better ways of doing databinding, for instance to XML, components, or JS objects.|| [https://bugzilla.mozilla.org/show_bug.cgi?id=285631 285631]
 |-
-| a [[XUL:Slider_Tag|slider tag]] (scale) for volume controls. Safari RSS has this and WebForms 2.0 will have this. We should make it work. || [https://bugzilla.mozilla.org/show_bug.cgi?id=290255 290255]
+|A [[XUL:Slider_Tag|slider tag]] (scale) for volume controls. Safari RSS has this and WebForms 2.0 will have this. We should make it work. || [https://bugzilla.mozilla.org/show_bug.cgi?id=290255 290255]
 |-
-|get the <spinbuttons> widget to work. It's missing images currently. ||[https://bugzilla.mozilla.org/show_bug.cgi?id=155053 155053].
+|Get the <spinbuttons> widget to work. It's missing images currently. ||[https://bugzilla.mozilla.org/show_bug.cgi?id=155053 155053].
 |-
-|fix all the existing XBL implemented elements so that they actually have all the methods of the interfaces they say they implement.||
+|Fix all the existing XBL implemented elements so that they actually have all the methods of the interfaces they say they implement.||
 |-
-|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.||
 |-
-|need to find a way to load localization files, both DTDs and string bundles, 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. (NeilDeakin) Supporting remote localization isn't a high priority but getting widgets like dialog and wizard to work properly is.||
+|Get the dtd handling working for remote content so that dialog/wizard and so on will work there. (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?||
 |-
-|improve chrome URLs so that name collisions aren't going to occur. (AxelHecht) proposal? Not sure what this is supposed to be. (NeilDeakin) BenjaminSmedberg proposed using namespaced package names in http://bdsmedberg.no-ip.org:8080/chrome/||
+|Improve chrome URLs so that name collisions aren't going to occur. (AxelHecht) proposal? Not sure what this is supposed to be. (NeilDeakin) BenjaminSmedberg proposed using namespaced package names in http://bdsmedberg.no-ip.org:8080/chrome/||
 |-
-|popups have a issues with certain content. We need to fix those.||
+|Popups have a issues with certain content. We need to fix those.||
 |-
 |Specify the XUL box model and then make sure it is implemented that way||
 |-
-|make it so that XBL can be attached without using CSS. Or, just make it so that XBL is available right a binding is applied.||[https://bugzilla.mozilla.org/show_bug.cgi?id=265086 265086].
+|Make it so that XBL can be attached without using CSS. Or, just make it so that XBL is available right a binding is applied.||[https://bugzilla.mozilla.org/show_bug.cgi?id=265086 265086].
 |}