CSS doesn't behave as previous versions

VERIFIED INVALID

Status

()

Core
CSS Parsing and Computation
P3
minor
VERIFIED INVALID
19 years ago
19 years ago

People

(Reporter: Mark Nottingham, Assigned: Pierre Saslawsky)

Tracking

Trunk
x86
Windows NT
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: waiting for more info from reporter, URL)

(Reporter)

Description

19 years ago
This sequence on the above page:
  <P class="trailer">
  <A href="/" class="traileritem"> top </a> &nbsp;
  <A href="/bookmarks/" class="traileritem"> bookmarks </a> &nbsp;
  <A href="/contact/" class="traileritem"> contact </a> &nbsp;
  </P>
when using these relavent styles:
.trailer {
  font-family: sans-serif;
  font-weight: lighter;
  font-size: 10pt;
  text-align: right;
  word-spacing: 1.8em;
  margin: 24pt 0pt 24pt 0pt;
  padding: 3px 0px 0px 72px;
  border-color: black;
  border-style: solid;
  border-width: 0px 0px 1px 0px;
  float: right;
  clear: both;
}
.traileritem {
  font-family: sans-serif;
  font-weight: lighter;
  font-size: 10pt;
}

doesn't render correctly in M10; contrast output with that of Navigator 4.x or
IE4/5.

Thanks,

Comment 1

19 years ago
Tried with 1999-10-15-11-M11 on Windows NT.
The page appeared with no CSS at all within a second, and
a second later changed to match the appearance it gets from
Navigator 4.7. Exactly what one would expect if the stylesheet,
linked in with LINK, has to wait its turn from an HTTP 1.0 server,
and the browser is able to render the page before the stylesheet arrives.

M10 may well have failed to use the stylesheet, but the present behaviour
seems OK.

It begs the question, though: should there be a short delay to wait for the
LINKed stylesheet, counting perhaps 4-5 seconds from the first GET,
non-renewable, so that short pages do not get rendered twice, once without
and once with stylesheet mojo?
(Assignee)

Comment 2

19 years ago
Reassigning peterl's bugs to myself.
(Assignee)

Comment 3

19 years ago
Mark, what do you mean by "doesn't render correctly"? Do you refer to the fact
that the page is rendered in two passes, or have you seen another problem?

Note that the display isn't the same as in other browsers because the
"float:right" declaration is supported by Gecko and ignored by the other ones.
(Assignee)

Updated

19 years ago
Whiteboard: waiting for more info from reporter
(Assignee)

Updated

19 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → INVALID
(Assignee)

Comment 4

19 years ago
Per email from Mark <mnot@pobox.com> who reported the bug, I'm closing this as
Invalid. I opened #17309 ("Wait for primary style sheets before constructing
frames") to track down the issue with the rendering that is done in 2 passes.

Updated

19 years ago
Status: RESOLVED → VERIFIED

Comment 5

19 years ago
Verified invalid
You need to log in before you can comment on or make changes to this bug.