RESOLVED WORKSFORME5908
<img> should start implied rendering of <body> when no <body> tag present 
https://bugs.webkit.org/show_bug.cgi?id=5908
Summary <img> should start implied rendering of <body> when no <body> tag present
Samuel Sidler
Reported 2005-12-01 12:24:28 PST
The URL is a testcase. Please see Mozilla bug 318365: https://bugzilla.mozilla.org/show_bug.cgi?id=318365
Attachments
Add attachment proposed patch, testcase, etc.
Joost de Valk (AlthA)
Comment 1 2006-02-07 14:22:10 PST
Marking as wontfix for the same reasons as the referred mozilla bug was marked as invalid: we're matching IE behavior here, and that's goog enough.
Samuel Sidler
Comment 2 2006-02-07 14:44:32 PST
(In reply to comment #1) > Marking as wontfix for the same reasons as the referred mozilla bug was marked > as invalid: we're matching IE behavior here, and that's goog enough. > Did you even read that bug? The bug notes that Safari/webkit is not starting an implied <body> tag at the presence of an <img> tag. The Mozilla bug was marked INVALID because *they* were matching IE's behavior. Webkit, however, is not. This is still a valid bug. Reopening.
Samuel Sidler
Comment 3 2006-02-07 14:44:58 PST
CCing Joost, since he's the one who closed this bug.
Joost de Valk (AlthA)
Comment 4 2006-02-08 11:42:58 PST
I did read it but it must have been late, soz, confirming now :)
David Kilzer (:ddkilzer)
Comment 5 2007-01-06 04:15:57 PST
Using Hixie's Live DOM Viewer, it appears that an implicit <body> tag is being created if you paste the contents of the URL into the top window (or if you just paste "<img>" in there). http://software.hixie.ch/utilities/js/live-dom-viewer/ Tested with a locally-built debug build of WebKit r18636 with Safari 2.0.4 (419.3) on Mac OS X 10.4.8 (8L127).
David Kilzer (:ddkilzer)
Comment 6 2007-01-06 04:17:49 PST
Also, the DOM Inspector in ToT WebKit shows a <body> element has been created after loading this URL: data:text/html,<img>
Alexey Proskuryakov
Comment 7 2012-08-14 16:19:35 PDT
This has been fixed long ago.
Note You need to log in before you can comment on or make changes to this bug.