>
>
> A script could then tell the system to add this element /
> HTMLImageElement object as one of the dependencies for a script it was
> injecting, so that that script doesn't run until the image is downloaded.
> (Doing this, assuming the script is then told to run immediately, would be
> anothe
On Fri, 23 May 2014, Matthew Robb wrote:
>
> I think this is a great discussion and it would be cool if it could get
> mirrored to the other working groups (specifically esdiscuss).
Assuming you mean this thread, it is. :-) (If you meant the HTML spec
discussion regarding needs="" and company, t
On 5/23/14, Ian Hickson wrote:
> On Fri, 23 May 2014, Ryosuke Niwa wrote:
>> On May 23, 2014, at 3:14 PM, Ian Hickson wrote:
>> >
Hi guys -
>> > -
I think this is a great discussion and it would be cool if it could get
mirrored to the other working groups (specifically esdiscuss).
It would be great if WebComponents used the Loader and thus you could
easily import a component into an es6 module and you could build a
component that is entirely
On Fri, 23 May 2014, Ryosuke Niwa wrote:
> On May 23, 2014, at 3:14 PM, Ian Hickson wrote:
> >
> > -
> I would therefore like to propose that we integrate these so that we end
> up with just one system that manages all three.
>
> What do people think?
Absolutely. I've been meaning to start a similar discussion on the w3c
lists, but I don't think I have quite the breadth of knowledge required.
T
Right now there appear to be three separate efforts to develop dependency
systems for the Web platform:
- ES6 Modules
- HTML Imports
-
Le 22 mai 2014 à 23:58, Claude Pache a écrit :
> Hi,
>
> Today, I came to a case where I wanted to grab a reference to some getter of
> the DOM,
> but to not fail if it doesn't exists:
>
> ```javascript
> try {
>originalElementsGetter =
> Object.getOwnPropertyDescriptor(window.HTMLFormEl
8 matches
Mail list logo
