On 23/02/2011, at 04:57, Boris Zbarsky wrote:
On 2/22/11 10:42 PM, Glenn Maynard wrote:
Including execute() being synchronous, raising SyntaxError exceptions
for parse errors, and uncaught exceptions from the script being
propagated up through execute() to its caller?
Hmm. That last one
Hi Rich,
On Wed, Feb 16, 2011 at 6:03 PM, Rich Tibbett ri...@opera.com wrote:
We are also trying a different approach but we're not really coming up
with anything other than modal dialogs, no-authorization models or policies;
none of which are suitable for different reasons. One option that
On Wed, Feb 23, 2011 at 10:16 AM, Jorge jo...@jorgechamorro.com wrote:
On 23/02/2011, at 04:57, Boris Zbarsky wrote:
On 2/22/11 10:42 PM, Glenn Maynard wrote:
Including execute() being synchronous, raising SyntaxError exceptions
for parse errors, and uncaught exceptions from the script being
I don't understand why the preloading specifically would imply different
HTTP caching semantics than normal dynamic script loading?
It doesn't have to. It's just that if preloading is easy to trigger by
accident and authors don't notice when they accidentally preload lots of
stuff then we may
3. My (and Nicholas's previous) proposal: Script elements are fetched
when
inserted into the DOM[1]. An event is dispatched when the script has
been
fetched, eg. onfetch or onpreload[2]. A preload attribute is
added;
when true, the script will not be executed when the fetch completes; call
On 2/23/11 4:16 AM, Jorge wrote:
Wouldn't this :
HTMLScriptElement.prototype.execute= function execute () {
// ...
return (1, eval)( this.innerText ); // global eval
}
do it ?
No. First of all, the script can be an external script, so innerText
doesn't do the right thing.
(only
On 2/23/11 8:33 AM, Kyle Simpson wrote:
I'm curious if we could apply some limit to the number of scripts that
will be simultaneously preloaded, at say 100 scripts for instance?
I would be fine with that from an implementation standpoint; not sure
about the author-facing aspect of it.
On 2/23/11 9:14 AM, Kyle Simpson wrote:
The goal (from my perspective) is to come up with the simplest proposal
that serves the use-cases. Simplest being defined in this particular
situation as the least amount of change to the spec, AND the least
amount of change to the browser that has by far
Le 23 févr. 2011 à 17:03, Martin Stender a écrit :
I've been searching the archives for some discussions about the need for a
dedicated banner-tag, but found only some WAI-related discussions about using
the 'role'-attribute for this.
banner tag proposed by Daniel Glazman? at the time of
On 2/23/11, Martin Stender mar...@stender.com wrote:
So it would be great to have the ability to just insert a banner-tag,
knowing that whatever goes on in side that tag, cannot alter the page
itself.
You should be able to grant the tag access to read various values of the
surrounding page,
I'm curious if we could apply some limit to the number of scripts that
will be simultaneously preloaded, at say 100 scripts for instance?
I would be fine with that from an implementation standpoint; not sure
about the author-facing aspect of it.
As one of the concerned web-authors, I can't
For consistency with other lists of things (such as Files), would it make
sense to rename DataTransferItems to DataTransferItemList? It makes it
easier to distinguish from DataTransferItem as welll.
Daniel
Sorry, I've been traveling and out of the loop for a bit. Just catching up on
the thread.
One thing I want to throw out there: the proposals I put together were intended
to start a discussion, not to end it. If there are parts that could be changed
to make implementation easier, then let's
On Wed, Feb 23, 2011 at 2:12 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
I know that iframes don't stop the rest of the page from rendering
while they load. I can't recall off the top of my head whether they
delay the load event or not.
It seems yes:
When there is an active parser in the
Again, I think the spirit we all share is to find the simplest proposal
that gets the job done, and introducing a new .execute() concept raised
more questions than it purported to solve.
The last dozen or two messages were regarding your rabbit hole, which
raised serious issues.
Serious
On Wed, Feb 23, 2011 at 11:53 PM, Aryeh Gregor simetrical+...@gmail.com wrote:
On Wed, Feb 23, 2011 at 2:12 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
I know that iframes don't stop the rest of the page from rendering
while they load. I can't recall off the top of my head whether they
16 matches
Mail list logo
