XUL:Priority List: Difference between revisions

Note that I don't list issues with remote XUL. Current issues with remote XUL are listed on [[XUL:Remove_Privilege|another page]]. It is assumed that all of the items below should work in remote content as well, unless there is some valid security reason for them not to.

#merge the two toolkits, mainly by switching xpfe to the new toolkit

#a CanvasTag for customized drawing is needed.

#make it so that XBL can be attached without using CSS. Or, just make it so that XBL is available right after a call to createElement. See [https://bugzilla.mozilla.org/show_bug.cgi?id=265086 bug 265086].

#currently when one wants to filter out results that don't match a condition, an empty rule has to be used. There should be a simple way to negate results.

#get XUL elements to work well in XML documents. (NeilRashbrook) Many of the XUL helper methods are currently defined on the XUL document. (AxelHecht) Is this part of my favorite content sink story or vice versa?

#way of making panels which arrange to fit, much like a Windows icon view. This can more or less be done with display: block, assuming that this doesn't change in upcoming CSS specs, but a tag for this would be nice. XAML calls this a FlowPanel and is a key layout primitive. (MinhNguyen) Java's AWT also has FlowLayout as the defalt layout manager.

#ensure that scrolling APIs for getting and changing the scroll position in elements are available and usable in remote content. Also useful would be to have a scrollToPosition type function for textboxes.

#add some functions to the listbox so that creating multi-column items is easier.

#allow toolbars that can be placed on the side or in a single row. Might not be as necessary with good toolbar customization capability.

#selecting text in a chrome window seems to be disabled regardless of -moz-user-select. We should allow this if the style is set right. Note that an inline label uses a different frame for displaying text so it might not be possible there, but I think it's necessary to have some level of selectable text. (NeilRashbrook) Note that read-only textboxes have the advantage of being accessible (modulo caret issues).

#add a crop value which crops but doesn't add the ellipsis. (NeilRashbrook) style="overflow: crop;"

#translucent dragging to allow dragging icons, treerows, etc around. I think only the Mac has this currently.

#add some styles to allow tabs to placed on the other sides on the tabbox.

#when one drags in some applications, a rectangle appears where dragging making it easier to determine what will be selected. In addition, the items inside become selected. This would be a useful feature to have.

#have an API for passwords to be saved. Mozilla has this. Needs to be accessible without allowing the retrieval of passwords associated with other components.

#probably want to have filters.

#be able to easily get access to the windows of an application, including remotely. For instance, an array or tree of all windows opened by the application.

#access to a font picker. Windows, at least, has a font picker as a common dialog. We should provide something like this.

#tri-state checkbox that actually displays in three states and is more sane.

#be able to modify images.

#some people might want to put more than one window definition in a single file, at least, small dialogs. (NeilRashbrook) Perhaps you could choose the window by the anchor on the URL? (MinhNguyen) And you could then surround the window tags with a windowset tag.

These items are already being implemented.