Bug 13604 - CSS Justify/Word-spacing/table bug
Summary: CSS Justify/Word-spacing/table bug
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: 523.x (Safari 3)
Hardware: Macintosh OS X 10.4
: P2 Normal
Assignee: Nobody
URL: http://utzon.com/WK13604/index.html
Keywords: HasReduction
Depends on:
Blocks: 47141
  Show dependency treegraph
 
Reported: 2007-05-06 10:47 PDT by Jeppe Utzon
Modified: 2013-06-01 02:07 PDT (History)
2 users (show)

See Also:


Attachments
Example code (1.02 KB, text/html)
2007-05-06 10:49 PDT, Jeppe Utzon
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jeppe Utzon 2007-05-06 10:47:05 PDT
Stumbled upon a funky wierdness in WebKit. If I have some CSS that defines both "justify" and "word-spacing" and then put some text in a "td", then it behaves as expected (in the nightly) - UNLESS the words are individually wrapped in "a href" tags. If that is done, then the words jump out of the "td" - they spill out of it on the right hand side. Not sure how good an explanation this is, but I've included some example code that shoud make it obvious.

In the example I have a basic page with two tables - each of which have just a single "td" inside. In the top table I have just normal text (without any links) and it behaves as expected. In the bottom table, however, I have wrapped every word in a link and this makes the content of the "td" spill out of it to the right.

So basically the two tables/tds look very different from each other when they should look the same (except for the link decoration). In Firefox both tables behave as they should.

HTH... :)

/Jeppe Utzon
Comment 1 Jeppe Utzon 2007-05-06 10:49:35 PDT
Created attachment 14375 [details]
Example code
Comment 2 mitz 2007-05-06 12:13:58 PDT
Good reduction!
Comment 3 Robert Hogan 2012-03-11 03:22:31 PDT
This doesn't look broken any more. Can you confirm?
Comment 4 Jeppe Utzon 2012-03-11 04:41:07 PDT
(In reply to comment #3)
> This doesn't look broken any more. Can you confirm?

Confirmed. Works correctly now AFAICT. Thanks.
Comment 5 Robert Hogan 2012-03-11 06:44:45 PDT
We should land the test from this bug before closing I guess.