https://www.w3.org/Bugs/Public/show_bug.cgi?id=27511
Hayato Ito hay...@chromium.org changed:
What|Removed |Added
Status|NEW |RESOLVED
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27533
Bug ID: 27533
Summary: The execCommand() show UI argument is unused
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
On Sat, Dec 6, 2014 at 7:34 AM, Arthur Barstow art.bars...@gmail.com
wrote:
On 12/6/14 4:21 AM, Steve Faulkner wrote:
Hi all,
looking at the custom elements spec http://w3c.github.io/
webcomponents/spec/custom/ i realized it includes no defined
requirements or advice for web developers on
On 8 December 2014 at 16:37, Dimitri Glazkov dglaz...@google.com wrote:
Totally. Happy to review/accept patches.
Great!
PR
https://github.com/w3c/webcomponents/pull/26
forked
http://stevefaulkner.github.io/webcomponents/spec/custom/#semantics
--
Regards
SteveF
HTML 5.1
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27538
Bug ID: 27538
Summary: [Custom]: Tone of note doesn't reflect severity
Product: WebAppsWG
Version: unspecified
Hardware: All
OS: All
Status: NEW
Since the Editing Task Force is working on several input-related issues, we
would like to take over the work on Input Events. I have created an unofficial
document for that purpose at
http://w3c.github.io/editing-explainer/input-events.html. It is based on the
work in DOM L3. Can we move the
|input| and |beforeinput| were only brought into D3E because they were
1) Required since |keypress| was being deprecated (with
|input|/|beforeinput| intended as a replacement)
2) Not being worked on by anyone.
From that POV, it sounds like a reasonable idea. Esp. since one of the
places (IIRC)
