Bug 15044 - Bulleted headings on www.amicididio.com are formatted incorrectly
Summary: Bulleted headings on www.amicididio.com are formatted incorrectly
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: Evangelism (show other bugs)
Version: 523.x (Safari 3)
Hardware: Mac OS X 10.4
: P2 Normal
Assignee: Nobody
URL: http://www.amicididio.com/cms/
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-22 01:15 PDT by David Ianni
Modified: 2020-10-23 13:30 PDT (History)
1 user (show)

See Also:


Attachments
Partial reduction (1.55 KB, text/html)
2007-08-22 08:58 PDT, David Kilzer (:ddkilzer)
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Ianni 2007-08-22 01:15:38 PDT
This page is shown correctly in Camino and Firefox but not so in Safari which I mainly use.
Comment 1 David Kilzer (:ddkilzer) 2007-08-22 08:58:12 PDT
Created attachment 16069 [details]
Partial reduction

The problem is the "white-space: pre-wrap;" style on the contentheading and contentpagetitle classes.

This causes the white space (newline character and six tabs) before the anchor tag (<a>) to be rendered as-is on the page.

I think this may be an evangelism issue.  The content authors should really be using an unordered list (<ul><li></ul>) or a definition list (<dl><dt><dd></dl>) to create the bulleted list, not tables.
Comment 2 David Kilzer (:ddkilzer) 2007-08-22 09:00:46 PDT
Or if they'd simply remove "white-space: pre-wrap;" from those two styles, that should fix the page as well.

Comment 3 David Kilzer (:ddkilzer) 2007-08-22 09:05:37 PDT
(In reply to comment #2)
> Or if they'd simply remove "white-space: pre-wrap;" from those two styles, that
> should fix the page as well.

The "white-space: pre-wrap;" style needs to be removed from the following classes:

.contentheading
.contentpagetitle
a.contentpagetitle:link, a.contentpagetitle:visited
a.contentpagetitle:hover

Comment 4 David Kilzer (:ddkilzer) 2007-08-22 09:06:36 PDT
David, could you contact the author(s) of the site to let them know about this issue?  This change should not affect the rendering in Firefox 2.0.0.x, although I'm not sure what MSIE 6/7 will do.

Thanks!