http://www.w3.org/Bugs/Public/show_bug.cgi?id=11669
Summary: Section: Parsing an event stream It looks like their
is a mistake in this ABNF description, end-of-line
is repeated: stream= [ bom ] *event event
= *(
I have removed LocalizableString interface from the Widgets API
specification because no one has proposed any use cases for it.
The purpose of the interface was to allow a developer to interrogate an
attribute of the widget object to find out what language that attribute
may be written in (if
On Wed, 05 Jan 2011 12:39:05 +0100, Marcos Caceres marc...@opera.com
wrote:
I have removed LocalizableString interface from the Widgets API
specification because no one has proposed any use cases for it.
The purpose of the interface was to allow a developer to interrogate an
attribute of
On 1/5/11 1:47 PM, Charles McCathieNevile wrote:
On Wed, 05 Jan 2011 12:39:05 +0100, Marcos Caceres marc...@opera.com
wrote:
I have removed LocalizableString interface from the Widgets API
specification because no one has proposed any use cases for it.
The purpose of the interface was to
Clipboard API and events
Status of this document
This is a Clipboard API event specification draft edited by Hallvord R. M.
Steen, Opera Software. Although I've used W3C stylesheets for convenience
this spec is not currently adopted by the W3C.
Thanks for taking initiative on this topic.
Hi Hallvord, All,
During last November's TPAC meeting, we briefly discussed [1] the
Clipboard Operations spec [2] (last published by the Web API WG in 2006
[3]). The general consensus then, was that it would be abandoned given
there was no active editor and some related functionality is being
