Re: DOM L3 Events Input Events Work to the Editing Task Force

[Кошмарчик]

|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) where we thought it was supposed to be was in the Editing
spec.

However, the biggest issues we had with |beforeinput| and |input| was
determining the correct event order relative to composition and keyboard
events. So it seems like a cross-dependency for D3E to depend on the
Editing spec to get |input| and |beforeinput| and for the Editing spec to
need D3E's composition and keyboard events (to properly specify the event
ordering).

Thus, I wonder if a separate Input Event spec (that both D3E and Editing
would refer to) would make more sense.

As for "easier to finish DOM L3", that depends. D2E defines keypress, which
is being deprecated in favor or input/beforeinput. Thus, D3E will not be a
complete functional replacement for D2E without a proper spec for
input/beforeinput.

-Gary


On Mon, Dec 8, 2014 at 2:05 PM, Ben Peters  wrote:

>  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 DOM L3 Input Events design to be only
> what is already implemented in browsers (which should make it easier to
> finish DOM L3, right?), and work on it going forward in the Editing Task
> Force?
>
>
>
> Ben
>

DOM L3 Events Input Events Work to the Editing Task Force

[Ben Peters]

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 DOM L3 Input Events design to be only what is 
already implemented in browsers (which should make it easier to finish DOM L3, 
right?), and work on it going forward in the Editing Task Force?

Ben

[Bug 27538] New: [Custom]: Tone of note doesn't reflect severity

[bugzilla]

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
  Severity: normal
  Priority: P2
 Component: Component Model
  Assignee: dglaz...@chromium.org
  Reporter: bugzi...@agosto.nl
QA Contact: public-webapps-bugzi...@w3.org
CC: m...@w3.org, public-webapps@w3.org
Blocks: 14968

"The addition of in line event handlers are for demonstration purposes only.
The event handlers could be added by the lifecycle callbacks imperatively, or
maybe even not used at all."

As a lot of developers forget correct event handlers; I feel as if this note
doesn't reflect the severity of the need for these event handlers.

I suggest something like:

"Developers **should** make sure event handlers are added for both keyboard and
mouse users. The inline event handlers shown in this example are for
demonstration purposes."

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Re: [custom-elements] Re: web developer conformance requirements and advice in custom elements spec

[Steve Faulkner]

On 8 December 2014 at 16:37, Dimitri Glazkov  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 

Re: [custom-elements] Re: web developer conformance requirements and advice in custom elements spec

[Dimitri Glazkov]

On Sat, Dec 6, 2014 at 7:34 AM, Arthur Barstow 
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 creation of custom elements
>> that are meaningful and expose useful semantics and behavior.
>>
>> I would like to take a stab at this, what's the best way to contribute?
>> pull requests?
>>
>
> Hi Steve,
>
> Yes, it appears you should submit a PR to [1] and I'm sure Dimitri will
> clarify if he recommends otherwise.
>

Totally. Happy to review/accept patches.


>
> BTW Dimitri - it looks like the ED has some relatively substantive changes
> since the last TR was published (October 2013) [Diff]. As such, it seems
> like the TR should be updated. WDYT?
>

Yes. I was kind of hoping to do the same trick that Hayato used for the
Shadow DOM spec, with the big red warning advising to go to the ED.


>
> -Thanks, AB
>
> [1] https://github.com/w3c/webcomponents
> [Diff] http://services.w3.org/htmldiff?doc1=http%3A%2F%
> 2Fwww.w3.org%2FTR%2F2013%2FWD-custom-elements-20131024%2F&
> doc2=http%3A%2F%2Fw3c.github.io%2Fwebcomponents%2Fspec%2Fcustom%2F
>
>
>

[Bug 27533] New: The execCommand() "show UI" argument is unused

[bugzilla]

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
  Severity: normal
  Priority: P2
 Component: HTML Editing APIs
  Assignee: a...@aryeh.name
  Reporter: phil...@opera.com
QA Contact: sideshowbarker+html-editing-...@gmail.com
CC: m...@w3.org, public-webapps@w3.org

The spec says "TODO: Define behavior for show UI." in a comment.

In Blink, the showUI argument does nothing, but there are two fixes:

In executeCreateLink:
// FIXME: If userInterface is true, we should display a dialog box to let the
user enter a URL.

In executeInsertImage:
// FIXME: If userInterface is true, we should display a dialog box and let the
user choose a local image.

Since not implementing these seems Web compatible, I suggest making showUI
explicitly do nothing, required merely for legacy compat.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 27511] [Shadow]: Six node trees in the diagram but description says "seven"

[bugzilla]

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27511

Hayato Ito  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Hayato Ito  ---
Thanks. Fixed.
https://github.com/w3c/webcomponents/commit/dbeb547270752f2909ace1753688f92489b9ec9a

-- 
You are receiving this mail because:
You are on the CC list for the bug.