RESOLVED CONFIGURATION CHANGED 26569
Error when not closing a code-element within a p-element 
https://bugs.webkit.org/show_bug.cgi?id=26569
Summary Error when not closing a code-element within a p-element
Doeke Zanstra
Reported 2009-06-20 00:52:39 PDT
When a code-tag within a p-tag is not closed, the document will be code from that part. A test case is included in the URL-field. This bug happens in the real world at this site: http://ejohn.org/blog/unimpressed-by-nodeiterator/ On Mac OS X, Camino 2.0b3 and Firefox 3.5b99 render the text as expected. Opera 9.64 renders the same as Safari/WebKit. The tested WebKit is today's latest: 44862.
Attachments
Test case (386 bytes, text/html)
2009-06-20 00:54 PDT, Doeke Zanstra 		no flags
Details
Safari 15.5 matches other browsers (682.13 KB, image/png)
2022-06-02 21:32 PDT, Ahmad Saleem 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Doeke Zanstra
Comment 1 2009-06-20 00:54:20 PDT
Created attachment 31589 [details] Test case File is the same as http://zanstra.com/x/webkit/code-p.html
Ahmad Saleem
Comment 2 2022-06-02 21:32:11 PDT
Created attachment 459986 [details] Safari 15.5 matches other browsers Based on attached test case, I am unable to reproduce any rendering difference in Safari 15.5 on macOS 12.4 compared to other browsers as shown in the attached test case. If I am looking at it incorrectly or my testing is wrong. Please retest accordingly. Thanks! Although, if it is same rendering across all browsers, then it can be marked as "RESOLVED CONFIGURATION CHANGED", since it got fixed down the line. Thanks!
zalan
Comment 3 2022-06-03 08:09:32 PDT
(In reply to Ahmad Saleem from comment #2) > Created attachment 459986 [details] > Safari 15.5 matches other browsers > > Based on attached test case, I am unable to reproduce any rendering > difference in Safari 15.5 on macOS 12.4 compared to other browsers as shown > in the attached test case. > > If I am looking at it incorrectly or my testing is wrong. Please retest > accordingly. Thanks! > > Although, if it is same rendering across all browsers, then it can be marked > as "RESOLVED CONFIGURATION CHANGED", since it got fixed down the line. > Thanks! Looks good! Thank you!
Note You need to log in before you can comment on or make changes to this bug.