Bug 18124

Summary:

Unclosed noscript element prevents Webkit from rendering a page

Product:

WebKit

Reporter:

Bertrand Presles <bpresles>

Component:

DOM

Assignee:

Adam Barth <abarth>

Status:

RESOLVED CONFIGURATION CHANGED

Severity:

Normal

CC:

abarth, ahmad.saleem792, ap, bfulgham, eric, gsnedders, rniwa, webkit

Priority:

Keywords:

HasReduction

Version:

528+ (Nightly build)

Hardware:

Mac

OS:

OS X 10.5

URL:

http://www.spa.asso.fr/

Attachments:

Description	Flags
test case	none
Safari 15.6 matches with other browsers	none

Bertrand Presles

Reported 2008-03-26 14:40:36 PDT

This website doesn't display at all in Safari (even with latest Webkit nightly). I don't know if it's for the similar reasons than the bug #15136

Attachments
test case (88 bytes, text/html) 2008-03-26 16:23 PDT, Robert Blaut	no flags	Details
Safari 15.6 matches with other browsers (483.92 KB, image/png) 2022-08-09 10:10 PDT, Ahmad Saleem	no flags	Details
View All Add attachment proposed patch, testcase, etc.

Robert Blaut

Comment 1 2008-03-26 16:22:30 PDT

This specific code: <noscript><noscript></noscript>This text is visible in Opera and Firefox make problem in Webkit only.

Robert Blaut

Comment 2 2008-03-26 16:23:34 PDT

Created attachment 20102 [details] test case

Alexey Proskuryakov

Comment 3 2012-02-03 17:26:38 PST

This works now. Should a regression test be landed for this, or do html5 tests cover it already?

Adam Barth

Comment 4 2012-02-03 17:51:05 PST

We might as well add a test. It's easy to test.

Ahmad Saleem

Comment 5 2022-08-09 10:10:26 PDT

Created attachment 461507 [details] Safari 15.6 matches with other browsers I am unable to reproduce this bug in Safari 15.6 and it matches with all other browsers as can be seen from attached screenshots. As for test cases, I was not able to find unclosed script tag on WPT. I might be wrong and need some help to find the exact. gsnedders@apple.com - Any help?

Ryosuke Niwa

Comment 6 2022-08-09 10:21:35 PDT

This seems config changed to me.

Note You need to log in before you can comment on or make changes to this bug.