Closed
Bug 312966
Opened 19 years ago
Closed 18 years ago
Drop XML Events from the default build
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: ian, Unassigned)
Details
One of the things we might want to cut from Firefox's default builds is XML Events. It is, as far as I can tell, never used on the Web, and is just yet another way of doing what can already be done multiple ways (e.g. with event handlers attributes and the DOM EventTarget API).
Comment 1•19 years ago
|
||
er, this would totally break XForms extension. Though, I think the best solution would be that XML Events could be implemented as an extension too. So basically XTF for namespaced attributes.
Comment 2•19 years ago
|
||
Argh. Yes, this is definately a no-go from XForms.
OS: MacOS X → All
Hardware: Macintosh → All
Comment 3•19 years ago
|
||
The code isn't that big to make any difference. I assume that means that Webforms 2 won't go in since no one uses it and there are other ways of achieving the same behavior?
I think that Firefox should look at XML Events not as something that stands alone, but rather XML Events is an important piece of things to come from the W3C. Especially for any XML-based UI standards. XForms 1.0 and 1.1, SVG 1.2, XHTML 2 and X+V all use XML Events. Opera implements X+V and XML Events, so I'd think that there is SOME content out there already.
Reporter | ||
Comment 5•18 years ago
|
||
> XForms 1.0 and 1.1, SVG 1.2, XHTML 2 and X+V all use XML Events.
...and they all suck, and I'd strongly recommend that Mozilla not implement any of those, either (in default builds, at least).
Summary: Cut XML Events from the default build? → Drop XML Events from the default build
Comment 6•18 years ago
|
||
(In reply to comment #5) > > XForms 1.0 and 1.1, SVG 1.2, XHTML 2 and X+V all use XML Events. > > ...and they all suck, and I'd strongly recommend that Mozilla not implement any > of those, either (in default builds, at least). > Your personal opinion is irrelevant to this discussion. Unlike XForms, XML Events cannot be easily separated out into an extension and in order for us to create XForms extensions (and other technologies) XML Events need to be there. If you really think this is a codesize issue, post some numbers and we'll go from there.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WONTFIX
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•