Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest

2015-02-11 Thread Marc Fawzi
even if the DOM must remain a single-threaded and truly lock/barrier/fence-free data structure, what you are reaching for is doable now, with some help from standards bodies. ***But not by vague blather*** You're contradicting yourself within a single two-line paragraph, being vague in your own

Re: [Unbearable] IETF seeking feedback on proposed Token Binding Working Group

2015-02-11 Thread Anne van Kesteren
On Wed, Feb 11, 2015 at 7:41 PM, Andrei Popov andrei.po...@microsoft.com wrote: This is part of a starting point proposal for the new working group; we expect the documents to change. I think it would be best if the document was written in such a way that any API could be plugged on top. And

[clipboard] Feature detect Clipboard API support?

2015-02-11 Thread James M. Greene
The current spec still leaves me a bit unclear about if implementors must include the ability to feature detect Clipboard API support, which I think is a critical requirement. In particular, I *need* to be able to detect support for the Clipboard API (click-to-copy support, in particular) in

Re: [clipboard] Feature detect Clipboard API support?

2015-02-11 Thread Michaela Merz
AFAIK, you can't trigger a clip board request without human interaction. $('#element).off().on('click',function(e) { var clip = new ClipboardEvent('copy'); clip.clipboardData.setData('text/plain','some data'); clip.preventDefault(); e.target.dispatchEvent(clip); });

Re: [clipboard API] platform integration stuff - in spec or out of scope?

2015-02-11 Thread James M. Greene
We never really came to a decision on if RTF (application/rtf) should be listed as a mandatory MIME type but the general consensus seemed to be leaning toward yes: https://lists.w3.org/Archives/Public/public-webapps/2013OctDec/0197.html Sincerely, James Greene On Sat, Jan 31, 2015 at

Re: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest

2015-02-11 Thread Brendan Eich
Marc Fawzi wrote: even if the DOM must remain a single-threaded and truly lock/barrier/fence-free data structure, what you are reaching for is doable now, with some help from standards bodies. ***But not by vague blather*** Sorry, I was too grumpy -- my apologies. I don't see much

Re: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest

2015-02-11 Thread Boris Zbarsky
On 2/11/15 3:04 PM, Brendan Eich wrote: If you want multi-threaded DOM access, then again based on all that I know about the three open source browser engines in the field, I do not see any implementor taking the huge bug-risk and opportunity-cost and (mainly) performance-regression hit of

Re: [clipboard API] platform integration stuff - in spec or out of scope?

2015-02-11 Thread Hallvord Reiar Michaelsen Steen
On Wed, Feb 11, 2015 at 3:34 PM, James M. Greene james.m.gre...@gmail.com wrote: We never really came to a decision on if RTF (application/rtf) should be listed as a mandatory MIME type but the general consensus seemed to be leaning toward yes:

Re: [clipboard] Feature detect Clipboard API support?

2015-02-11 Thread Glenn Maynard
On Wed, Feb 11, 2015 at 12:34 PM, Michaela Merz michaela.m...@hermetos.com wrote: AFAIK, you can't trigger a clip board request without human interaction. $('#element).off().on('click',function(e) { var clip = new ClipboardEvent('copy');

Re: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest

2015-02-11 Thread Boris Zbarsky
On 2/11/15 9:45 PM, Marc Fawzi wrote: this backward compatibility stuff is making me think that the web is built upon the axiom that we will never start over and we must keep piling up new features and principles on top of the old ones Pretty much, yep. this has worked so far, miraculously

Re: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest

2015-02-11 Thread Marc Fawzi
this backward compatibility stuff is making me think that the web is built upon the axiom that we will never start over and we must keep piling up new features and principles on top of the old ones this has worked so far, miraculously and not without overhead, but I can only assume that it's at

Re: Thread-Safe DOM // was Re: do not deprecate synchronous XMLHttpRequest

2015-02-11 Thread Tab Atkins Jr.
On Thu, Feb 12, 2015 at 1:45 PM, Marc Fawzi marc.fa...@gmail.com wrote: this backward compatibility stuff is making me think that the web is built upon the axiom that we will never start over and we must keep piling up new features and principles on top of the old ones Yup. this has worked

Re: [clipboard API] platform integration stuff - in spec or out of scope?

2015-02-11 Thread James M. Greene
Allow me to clarify my position. My expectation is NOT for the browsers' default action on copy/cut to convert HTML into RTF. I do not see any such implication of that behavior in the spec language [1]. Rather, I just want to ensure that browsers will honor/maintain that clipboard format/segment

IETF seeking feedback on proposed Token Binding Working Group

2015-02-11 Thread Arthur Barstow
[ public-webapps should have been included but was not ] Forwarded Message Subject:IETF seeking feedback on proposed Token Binding Working Group Date: Wed, 11 Feb 2015 07:00:35 -0500 From: Arthur Barstow art.bars...@gmail.com Reply-To: unbeara...@ietf.org CC:

Re: IETF seeking feedback on proposed Token Binding Working Group

2015-02-11 Thread Anne van Kesteren
On Wed, Feb 11, 2015 at 1:10 PM, Arthur Barstow art.bars...@gmail.com wrote: WebApps - please note the draft spec includes a new XHR property withRefererTokenBindingID https://tools.ietf.org/html/draft-balfanz-https-token-binding-00#section-3.4. If anyone has feedback about the proposal,