On 02/09/2010 09:11 AM, Kent Briggs wrote: >> I was thinking that those two issues, being html5 realated (p element) >> could be an issue by a client that is checking the code. Perhap IE is >> ignoring it... > > I suspect it's script related because I noticed I can click the Stop > button a few seconds after entering the URL and it gets the whole page > rendered and then appears to work fine.
I suspect you are correct. Just opened in IE8 and notice the little error sign in lower left status bar, opened it and it's showing: 'Node' is undefined toc.js URI: http://www.whatsg.org/specs/web-apps/current-work/toc.js "Object doesn't support this property or method" status.js URI: http://www.whatsg.org/specs/web-apps/current-work/status.js reviewer.js URI: http://www.whatsg.org/specs/web-apps/current-work/reviewer.js dfn.js URI: http://www.whatsg.org/specs/web-apps/current-work/dfn.js Also note that in IE you don't get the 'Last call for comments' notices, example: <http://www.whatwg.org/specs/web-apps/current-work/complete.html#elements-0> So that somewhat confirms my suspicion that IE is simply ignoring those scripts & hence the reason for loading/viewing faster. Note that the same occurs if you use the 'Stop' button in SM or Fx. In SM using the error console (Ctrl-Shift-J in both Fx and SM) shows 7 warnings. Mostly 'Error in parsing... Declaration dropped'. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
