On Wed, Mar 27, 2013 at 8:18 PM, Arun Ranganathan a...@mozilla.com wrote:
Done.
http://dev.w3.org/2006/webapi/FileAPI/#NetworkError
Awesome!
--
http://annevankesteren.nl/
The current clipboard API specification mentions security risks
of copy paste but doesn't seem to explicitly mention methods by
which user agents deal with such security risks.
Hi Ryosuke,
I did remove the section on cleaning up content because it was not implemented
by anyone and seemed
On 03/28/2013 12:34 PM, Hallvord Reiar Michaelsen Steen wrote:
On 03/28/2013 10:36 AM, Hallvord Reiar Michaelsen Steen wrote:
In particular, WebKit has been stripping script element from
the pasted content but this may have some side effects on CSS
rules.]
AFAIK (without re-testing right
On Thu, Mar 28, 2013 at 11:42 AM, James Graham jgra...@opera.com wrote:
I don't see why the interop issues are particularly far-fetched. The
approach of not problems in spec A because they ought to be addressed some
other hypothetical spec B is something we have tried before and it hasn't
On 03/28/2013 10:36 AM, Hallvord Reiar Michaelsen Steen wrote:
In particular, WebKit has been stripping script element from the
pasted content but this may have some side effects on CSS rules.]
AFAIK (without re-testing right now), WebKit's implementation is:
* rich text content that is
On Wed, Mar 27, 2013 at 1:35 PM, Jonas Sicking jo...@sicking.cc wrote:
Same question applies if you create an img src=blob:... and then
drawImage it into a canvas, does the canvas get tainted? Again, I
think different browsers do different things for data: URLs here.
You'd need to say img
So. :
rel type: import
spec name:
1) HTML Imports
2) Web Imports
:DG
The Future has arrived:
http://dom.spec.whatwg.org/#futures
Thanks in particular to the https://github.com/slightlyoff/DOMFuture
project for nailing down all of the details. If someone is interested
in contributing examples the DOM Standard accepts pull requests
https://github.com/whatwg/dom
3
Le 28/03/2013 17:04, Anne van Kesteren a écrit :
The Future has arrived:
http://dom.spec.whatwg.org/#futures
Thanks in particular to the https://github.com/slightlyoff/DOMFuture
project for nailing down all of the details. If someone is interested
in contributing examples the DOM
On Wed, 27 Mar 2013 23:16:11 +0100, Scott Miles sjmi...@google.com wrote:
This is great stuff Mike, thanks for making it available. I think we are
all #facepalm at the notion of self-documenting component files, very
clever.
Hmm. We built the BEM framework for templating with multiple
On Mar 28, 2013 11:45 AM, Dimitri Glazkov dglaz...@google.com wrote:
So. :
rel type: import
spec name:
1) HTML Imports
2) Web Imports
:DG
Makes sense to me!
On Mon, Mar 25, 2013 at 2:48 AM, Dominic Cooney domin...@chromium.orgwrote:
On Sun, Mar 24, 2013 at 3:50 PM, Elliott Sprehn espr...@gmail.com wrote:
On Mon, Mar 18, 2013 at 4:48 AM, Dominic Cooney domin...@chromium.orgwrote:
...
I think the offset{Parent, Top, Left} properties should be
On Wed, Mar 27, 2013 at 2:02 PM, Boris Zbarsky bzbar...@mit.edu wrote:
Scott Miles wrote:
This is a thorny problem, but my initial reaction is that you
threaded the needle appropriately. I don't see how we avoid some
lossiness in this situation.
Note that if you're using
On Thu, Mar 28, 2013 at 12:49 PM, Elliott Sprehn espr...@gmail.com wrote:
On Mon, Mar 25, 2013 at 2:48 AM, Dominic Cooney domin...@chromium.orgwrote:
On Sun, Mar 24, 2013 at 3:50 PM, Elliott Sprehn espr...@gmail.comwrote:
offsetParent is very useful to find your positioned parent, and you're
On 3/28/13 12:55 PM, Elliott Sprehn wrote:
and isPositioned is a bitfield check
That happens to be a WebKit-specific claim, as far as I can tell.
parse the property name
As is this.
But yes, the general claim that the JS APIs for doing this right now are
full of performance fail stands.
+1 on HTML Imports - link ref=import
On Thu, Mar 28, 2013 at 9:44 AM, Brian Kardell bkard...@gmail.com wrote:
On Mar 28, 2013 11:45 AM, Dimitri Glazkov dglaz...@google.com wrote:
So. :
rel type: import
spec name:
1) HTML Imports
2) Web Imports
:DG
Makes sense to
On Thu, Mar 28, 2013 at 11:12 AM, Eric Bidelman ericbidel...@google.com wrote:
+1 on HTML Imports - link ref=import
I am okay with this. Despite it sounding like a front for a shady
criminal organization. I can't complain. I mean, look at Shadow DOM.
:DG
On Mar 28, 2013, at 1:55 AM, Anne van Kesteren wrote:
On Wed, Mar 27, 2013 at 8:16 PM, Arun Ranganathan a...@mozilla.com wrote:
They're very different than data URLs. What's a good use case for making
them cross-origin, that isn't addressed by use of postMessage?
Well, the question we
On Thu, Mar 28, 2013 at 7:22 PM, Arun Ranganathan a...@mozilla.com wrote:
The restriction was due to the (perhaps misguided?) safety assumption that
it was prudent to restrict file references via this scheme to the origin
invoking URL.createObjectURL. The initial proposal was scoped to origin,
19 matches
Mail list logo
