Assign non XUL attributes to a non XUL namespace

NEW
Unassigned

Status

()

Core
XUL
--
enhancement
17 years ago
8 years ago

People

(Reporter: Peter Wilson, Unassigned)

Tracking

Trunk
mozilla1.2alpha
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [xul1.0])

(Reporter)

Description

17 years ago
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.
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 1

17 years ago
Yes, this will also be important for schema validation.

Updated

17 years ago
Blocks: 70753
Whiteboard: [xul1.0]
Target Milestone: --- → mozilla1.0

Comment 2

17 years ago
Should we file a separate "bug" for reserved tagnames for future versions 
of XUL so that those dont get stepped on by other implementers?

Updated

16 years ago
Target Milestone: mozilla1.0 → mozilla1.2

Comment 3

16 years ago
Moving non nsbeta1+ XUL 1.0 bugs to mozilla1.2

Updated

16 years ago
No longer blocks: 70753

Updated

10 years ago
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: jrgmorrison → xptoolkit.widgets

Updated

8 years ago
Assignee: hyatt → nobody
You need to log in before you can comment on or make changes to this bug.