[Bug 16357] Avoid proliferating init*Event methods in preparation for Event constructors

https://www.w3.org/Bugs/Public/show_bug.cgi?id=16357

Travis Leithead [MSFT] <travil@microsoft.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |ASSIGNED

--- Comment #3 from Travis Leithead [MSFT] <travil@microsoft.com> 2012-04-10 21:52:24 UTC ---
(In reply to comment #2)
> I don't think that's acceptable. A standard should describe the end goal, not
> some inbetween state.

Understand, but if I remove the init methods completely from CompositionEvent,
and WheelEvent (TextEvent is gone), I'm going to get a bug later that says that
"I cannot initialize the properties of a composition/wheel event!"

That's going to then lead to specifying event constructors as the only real
alternative to bringing back the init methods.

I don't want to add event constructors because that's what DOM4 is introducing,
and I don't want to be introducing new features to DOM3 events at this point in
it's life. (Reminder: it needs to be finished!)

Marking these as deprecated was the best option I had. I'd rather have this
spec finish with a deprecated set of init methods knowing that they may never
be implemented in some user agents, versus finishing with a set of interfaces
that don't support initialization at all.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Tuesday, 10 April 2012 21:52:30 UTC