- From: Chris Pearce <cpearce@mozilla.com>
- Date: Fri, 19 Aug 2011 15:13:46 +1200
On 19/08/2011 12:01 a.m., Philip J?genstedt wrote: > I think that too much variation in how preload is implemented is also > likely to give compat problems. In > <http://www.w3.org/Bugs/Public/show_bug.cgi?id=12596#c7> I have an > example of what might break when pages inevitably assume that > preload="none" causes the loadedmetadata event to not be fired. This seems a valid reason to change from "should" to "must" for preload. I agree. > If you only allow the internal state to increase, don't you need to > reset it at some point as well? Or is it impossible in your > implementation to use preload="auto" on one load and > preload="metadata" on the next due to this? Oops, that is impossible in our implementation. That's a bug! I'll fix that, thanks for pointing this out. I agree that it we should specify when the preload internal state is updated to prevent this bug in other implementations. Resetting the internal preload state inside the synchronous section of the resource selection algorithm as you suggest is sensible. I agree with you! Cheers, Chris Pearce.
Received on Thursday, 18 August 2011 20:13:46 UTC