eters; public-webapps
> Subject: Re: [selection] Selection.setBaseAndExtent
>
> Focus and anchor are different concepts from base and extent. While the
> former always coincide with start and end, base and extent may be different
> from those two.
>
> In particular, when a user
for
>> this?
>>
>>
>>
>> *From:* Ryosuke Niwa [mailto:rn...@apple.com]
>> *Sent:* Wednesday, August 6, 2014 12:43 PM
>> *To:* James M. Greene
>> *Cc:* Ben Peters; public-webapps
>> *Subject:* Re: [selection] Selection.setBaseAndExtent
>>
>
Peters
Cc: Ryosuke Niwa; James M. Greene; public-webapps
Subject: Re: [selection] Selection.setBaseAndExtent
For what its worth, we plan to remove base and extent from Blink/Chromium
(https://code.google.com/p/chromium/issues/detail?id=230267). We've found that
developers do not understan
n...@apple.com]
> *Sent:* Wednesday, August 6, 2014 12:43 PM
> *To:* James M. Greene
> *Cc:* Ben Peters; public-webapps
> *Subject:* Re: [selection] Selection.setBaseAndExtent
>
>
>
> Focus and anchor are different concepts from base and extent. While the
> former always coincide wi
t: Re: [selection] Selection.setBaseAndExtent
Focus and anchor are different concepts from base and extent. While the former
always coincide with start and end, base and extent may be different from those
two.
In particular, when a user selects text by double clicking on a word, base and
e
length ([DOM4]). Otherwise, it must create a new range,
>> set ([DOM4]) its start to (baseNode, baseOffset) and its and end to
>> (extentNode, extentOffset), and set the context object's range to the
>> newly-created range.
>>
>>
>>
>> From: Ben Peter
d end to
> (extentNode, extentOffset), and set the context object's range to the
> newly-created range.
>
>
>
> *From:* Ben Peters
> *Sent:* Tuesday, May 20, 2014 11:37 AM
> *To:* Ben Peters; Ryosuke Niwa; public-webapps@w3.org
> *Subject:* RE: [selection] Selection.set
?This API is already used on the web so we should probably keep it as-is.
From: James M. Greene
Sent: Tuesday, August 5, 2014 4:58 PM
To: Ben Peters
Cc: Ryosuke Niwa; public-webapps
Subject: RE: [selection] Selection.setBaseAndExtent
For consistent terminology
*Sent:* Tuesday, May 20, 2014 11:37 AM
> *To:* Ben Peters; Ryosuke Niwa; public-webapps@w3.org
> *Subject:* RE: [selection] Selection.setBaseAndExtent
>
>
>
> I have filed a bug to track this issue [1].
>
>
>
> Ben
>
>
>
> [1] https://www.w3.org/Bugs/Public/show_bug
1:37 AM
To: Ben Peters; Ryosuke Niwa; public-webapps@w3.org
Subject: RE: [selection] Selection.setBaseAndExtent
I have filed a bug to track this issue [1].
Ben
[1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=25831
From: Ben Peters [mailto:ben.pet...@microsoft.com]
Sent: Monday, May 5, 2014 1
Monday, May 5, 2014 11:28 PM
> To: Ryosuke Niwa; public-webapps@w3.org
> Subject: [selection] Selection.setBaseAndExtent
>
> I noticed that some websites use selection.setBaseAndExtent [1]. According to
> what limited documentation I could find, it works similar to
> selection
I have filed a bug to track this issue [1].
Ben
[1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=25831
From: Ben Peters [mailto:ben.pet...@microsoft.com]
Sent: Monday, May 5, 2014 11:28 PM
To: Ryosuke Niwa; public-webapps@w3.org
Subject: [selection] Selection.setBaseAndExtent
I noticed that
I noticed that some websites use selection.setBaseAndExtent [1]. According to
what limited documentation I could find, it works similar to selection.extend.
Is there any intention to standardize this, or is it made obsolete by
selection.extend?
Ben
[1]
http://stackoverflow.com/questions/98527
13 matches
Mail list logo
