Hi, Yosi–
On 10/6/15 9:30 PM, Yoshifumi Inoue wrote:
It's exciting!
Thanks!
For Shadow DOM, current Blink implementation traverses composed tree
rather than DOM tree. We introduced a concept position in composed
tree and ephemeral range in composed tree; "ephemeral" means range in
composed
How does this work with shadow dom? Range is not very friendly to that.
On Oct 6, 2015 4:35 PM, "Frederick Hirsch" wrote:
> This is a call for consensus (CfC) to publish a First Public Working Draft
> (FPWD) of FindText API; deadline 14 October (1 week)
>
> This FindText API
This is a call for consensus (CfC) to publish a First Public Working Draft
(FPWD) of FindText API; deadline 14 October (1 week)
This FindText API is joint deliverable of the WebApps WG and Web Annotation WG
(listed as "Robust Anchoring" in the charters [1], [2]).
This is a Call for Consensus
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19771
Gary Kacmarcik changed:
What|Removed |Added
Status|NEW |RESOLVED
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26813
Anne changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
ISSUE-187: Https://github.com/w3c/uievents/issues/20
http://www.w3.org/2008/webapps/track/issues/187
Raised by:
On product:
I closed this--it was opened by accident.
-Original Message-
From: Web Applications Working Group Issue Tracker
[mailto:sysbot+trac...@w3.org]
Sent: Tuesday, October 6, 2015 5:26 PM
To: public-webapps@w3.org
Subject: ISSUE-187: Https://github.com/w3c/uievents/issues/20
ISSUE-187:
It's exciting!
For Shadow DOM, current Blink implementation traverses composed tree rather
than DOM tree.
We introduced a concept position in composed tree and ephemeral range in
composed tree;
"ephemeral" means range in composed tree isn't live. Ephemeral range
objects aren't update at
DOM
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21083
Gary Kacmarcik changed:
What|Removed |Added
Status|NEW |RESOLVED
Hi, Eliott–
Good question.
I don't have a great answer yet, but this is something that will need to
be worked out with Shadow DOM, not just for this spec, but for Selection
API and others, as well as to CSS, which has some Range-like styling.
I don't know if this means a change to Shadow
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21121
Gary Kacmarcik changed:
What|Removed |Added
Status|NEW |RESOLVED
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21083
Bug 21083 depends on bug 21121, which changed state.
Bug 21121 Summary: Define mobile phone related keys
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21121
What|Removed |Added
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21083
Bug 21083 depends on bug 21137, which changed state.
Bug 21137 Summary: Define key names for game controller of Android
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21137
What|Removed |Added
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22569
Gary Kacmarcik changed:
What|Removed |Added
Status|NEW |RESOLVED
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22891
Gary Kacmarcik changed:
What|Removed |Added
Status|NEW |RESOLVED
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23259
Gary Kacmarcik changed:
What|Removed |Added
Status|NEW |RESOLVED
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25485
Gary Kacmarcik changed:
What|Removed |Added
Status|NEW |RESOLVED
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21120
Gary Kacmarcik changed:
What|Removed |Added
Status|NEW |RESOLVED
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21083
Bug 21083 depends on bug 21120, which changed state.
Bug 21120 Summary: Define TV or A/V remote controller's keys
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21120
What|Removed |Added
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21136
Gary Kacmarcik changed:
What|Removed |Added
Status|NEW |RESOLVED
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21083
Bug 21083 depends on bug 21136, which changed state.
Bug 21136 Summary: Define Home key and Back key of Android smartphone
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21136
What|Removed |Added
On Tue, Oct 6, 2015 at 3:34 PM, Doug Schepers wrote:
> Hi, Eliott–
>
> Good question.
>
> I don't have a great answer yet, but this is something that will need to be
> worked out with Shadow DOM, not just for this spec, but for Selection API
> and others, as well as to CSS, which
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21137
Gary Kacmarcik changed:
What|Removed |Added
Status|NEW |RESOLVED
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21830
Gary Kacmarcik changed:
What|Removed |Added
Status|NEW |RESOLVED
Hi, Tab–
Thanks for the correction. I assumed that Houdini would expose more of
the underpinnings of the ::selection pseudo-element [1] and its ilk.
Maybe that hasn't surfaced (and maybe it won't). It does seem to be more
magic, though, which I'd thought we were trying to demystify.
But if
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23907
Gary Kacmarcik changed:
What|Removed |Added
Status|NEW |RESOLVED
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23575
Arthur Barstow changed:
What|Removed |Added
Status|NEW |RESOLVED
On Mon, 5 Oct 2015 at 23:31 Joshua Bell wrote:
> Yeah - "When control is returned to the event loop" isn't precise enough.
> It's an open issue in the 2nd Ed. and I welcome suggestions for tightening
> it up. Note that Jake Archibald, at least, was happy with the Blink
>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27108
Arthur Barstow changed:
What|Removed |Added
Status|NEW |RESOLVED
https://www.w3.org/Bugs/Public/show_bug.cgi?id=14214
Arthur Barstow changed:
What|Removed |Added
Status|NEW |RESOLVED
30 matches
Mail list logo