Bug 14633 - Reference to a non-existant CSS causes incorrect layout
Summary: Reference to a non-existant CSS causes incorrect layout
Status: RESOLVED WORKSFORME
Alias: None
Product: WebKit
Classification: Unclassified
Component: CSS (show other bugs)
Version: 523.x (Safari 3)
Hardware: PC Windows XP
: P2 Normal
Assignee: Nobody
URL: http://just1gb.googlepages.com/tech_w...
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-16 10:51 PDT by Sridhar Gurivireddy
Modified: 2008-02-09 14:07 PST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sridhar Gurivireddy 2007-07-16 10:51:45 PDT
In the example below, have a reference to a non-existant CSS files causes Safari to get the incorrect layout. Removing the reference to CSS fixes it.

<html>

<head>
<link href="http://www.doesnotexist.com/eng/ddd/techpubs/zippy/zippy.css" type="text/css" rel="stylesheet">
</head>

<body bgcolor="white">

<table border="0" width="95%" align="center" summary="Header table">
  <tr style="background-color: #FFFFFF;">
    <td>
      <div> Engineering<br> Technical Writers' Corner</div>
    </td>

  </tr>
</table>

</body>

</html>
Comment 1 mitz 2007-07-16 15:17:44 PDT
This is done deliberately in order to avoid rendering unstyled content. When the request for the stylehseet times out, the page finally renders (without style).
Comment 2 Sridhar Gurivireddy 2007-07-16 16:03:27 PDT
That still does not explain why the page renders differently without style and with <non_existant> style
Comment 3 mitz 2007-07-16 23:02:57 PDT
(In reply to comment #2)
> That still does not explain why the page renders differently without style and
> with <non_existant> style
> 

Can you attach a screenshot of the different renderings? With the latest WebKit, I get the same results, eventually.
Comment 4 Sridhar Gurivireddy 2007-07-20 14:02:02 PDT
In which case, a user would expect the same result for these 2 files
1) without the invalid CSS reference
2) with invalid CSS reference
Comment 5 Alexey Proskuryakov 2007-07-21 02:28:08 PDT
I also cannot reproduce this issue (although I'm testing on a Mac). Please attach screenshots of both renderings.
Comment 6 David Kilzer (:ddkilzer) 2007-07-21 08:04:57 PDT
(In reply to comment #4)
> In which case, a user would expect the same result for these 2 files
> 1) without the invalid CSS reference
> 2) with invalid CSS reference

How long did you wait?  Did you wait until the loading for the invalid CSS reference completed?

Comment 7 Robert Blaut 2008-02-09 14:07:06 PST
I cannot confirm this bug as well in Webkit r30090.