Bug 17857

Summary: <wbr> inside a position:absolute block crashes WebKit
Product: WebKit Reporter: Eric Roman <eroman>
Component: CSSAssignee: Nobody <webkit-unassigned>
Status: RESOLVED WORKSFORME    
Severity: Normal CC: webkit, wiktar
Priority: P1    
Version: 523.x (Safari 3)   
Hardware: All   
OS: All   
URL: http://www.holidaycheck.de/laender-reiseinformationen_griechenland-lid_7.html
Attachments:
Description Flags
Test case to reproduce the crash none

Eric Roman
Reported 2008-03-14 15:33:11 PDT
This page crashes in Safari 3.1 beta: http://www.holidaycheck.de/laender-reiseinformationen_griechenland-lid_7.html A reduced test case for the crash is: <html> <style> .kLabel * { position:absolute; } </style> <div class="kLabel"><wbr></div> </body> </html>
Attachments
Test case to reproduce the crash (132 bytes, text/plain)
2008-03-14 15:35 PDT, Eric Roman 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Eric Roman
Comment 1 2008-03-14 15:35:05 PDT
Created attachment 19776 [details] Test case to reproduce the crash Crashed for me in various versions of Safari (including 3.1). Tested on Windows XP
Matt Lilek
Comment 2 2008-03-14 16:10:40 PDT
This doesn't crash in ToT. Probably fixed with the fix for bug 17464.
Eric Roman
Comment 3 2008-03-14 18:44:57 PDT
Actually, I found the exact CL which fixed this (in trunk) http://trac.webkit.org/projects/webkit/changeset/30412 However the problem still remains that this is broken in the Safari 3.1 branch, should I be reporting Safari 3.1 branch bugs somewhere else?
Robert Blaut
Comment 4 2008-03-15 02:26:40 PDT
(In reply to comment #3) > However the problem still remains that this is broken in the Safari 3.1 branch, > should I be reporting Safari 3.1 branch bugs somewhere else? > Please, file a bug report to: http://bugreport.apple.com.
Eric Seidel (no email)
Comment 5 2008-03-17 09:52:19 PDT
Fixing title and priority even though this is closed. This bug already has a Radar associated with it: rdar://problem/5637569 (which is the original radar which prompted the fix). But yes, Eric, if this affects your particular website, or you have other reasons to suggest that Safari should take this as part of 3.1, you'd need to talk to the Apple folks.
Eric Seidel (no email)
Comment 6 2008-03-17 09:53:34 PDT
Given that this was a crashing regression, I would be surprised if they don't fix it with 3.1. But again, I'm not Apple.
Mark Rowe (bdash)
Comment 7 2008-12-15 13:40:08 PST
*** Bug 22864 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.