And if so, which objects should they be on? Window? Documents? Elements?
-Boris
[Including Anne Tantek due to their work on Fullscreen]
The pointer lock specification intentionally mimics the fullscreen
specification to provide consistency for developers, as they are similar
and expected to be commonly used in the same apps. Neither specification
mention event properties.
On 1/10/13 1:19 PM, Vincent Scheib wrote:
The pointer lock specification intentionally mimics the fullscreen
specification to provide consistency for developers, as they are similar
and expected to be commonly used in the same apps. Neither specification
mention event properties.
But HTML5
Web Applications Working Group,
Greetings. In the BookmarkML approach, we can add bibliographic metadata,
useful for graphical user interface summarizations and visualizations of
bookmarks and useful for interoperability with authoring software when quoting,
citing and referencing materials.
On 1/10/13 2:02 PM, Vincent Scheib wrote:
I'm confused why HTML should include the properties, and not the
respective specifications.
Other than scope creep?
I am too; see the bug I linked to.
-Boris
On Thu, Dec 27, 2012 at 9:01 PM, Jens O. Meiert j...@meiert.com wrote:
Thanks for clarifying.
Can you help me explain the disconnect that I’m seeing in how the
draft is clear?
All it says is:
6.2 text-decoration Property
The text decorations, specified by the text-decoration property
On Thu, Jan 10, 2013 at 7:19 PM, Vincent Scheib sch...@google.com 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
