On Nov 12, 2013, at 8:12 AM, Dimitri Glazkov dglaz...@chromium.org wrote:
On Sun, Nov 10, 2013 at 6:49 PM, Arthur Barstow art.bars...@nokia.com wrote:
On 11/9/13 3:24 AM, ext Ryosuke Niwa wrote:
Hi all,
We have been discussing cross-orign use case and declarative syntax of web
components
On Tue, Nov 12, 2013 at 12:45 AM, Ryosuke Niwa rn...@apple.com wrote:
[...]
- Script in the import is executed in the context of the window that
contains the importingdocument. So window.document refers to the main
page document. This has two useful corollaries:
- functions
I'm not sure I would want jQuery UI to pollute the window object with
$, with ES6 modules around the corner it seems like a step backwards
for imports to start polluting window objects with their libraries...
On Tue, Nov 12, 2013 at 9:01 PM, Elliott Sprehn espr...@gmail.com wrote:
On Tue, Nov
On Nov 13, 2013, at 7:21 AM, Brian Di Palma off...@gmail.com wrote:
I'm not sure I would want jQuery UI to pollute the window object with
$, with ES6 modules around the corner it seems like a step backwards
for imports to start polluting window objects with their libraries…
Indeed!
On Tue,
pollute the window object with $, with ES6 modules around the corner
The $ was just an example, the import could also happily define one or more
modules. This concept allows us to decouple scoping from imports.
Now, the import is only a vehicle, but it advances the state of the art by
also
On Nov 11, 2013, at 3:56 PM, Adam Barth w...@adambarth.com wrote:
Can you help me understand what security properties your proposal
achieves and how it achieves them? I spent some time thinking about
this problem a couple of years ago when this issue was discussed in
depth, but I couldn't
On Mon, Nov 11, 2013 at 12:57 AM, Ryosuke Niwa rn...@apple.com wrote:
On Nov 11, 2013, at 3:56 PM, Adam Barth w...@adambarth.com wrote:
Can you help me understand what security properties your proposal
achieves and how it achieves them? I spent some time thinking about
this problem a couple
On Nov 11, 2013, at 5:33 PM, Ryosuke Niwa rn...@apple.com wrote:
On Nov 11, 2013, at 5:13 PM, Adam Barth w...@adambarth.com wrote:
On Mon, Nov 11, 2013 at 12:57 AM, Ryosuke Niwa rn...@apple.com wrote:
On Nov 11, 2013, at 3:56 PM, Adam Barth w...@adambarth.com wrote:
Can you help me
On Mon, Nov 11, 2013 at 1:33 AM, Ryosuke Niwa rn...@apple.com wrote:
[...] we’re open to creating a proxy/fake element subclass which is not
visible in the global scope and identical to HTMLKnownElement in its
prototype chain in the host document as well.
Can you clarify why it can't be
On Nov 12, 2013, at 6:22 AM, Elliott Sprehn espr...@gmail.com wrote:
On Mon, Nov 11, 2013 at 1:33 AM, Ryosuke Niwa rn...@apple.com wrote:
[...] we’re open to creating a proxy/fake element subclass which is not
visible in the global scope and identical to HTMLKnownElement in its
prototype
On Sun, Nov 10, 2013 at 6:49 PM, Arthur Barstow art.bars...@nokia.comwrote:
Hi Dimitri, Dominic,
Ryosuke is here in Shezhen at WebApps' f2f meeting. We would like to have
one or both of you join us (via voice conference) on Tuesday morning to
talk about Web Components and his comments below.
for Cross Origin Use Case and Declarative
Syntax
On Sun, Nov 10, 2013 at 6:49 PM, Arthur Barstow
art.bars...@nokia.commailto:art.bars...@nokia.com wrote:
Hi Dimitri, Dominic,
Ryosuke is here in Shezhen at WebApps' f2f meeting. We would like to have one
or both of you join us (via voice conference
Hi Dimitri, Dominic,
Ryosuke is here in Shezhen at WebApps' f2f meeting. We would like to
have one or both of you join us (via voice conference) on Tuesday
morning to talk about Web Components and his comments below.
Please look at the agenda page and let us know your availability for the
Hi Ryosuke,
Can you help me understand what security properties your proposal
achieves and how it achieves them? I spent some time thinking about
this problem a couple of years ago when this issue was discussed in
depth, but I couldn't come up with a design that was simultaneously
useful and
Hi all,
We have been discussing cross-orign use case and declarative syntax of web
components internally at Apple, and here are our straw man proposal to amend
the existing Web Components specifications to support it.
1. Modify HTML Imports to run scripts in the imported document itself
This
15 matches
Mail list logo
