Bug 12356

Summary:

Whitespace handling inconsistency bug

Product:

WebKit

Reporter:

Jeppe Utzon <jeppe>

Component:

New Bugs

Assignee:

Nobody <webkit-unassigned>

Status:

RESOLVED FIXED

Severity:

Normal

Priority:

Version:

418.x

Hardware:

Mac

OS:

OS X 10.4

URL:

http://www.utzon.com/sww/

Attachments:

Description	Flags
A reduced set of xhtml and css files	none

Jeppe Utzon

Reported 2007-01-21 19:00:48 PST

The bug seems to have something to do with the way Safari 2.0.4 handles the combination of a monospace font, word-spacing set to 1px, a strong-tag, and preceeding whitespace just after a td-tag. Basically I discovered an inconsistency in the way Safari renders the whitespace in this case.

Attachments
A reduced set of xhtml and css files (2.49 KB, application/zip) 2007-01-21 19:03 PST, Jeppe Utzon	no flags	Details
View All Add attachment proposed patch, testcase, etc.

Jeppe Utzon

Comment 1 2007-01-21 19:03:38 PST

Created attachment 12594 [details] A reduced set of xhtml and css files

David Kilzer (:ddkilzer)

Comment 2 2007-01-21 19:22:47 PST

Jeppe, thanks for filing this bug with a reduced test case! Could you try testing your reduced test case against a WebKit Nightly build? http://nightly.webkit.org/ No installation is required--just mount the DMG and double-click on the gold Safari icon.

Jeppe Utzon

Comment 3 2007-01-21 20:09:02 PST

Hello David. I just tested it with the latest build (WebKit-SVN-r19016.dmg Mon Jan 22 1:05:17 GMT 2007) which is 2.0.4 (419.3) and it seems to have solved the problem. Tried altering the code a few times to see if I could make the bug manifest itself again but no "luck". So it seems it's taken care of already. Sorry about that.

David Kilzer (:ddkilzer)

Comment 4 2007-01-21 20:19:35 PST

(In reply to comment #3) > Hello David. I just tested it with the latest build (WebKit-SVN-r19016.dmg Mon > Jan 22 1:05:17 GMT 2007) which is 2.0.4 (419.3) and it seems to have solved the > problem. Tried altering the code a few times to see if I could make the bug > manifest itself again but no "luck". So it seems it's taken care of already. > Sorry about that. Not a problem! See Bug 12199 Comment #3 for speculation on when this may be fixed in shipping Safari.

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