FYI: Change in my affiliation
[ Bcc public-pointer-events ] FYI, as of January 20, I am no longer an employee (or affiliated with) Nokia. I have been re-appointed as a co-Chair of WebApps (and Chair of Pointer Events WG) under an Invited Expert status. I will continue to chair as a volunteer as I seek a new employer to support my chairing role and/or other opportunities. [Yes, that's a shameless hint to please contact me privately for any leads ;-)]. -Thanks, ArtB On 1/22/15 1:30 PM, Coralie Mercier wrote: I am pleased to announce that Art Barstow has been re-appointed as co-Chair of the Web Applications Working Group [1], and Chair of the Pointer Events Working Group [2] after a change in employment status. Per section 3.1.1 [3], I am re-appointing Art, under an Invited Expert status. Many thanks to Art for offering time to these groups. For Tim Berners-Lee, Director, and Philippe Le Hegaret, Interaction Domain Lead, Yves Lafon and Xiaoqian Wu, Web Applications Working Group Team Contacts, Doug Schepers, Pointer Events Working Group Team Contact; Coralie Mercier, W3C Communications [1] http://www.w3.org/2008/webapps/ [2] http://www.w3.org/2012/pointerevents/ [3] http://www.w3.org/2014/Process-20140801/#coi
Re: webview API common subset
On 1/23/15 5:11 AM, Kan-Ru Chen (陳侃如) wrote: Hi all, I intend to implement the webview element in gecko and as part of my research I put up a wiki page that summarize the browser-api or webview API that has been implemented by vendors here: https://wiki.mozilla.org/WebAPI/BrowserAPI/Common_Subset I wonder if other vendors are interested in creating a unified webview standard? I hope this is the right forum for this. Hi Kanru, Thanks for your e-mail. Where applicable, what do you think about including a link to the relevant standard? For example, it appears that back() has a standard at [1] and [2]. I say this because I presume some goals here are to help converge on an agreed standard if/when one is available and to help identify standardization gaps? -ArtB [1] https://html.spec.whatwg.org/#dom-history-back [2] http://www.w3.org/html/wg/drafts/html/master/browsers.html#dom-history-back Kanru
Re: [Selection] Should selection.getRangeAt return a clone or a reference?
On Thu, Jan 22, 2015 at 12:20 AM, Mats Palmgren m...@mozilla.com wrote: If we really want authors to have convenience methods like setStartBefore() on Selection, we could add them to Selection. Selection methods wouldn't provide the same functionality though. Selection.setStart* would presumably be equivalent to setStart* on the first range in the Selection, but how do you modify the start boundary point on other ranges when there are more than one? I guess we could add them as convenience methods, making setStart* operate on the first range and setEnd* on the last, but it's still an incomplete API for multi-range Selections. We could add, say, getRangeProxyAt(index) to get a selection object that has Rage interface if this is really what authors want. But right now, authors are not relying on the live-ness behavior because it's not interoperable. As I understand, not-interoperable is bigger issue than getRangeAt(index) does not have live-ness. In selections and editing, we have so much we wish to do, I'd like us to solve bigger issues first, make them available to editor developers, then improve as needed. Actually -- well, only if you're interested in doing this -- you could have both methods, then see how much authors prefer the live-ness. If it's proved that the live-ness is so much liked by editor developers, and if we have solved other critical issues at that point, I do not see any reasons other browsers do not follow. /koji
webview API common subset
Hi all, I intend to implement the webview element in gecko and as part of my research I put up a wiki page that summarize the browser-api or webview API that has been implemented by vendors here: https://wiki.mozilla.org/WebAPI/BrowserAPI/Common_Subset I wonder if other vendors are interested in creating a unified webview standard? I hope this is the right forum for this. Kanru
Re: webview API common subset
On 01/23/2015 02:20 PM, Arthur Barstow wrote: On 1/23/15 5:11 AM, Kan-Ru Chen (陳侃如) wrote: Hi all, I intend to implement the webview element in gecko and as part of my research I put up a wiki page that summarize the browser-api or webview API that has been implemented by vendors here: https://wiki.mozilla.org/WebAPI/BrowserAPI/Common_Subset I wonder if other vendors are interested in creating a unified webview standard? I hope this is the right forum for this. Hi Kanru, Thanks for your e-mail. Where applicable, what do you think about including a link to the relevant standard? For example, it appears that back() has a standard at [1] and [2]. back() in [1] is about the whole browsing context tree. webview would need to limit it to the contents of the element. So the scope of the session history needs to be split at webview. I say this because I presume some goals here are to help converge on an agreed standard if/when one is available and to help identify standardization gaps? -ArtB [1] https://html.spec.whatwg.org/#dom-history-back [2] http://www.w3.org/html/wg/drafts/html/master/browsers.html#dom-history-back Kanru
