Re: Call for Consensus: Publish First Public Working Draft of FindText API, respond by 14 October

+1 Looks like I great start. Thanks again, Doug! On Oct 8, 2015 11:51 AM, "Frederick Hirsch" wrote: > +1 to FPWD of FindText API > > > On Oct 7, 2015, at 11:38 AM, Robert Sanderson > wrote: > > > > +1 to FPWD > > > > On Wed, Oct 7, 2015 at 8:34 AM, Ivan

Re: Call for Consensus: Publish First Public Working Draft of FindText API, respond by 14 October

+1 to FPWD Greetings, Ben Ben De Meester Researcher Semantic Web Ghent University - iMinds - Multimedia Lab | Faculty of Engineering and Architecture | Department of Electronics and Information Systems Gaston Crommenlaan 8 bus 201, B-9050 Ledeberg-Ghent, Belgium t: +32 9 331 49 59 | e:

Re: Call for Consensus: Publish First Public Working Draft of FindText API, respond by 14 October

+1 to FPWD of FindText API > On Oct 7, 2015, at 11:38 AM, Robert Sanderson wrote: > > +1 to FPWD > > On Wed, Oct 7, 2015 at 8:34 AM, Ivan Herman wrote: > I am happy to have this documents published as FPWD. > > Ivan > > > > On 06 Oct 2015, at 22:32 ,

Re: Call for Consensus: Publish First Public Working Draft of FindText API, respond by 14 October

I am happy to have this documents published as FPWD. Ivan > On 06 Oct 2015, at 22:32 , 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 is

Re: Call for Consensus: Publish First Public Working Draft of FindText API, respond by 14 October

+1 to FPWD On Wed, Oct 7, 2015 at 8:34 AM, Ivan Herman wrote: > I am happy to have this documents published as FPWD. > > Ivan > > > > On 06 Oct 2015, at 22:32 , Frederick Hirsch wrote: > > > > This is a call for consensus (CfC) to publish a First Public Working

Re: Call for Consensus: Publish First Public Working Draft of FindText API, respond by 14 October

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]). +1 for publishing this

Re: Call for Consensus: Publish First Public Working Draft of FindText API, respond by 14 October

Hi, Raphaël– Yes, this is one narrowly-scoped piece of generalized functionality that we hope can get broad agreement and implementation. It's just one of the building blocks of a full set of robust anchoring features, some of which might be standardized, but which may actually be done in

Re: Call for Consensus: Publish First Public Working Draft of FindText API, respond by 14 October

Hi Doug, It's just one of the building blocks of a full set of robust anchoring features, some of which might be standardized, but which may actually be done in script. We'll most likely gather together those pieces in the sort of umbrella document you suggest… maybe something like "Mapping Web

Re: Call for Consensus: Publish First Public Working Draft of FindText API, respond by 14 October

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

Re: Call for Consensus: Publish First Public Working Draft of FindText API, respond by 14 October

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

Call for Consensus: Publish First Public Working Draft of FindText API, respond by 14 October

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

Re: Call for Consensus: Publish First Public Working Draft of FindText API, respond by 14 October

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

Re: Call for Consensus: Publish First Public Working Draft of FindText API, respond by 14 October

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

Re: Call for Consensus: Publish First Public Working Draft of FindText API, respond by 14 October

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

Re: Call for Consensus: Publish First Public Working Draft of FindText API, respond by 14 October

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