Re: [whatwg] Making cross-origin iframe seamless= (partly) usable
On Wed, Dec 5, 2012 at 8:54 AM, Ian Hickson i...@hixie.ch wrote: On Wed, 5 Dec 2012, Jonas Sicking wrote: It seems to me like the best solution is to have a new HTTP header, with the four following values being allowed: Seamless-Options: allow-shrink-wrap Seamless-Options: allow-styling Seamless-Options: allow-shrink-wrap allow-styling Seamless-Options: allow-styling allow-shrink-wrap I guess it depends how costly you think it is to mint new HTTP headers rather than having fewer, harder working headers. I hear no end of people arguing that HTTP headers are too hard for people to use. Could we make these settable through meta elements as well as, or instead of, using headers. The problem is that we need to have the information before we create the Document, since once the Document is created the page might be rendered, and if the information comes after the Document is rendered, there would be flicker (different sizes for the iframes, different styles in the iframes). One solution would be not not render the contained document in the iframe seamless= until we hit the element that opts in to cross-origin seamless rendering. If the document never opts in, it'll never get rendered, but is still loaded. This might be non-trivial to implement though since I believe that unrendered documents is not something that exists in the platform today. The simplest way to emulate it would be to make the iframe act as if it was display:none. / Jonas
Re: [whatwg] Make the files attribute of the input element writable
On Wed, Dec 5, 2012 at 9:11 AM, Ian Hickson i...@hixie.ch wrote: On Wed, 5 Dec 2012, Victor Costan wrote: There was a thread on this mailing list discussing making it possible to set the file data behind an input type=file element. http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2012-May/thread.html#36140 The thread seems to have died down due to insufficient applications for the proposal. Actually the reason this thread hasn't gone anywhere is that there seems to only be implementer interest from Chrome. Actually, I'd be quite interested to see this implemented in Gecko. My only requirement is that something like the following should work: myFileInput.files = [ablob, afile, anotherblob, new Blob([foo])]; / Jonas
Re: [whatwg] Make the files attribute of the input element writable
On 12/15/12 8:39 PM, Jonas Sicking wrote: myFileInput.files = [ablob, afile, anotherblob, new Blob([foo])]; There's no way to express that in WebIDL, but I think that's a bug we should fix in WebIDL. We should allow getters and setters for attributes to accept different IDL types... -Boris
Re: [whatwg] Need to define same-origin policy for WebIDL operations/getters/setters
On 12/15/12 8:33 PM, Jonas Sicking wrote: An easy solution would be to just return null for .contentDocument in the case of cross-origin iframes. Even if that were web-compatible (which is not obvious), that doesn't solve the problem of doing the same sort of thing with .contentWindow. -Boris
Re: [whatwg] Make the files attribute of the input element writable
On 16/12/12 2:05 PM, Boris Zbarsky wrote: There's no way to express that in WebIDL, but I think that's a bug we should fix in WebIDL. We should allow getters and setters for attributes to accept different IDL types... Yeah, that has come up a couple of times now. Filed https://www.w3.org/Bugs/Public/show_bug.cgi?id=20407.
