Currently Mozilla XUL uses arbitary additional attributes on XUL elements to pass data values to the program processing the XUL. e.g. errmsg etc. These additional attributes should be assigned to a different namespace than XUL. 1. This would aid documentation efforts as these attributes would, plainly, not be part of XUL. 2. A number of efforts are under way to use XML Schema or Relax NG to describe XUL so that syntax checking will be possible. The additional attributes can only be accommodated by the equivalent of attribute:any on an element description. This defeats syntax checking as any mis-spelling of a legitimate attribute will be silently picked up by the "any" catch all. 3. A similar usage should be adopted for non XUL elements. 4. The use of the <data> element which is also used in XUL for program data should be legitimized and documented.
17 years ago
Status: UNCONFIRMED → NEW
Ever confirmed: true
Yes, this will also be important for schema validation.
Target Milestone: --- → mozilla1.0
Should we file a separate "bug" for reserved tagnames for future versions of XUL so that those dont get stepped on by other implementers?
Moving non nsbeta1+ XUL 1.0 bugs to mozilla1.2
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: jrgmorrison → xptoolkit.widgets
You need to log in before you can comment on or make changes to this bug.