https://www.w3.org/Bugs/Public/show_bug.cgi?id=23422
Bug ID: 23422
Summary: Adding a method to deliver editing-related events to a
DOM element
Product: WebAppsWG
Version: unspecified
Hardware: All
OS: All
On Tue, Oct 1, 2013 at 9:33 PM, Kyle Huey m...@kylehuey.com wrote:
The File API specifies how to deal with fragment identifiers. It should
also specify what to do with the query string. Presumably it should be
ignored when looking up blob URIs.
This is also what
04.09.2013, 22:19, Dimitri Glazkov dglaz...@chromium.org:
On Sun, Sep 1, 2013 at 9:42 AM, Alexey Kuzmin ale...@alexeykuzmin.com
wrote:
Hello!
As I understand current spec [1] there is only two ways to provide styles
for DOM elements in shadow trees:
1) add styles to document and
Hi All,
During WebApps' f2f meetings, we typically review each spec in
[PubStatus] to determine if the specs' data is accurate, as well as to
identify any general issues about each spec. I think this has been
useful to help get us on the same page as well as to help set
expectations such as
Hi Kris, Adrian, Ken,
If any of the testing-related data for the Web Sockets spec in
[PubStatus] is not accurate, please provide corrections.
Also, please provide a short update re plans for CR interop testing
(Draft implementation report is
Hi Feras,
If any of the data for the Streams API spec in [PubStatus] is not
accurate, please provide corrections.
Also, please see the following thread and let us know your plan for this
spec
http://lists.w3.org/Archives/Public/public-webapps/2013JulSep/0599.html.
-Thanks, ArtB
Hi Alex, Kris, Adrian,
If any of the testing-related data for the Web Messaging spec in
[PubStatus] is not accurate, please provide corrections.
Also, please provide a short update re plans for CR interop testing
(Draft implementation report is
Hi Travis and Gary,
If any of the data for D3E in [PubStatus] is not accurate, please
provide corrections.
Also, please provide a short update re the plan and time-frame to
publish a new LCWD. [Hint: it would be really nice to get a new LCWD of
D3E published as soon as possible ;-)]
Hi Vincent,
If any of the data for the Pointer Lock spec in [PubStatus] is not
accurate, please provide corrections.
Also, if you have any new information re your plans for the spec - last
published 29-May-2012 - or the spec's status with respect to being
feature complete, implementation
Hi Lachlan,
If any of the data for the Selectors API v2 spec in [PubStatus] is not
accurate, please provide corrections.
Also, if you have any new information re your plans for the spec - last
published 28-June-2012 - or the spec's status with respect to being
feature complete,
Hi Takayoshi and Kenji,
If any of the data for the IME spec in [PubStatus] is not accurate,
please provide corrections.
Also, if you have any new information re your plans for the spec, or the
spec's status with respect to being feature complete, implementation
status, etc. please let us
Hi Gary, Travis,
If any of the data for the UI Events spec in [PubStatus] is not
accurate, please provide corrections.
Also, if you have any new information re your plans for the spec - last
published 25-July-2013 - or the spec's status with respect to being
feature complete, implementation
Hi Jungkee,
If any of the testing-related data for Progress Events in [PubStatus] is
not accurate, please provide corrections.
Also, I would appreciate it, if you would please provide a short update
re the status and plan for CR Implementation Report
Hi Tantek,
If any of the data for Fullscreen in [PubStatus] is not accurate, please
provide corrections.
Also, if you have any new information re your plans for the spec - last
published 6-July-2012 - or the spec's status with respect to being
feature complete, implementation status, etc.,
Hi Kinuko,
If any of the data for the Quota Management API spec in [PubStatus] is
not accurate, please provide corrections.
Also, if you have any new information re your plans for the spec - last
published 03-July-2012 - or the spec's status with respect to being
feature complete,
Hi Bryan, Eduardo,
If any of the data for the Push API spec in [PubStatus] is not accurate,
please provide corrections.
Also, if you have any new information re your plans for the spec, the
spec's status with respect to being feature complete, implementation
status, etc., please let us
Hi Mounir,
If any of the data for the Screen Orientation API in [PubStatus] is not
accurate, please provide corrections.
Also, if you have any new information re your plans for the spec - last
published 06-Dec-2012 - or the spec's status with respect to being
feature complete,
Hi Tina,
If any of the test-related data for the Server-Sent Events spec in
[PubStatus] is not accurate, please provide corrections.
Also, I would appreciate it, if you would please provide a short update
re the status and plans for the CR Implementation Report
Hi Dimitri,
If any of the data for the four Web Components documents (including the
`Explainer`) in [PubStatus] is not accurate, please provide corrections.
Also, for each of these documents, please provide a short summary re
your plans for the spec, f.ex. the spec's status with respect to
Hi Jonas, Joshua, Eliot and Alex,
If any of the test-related data for Indexed Database API in [PubStatus]
is not accurate, please provide corrections.
Also, what is the plan - f.ex. Who is going to do What and by When -
for: 1) reviewing test submissions; 2) completing the test suite; and 3)
Hi Simon, Odin,
If any of the testing-related data for the Web Workers spec in
[PubStatus] is not accurate, please provide corrections.
Also, please provide a short update re plans for CR interop testing.
As I understand it, several workers tests have been reviewed and
approved [Tests] but
Hi Eric,
If any of the data for your two File APIs in [PubStatus] is not
accurate, please provide corrections.
Also, if you have any new information re your plans for these specs
(last published 17-Apr-2012), or the specs' status with respect to being
feature complete, please let us know.
Hi Ted, Scott,
If any of the data for the Gamepad spec in [PubStatus] is not accurate,
please provide corrections.
Also, if you have any new information re your plans for the spec - last
published 29-May-2012 - or the spec's status with respect to being
feature complete, implementation
Hi Hallvord,
If any of the data for Clipboard APIs and Events in [PubStatus] is not
accurate, please provide corrections.
Also, if you have any new information re your plans for the spec, the
spec's status with respect to being feature complete, implementation
status, please let us know.
Hi Hallvord, Julian and Jungkee,
If any of the data for the XHR spec in [PubStatus] is not accurate,
please provide corrections.
I am also interested in the status and plans for both the version of XHR
that is supposed to move to LC-CR-REC in 2013 and the XHR-Bleeding-Edge
version.
-Thanks,
On Wed, Oct 2, 2013 at 12:29 PM, Arthur Barstow art.bars...@nokia.com wrote:
If any of the data for Fullscreen in [PubStatus] is not accurate, please
provide corrections.
Also, if you have any new information re your plans for the spec - last
published 6-July-2012 - or the spec's status with
On Wed, Oct 2, 2013 at 12:39 PM, Arthur Barstow art.bars...@nokia.com wrote:
If any of the data for the XHR spec in [PubStatus] is not accurate,
please provide corrections.
I am also interested in the status and plans for both the version of XHR
that is supposed to move to LC-CR-REC in 2013
On Fri, Sep 20, 2013 at 5:09 AM, Simon Pieters sim...@opera.com wrote:
On Fri, 20 Sep 2013 05:24:26 +0200, Jonas Sicking jo...@sicking.cc wrote:
I would hardly call taking the length subtracting any characters
before the , and applying a multiplier parsing. You don't have to
look at any
Sure thing, Art!
* Introduction to Web Components (http://www.w3.org/TR/components-intro/)
status should be WD, next working draft coming out shortly, adjusting for
changes in the underlying specs. Dominic Cooney (domin...@chromium.org) is
the primary editor of this document.
* Custom Elements
On Oct 2, 2013, at 12:29 PM, Arthur Barstow wrote:
Hi Eric,
If any of the data for your two File APIs in [PubStatus] is not accurate,
please provide corrections.
Also, if you have any new information re your plans for these specs (last
published 17-Apr-2012), or the specs' status with
On 2013-10-02 18:31, Arthur Barstow wrote:
If any of the data for the Selectors API v2 spec in [PubStatus] is not
accurate, please provide corrections.
Also, if you have any new information re your plans for the spec - last
published 28-June-2012 - or the spec's status with respect to being
Thanks for the update Dimitri!
On 10/2/13 1:58 PM, ext Dimitri Glazkov wrote:
* HTML Imports (http://www.w3.org/TR/html-imports/) is getting close
to the next WD. Hajime Morrita has been working on that spec, and I
would like to put him down as the primary editor.
That's fine with me. Thanks
On 10/2/13 12:51 PM, ext Anne van Kesteren wrote:
On Wed, Oct 2, 2013 at 12:29 PM, Arthur Barstow art.bars...@nokia.com wrote:
If any of the data for Fullscreen in [PubStatus] is not accurate, please
provide corrections.
Also, if you have any new information re your plans for the spec - last
Hi Arthur,
On Thu, Oct 3, 2013 at 1:30 AM, Arthur Barstow art.bars...@nokia.comwrote:
Hi Kinuko,
If any of the data for the Quota Management API spec in [PubStatus] is not
accurate, please provide corrections.
Also, if you have any new information re your plans for the spec - last
Sorry for the delay.
On Tue, Sep 3, 2013 at 9:00 PM, Anne van Kesteren ann...@annevk.nl wrote:
On Tue, Sep 3, 2013 at 9:18 AM, Takeshi Yoshino tyosh...@google.com
wrote:
In the spec, we have three cancels
- cancel an instance of fetch algorithm
- cancel network activity
These are the
35 matches
Mail list logo
