On 18 July 2013 23:28, Kyle Simpson get...@gmail.com wrote:
About a week ago, I presented a set of code comparing the script
dependencies=.. approach to the script preload approach, as far as
creating generalized script loaders.
There were a number of concerns presented in those code
On 12 July 2013 20:12, Ian Hickson i...@hixie.ch wrote:
On Fri, 5 Apr 2013, Jake Archibald wrote:
Been reading the steps for image downloading -
http://www.whatwg.org/specs/web-apps/current-work/multipage/embedded-content-1.html#update-the-image-data
...
Unless I'm reading it wrong, that
On Thu, 20 Dec 2012, Rik Cabanier wrote:
On Thu, 20 Sep 2012, Dirk Schulze wrote:
On Sep 21, 2012, at 3:12 AM, Ian Hickson i...@hixie.ch wrote:
The only situation that might be reasonable would be a transform
on the Canvas that an author want to cover in the Path. But for
the
On Tue, Jul 9, 2013 at 12:39 PM, Ian Hickson i...@hixie.ch wrote:
The proposals I've seen so far for extending the spec's script preloading
mechanisms fall into two categories:
- provide some more control over the mechanisms already there, e.g.
firing events at various times, adding
FWIW, I'd be much more in favor of Jonas' proposal, at this point, than the
dependencies=.. proposal. The `noexecute/execute()` is conceptually pretty
similar to the preload proposal I've been pushing. As far as I can tell from
how Jonas describes it, it looks like it would fit most of the
On Mon, Jul 22, 2013 at 2:35 PM, Kyle Simpson get...@gmail.com wrote:
FWIW, I'd be much more in favor of Jonas' proposal, at this point, than the
dependencies=.. proposal. The `noexecute/execute()` is conceptually pretty
similar to the preload proposal I've been pushing. As far as I can tell
Do you have a link to your preload proposal?
My main `script preload` proposal (skip the first section of this LONG email,
proposal starts at Summary: several paragraphs down):
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2013-July/039973.html
Then proposal slightly amended here:
When an element goes fullscreen, should the browser try to retain the
layout of the underlying document, e.g., by creating a placeholder for
the element?
With the top layer, it's possible to style the fullscreened element and
::backdrop such that the underlying document is visible. In such a
On Mon, Jul 22, 2013 at 4:01 PM, Kyle Simpson get...@gmail.com wrote:
Do you have a link to your preload proposal?
My main `script preload` proposal (skip the first section of this LONG
email, proposal starts at Summary: several paragraphs down):
