Re: [PointerLock] Should there be onpointerlockchange/onpointerlockerror properties defined in the spec

On Thu, Jan 10, 2013 at 1:28 PM, Anne van Kesteren <> wrote:
> On Thu, Jan 10, 2013 at 7:19 PM, Vincent Scheib <> wrote:
>> Pending agreement to add properties to the fullscreen specification, I agree
>> this should be included in the specification.
> I think HTML should maintain the registry and policy for on*
> attributes insofar they concern Window/Document/HTMLElement objects.
> only fires on Document, fwiw.

That doesn't seem either scalable or documentation/implementation
friendly. It means that someone reading the X feature spec (to
implement it, to use it or to review it) will have to also go look at
the HTML spec. And know that he/she needs to do so. And it means that
the development of the X feature spec is blocked on getting the
attention of the HTML spec authors.

Isn't this the reason we adding "partial interface" to WebIDL?

/ Jonas

Received on Friday, 18 January 2013 03:35:47 UTC