On Apr 13, 2014, at 5:21 AM, Aryeh Gregor a...@aryeh.name wrote:
On Fri, Apr 11, 2014 at 9:05 PM, Ryosuke Niwa rn...@apple.com wrote:
Thanks for the pointer.
Unfortunately, we might need to take a slightly different approach more
based on the CSS box tree because whitespace collapsing,
On Apr 11, 2014, at 9:29 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 4/11/14 10:09 AM, Domenic Denicola wrote:
- https://www.w3.org/Bugs/Public/show_bug.cgi?id=13145
-
https://web.archive.org/web/20121127212525/http://aryeh.name/spec/innertext/innertext.html
The outcome of that was
I've uploaded the first cut the selection API specification unofficial draft at
https://github.com/rniwa/selection-api
I've modernized and rephrased the text; e.g. the spec refers to browsing
context instead of defaultView, and defines selection's range being null as
being empty.
Finally,
From: Ryosuke Niwa [mailto:rn...@apple.com]
Given defining innerText is completely outside the scope of the selection API
specification, we might need to defer this part to a level 2 specification
since the only alternative is to wait for someone to write a innerText spec.
I don't know all
On 4/10/14 11:41 PM, ext Ryosuke Niwa wrote:
I've uploaded the first cut the selection API specification unofficial draft at
https://github.com/rniwa/selection-api
Wow, that was quick; thanks!
To facilitate review, I think it would be helpful if you would please
create a `directly readable`
Done: http://rniwa.github.io/selection-api.html
On Apr 11, 2014, at 7:35 AM, Arthur Barstow art.bars...@nokia.com wrote:
On 4/10/14 11:41 PM, ext Ryosuke Niwa wrote:
I've uploaded the first cut the selection API specification unofficial draft
at https://github.com/rniwa/selection-api
Wow,
On Apr 11, 2014, at 7:09 AM, Domenic Denicola dome...@domenicdenicola.com
wrote:
From: Ryosuke Niwa [mailto:rn...@apple.com]
Given defining innerText is completely outside the scope of the selection
API specification, we might need to defer this part to a level 2
specification since
On 4/11/14 10:09 AM, Domenic Denicola wrote:
- https://www.w3.org/Bugs/Public/show_bug.cgi?id=13145
-
https://web.archive.org/web/20121127212525/http://aryeh.name/spec/innertext/innertext.html
The outcome of that was basically that the WebKit folks wanted innerText
to be some sort of
Looking into selection in this brave new world (Shadow DOM for sure, but
there are issues as well with flexbox if I'm not mistaken), is definitely
something we are interested in.
I also agree with moving selection to its own spec. Solving selection first
opens the door to solving editing.
I would think that would be a great idea. We would need to contact the
different editor development teams and see if that works for them.
On Fri, Mar 21, 2014 at 2:12 PM, Ryosuke Niwa rn...@apple.com wrote:
On Mar 18, 2014, at 2:22 PM, Johannes Wilm johan...@fiduswriter.com
wrote:
On
Web Applications Working Group,
With a Selections API in its own specification, discussion topics include:
Document Object Model
Range
Selection
HTMLRange : Range
HTMLSelection : Selection
Interfaces such as HTMLRange and HTMLSelection can extend Range and Selection
to provide UI
On Mar 18, 2014, at 2:22 PM, Johannes Wilm johan...@fiduswriter.com wrote:
On Mon, Mar 17, 2014 at 4:59 AM, Robin Berjon ro...@w3.org wrote:
On 15/03/2014 18:44 , Johannes Wilm wrote:
yes btw -- where should one go to lobby in favor of the editing spec? I
have been communicating with
On Mon, Mar 17, 2014 at 1:59 PM, Robin Berjon ro...@w3.org wrote:
My understanding from talking to various people is that at least part of the
problem comes from the type of code that is currently deployed in the wild.
An awful lot of it works around browser inconsistencies not through feature
On Mon, Mar 17, 2014 at 4:59 AM, Robin Berjon ro...@w3.org wrote:
On 15/03/2014 18:44 , Johannes Wilm wrote:
yes btw -- where should one go to lobby in favor of the editing spec? I
have been communicating with several other browser-based editor
projects, and there seems to be a general
On 15/03/2014 18:44 , Johannes Wilm wrote:
yes btw -- where should one go to lobby in favor of the editing spec? I
have been communicating with several other browser-based editor
projects, and there seems to be a general interest of more communication
with the browser creators and spec writers.
On Mar 17, 2014, at 4:59 AM, Robin Berjon ro...@w3.org wrote:
On 15/03/2014 18:44 , Johannes Wilm wrote:
yes btw -- where should one go to lobby in favor of the editing spec? I
have been communicating with several other browser-based editor
projects, and there seems to be a general interest of
On Fri, Mar 14, 2014 at 1:43 AM, Ryosuke Niwa rn...@apple.com wrote:
It appears that there is a lot of new features such as CSS regions and shadow
DOM that have significant implications on selection API, and we really need a
spec. for selection API these specifications can refer to.
On 3/14/14 3:21 PM, ext Ryosuke Niwa wrote:
On Mar 14, 2014, at 5:58 AM, Arthur Barstow art.bars...@nokia.com wrote:
I think the selection API is ready for recommendation track work. It's
mostly interoperable between non-Gecko browsers.
One factor to consider re WebApps formally working on
On 3/16/14 9:57 AM, ext Arthur Barstow wrote:
[Draft]
http://www.w3.org/2012/webapps/charter/Overview.html#deliverables
That should be:
[Draft] http://afbarstow.github.io/WebApps/charter.html#deliverables
Hey,
yes btw -- where should one go to lobby in favor of the editing spec? I
have been communicating with several other browser-based editor projects,
and there seems to be a general interest of more communication with the
browser creators and spec writers. Currently the situation is that it's so
On 3/13/14 7:43 PM, ext Ryosuke Niwa wrote:
Hi,
It appears that there is a lot of new features such as CSS regions and shadow
DOM that have significant implications on selection API, and we really need a
spec. for selection API these specifications can refer to.
Thankfully, Aryeh has done a
On Mar 14, 2014, at 5:58 AM, Arthur Barstow art.bars...@nokia.com wrote:
On 3/13/14 7:43 PM, ext Ryosuke Niwa wrote:
Hi,
It appears that there is a lot of new features such as CSS regions and
shadow DOM that have significant implications on selection API, and we
really need a spec. for
From: Ryosuke Niwa [mailto:rn...@apple.com]
Any thoughts and opinions?
Have there been indications from vendors that they would have more resources to
devote to implementing or critiquing the selection API if it were isolated into
a smaller document? Is the idea that the surrounding text
Looking into selection in this brave new world (Shadow DOM for sure, but
there are issues as well with flexbox if I'm not mistaken), is definitely
something we are interested in.
We haven't gotten around it yet which I believe explain our lack of
feedback so far.
2014-03-14 8:43 GMT+09:00
On Mar 13, 2014, at 5:08 PM, Domenic Denicola dome...@domenicdenicola.com
wrote:
From: Ryosuke Niwa [mailto:rn...@apple.com]
Any thoughts and opinions?
Have there been indications from vendors that they would have more resources
to devote to implementing or critiquing the selection API
25 matches
Mail list logo
