::first-line within table wreaks havoc on rest of paragraph

RESOLVED WORKSFORME

Status

()

Core
Layout
RESOLVED WORKSFORME
16 years ago
9 years ago

People

(Reporter: shaver, Assigned: dbaron)

Tracking

(Depends on: 1 bug, {css2})

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [CSS2-5.12.1], URL)

Attachments

(2 attachments)

See test URL: using :first-line within a table cell causes deep weird for the
following text.  Causing a reflow of sufficient disruption (changing text size,
good solid rogering of a resize, etc.) can remedy some but not all of the woes.
(Assignee)

Comment 1

16 years ago
Created attachment 83221 [details]
one of the three parts of shaver's testcase, for the record

Testcase for the record, in case shaver doesn't leave it on the web forever. 
This is just the simplest of the three parts -- it also has a version with
'font-size' and a version with 'font-variant'.

I suspect this could be a problem with ReParentStyleContext.
QA Contact: petersen → ian
Created attachment 92000 [details]
Screenshot of Shaver's blog - repeating link on hover.

Sorry for the spam, is this related to, a DUP of this bug?
FWIW, I don't use tables at all in my blog.
(Assignee)

Comment 4

15 years ago
Re comment 2:  Related, perhaps.  Duplicate, no.
(Assignee)

Comment 5

15 years ago
The bug in comment 2 is now bug 177539.
Keywords: css2
Whiteboard: [CSS2-5.12.1]
(Assignee)

Updated

15 years ago
Depends on: 141265

Updated

14 years ago
OS: Linux → All
Hardware: PC → All
Summary: :first-line within table wreaks havoc on rest of paragraph → ::first-line within table wreaks havoc on rest of paragraph

Comment 6

11 years ago
http://off.net/~shaver/diary/bugs/overlapping-text/
wfm

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a2pre) Gecko/20061231 Minefield/3.0a2pre

Comment 7

9 years ago
-> WFM

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b2pre) Gecko/20081011 Minefield/3.1b2pre
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.