On Mon, Apr 21, 2014 at 08:53:54AM +0000, Karl Dahlke wrote: > Adam writes: > > I think in this case it is expected that the script element is placed (and > > thus > > executed) in the DOM just as it would be if it was done in the html. > > Perhaps, but in this case, Amazon.com, the script element is added > to the head section, which is about 1000 lines in the past. > It is not placed in some tag in the future. > Since we don't have time travle, > the best we can do is to execute the script right now. > I guess, it's all rather merky.
Yeah, that's seriously weird. I fail to see how this is expected to work, since even if the DOM is created first then script elements executed in the order they appear, the addition of an extra script element in the head section after that part of the DOM has had all its script elements executed would be a bit pointless. The only way this could possibly work without invoking the script out of place would be to re-check the DOM on each update executing new script elements. This just sounds like a bit of a recipe for disaster. Before doing anything with this I'd be tempted to look at how other browsers handle this case, assuming it's not just a bug in amazon's page which no one has noticed yet. Cheers, Adam.
signature.asc
Description: Digital signature
_______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
