Closed Bug 18218 Opened 25 years ago Closed 24 years ago

'inline-table' should not be recognised by CSS parser

Categories

(Core :: CSS Parsing and Computation, defect, P3)

defect

Tracking

()

VERIFIED FIXED

People

(Reporter: ian, Assigned: pierre)

References

Details

(Keywords: css1)

If 'inline-table' is not implemented, then the entire 'display' declaration in
which it occurs should be ignored. That is so that authors can easily work
around this lack of feature. NOTE! THIS IS CURRENTLY A BUG!

i.e., currently, the following:

   SPAN { display: inline; }
   SPAN { display: inline-table; }

...renders the span as 'display:none', but it should render as a simple inline
element. This is due to the forward-compatability parsing rules: if a feature
is not supported, then the declaration should be ignored.

If inline-table is going to be implemented, then this bug is invalid. If it is
not going to be implemented, though, then this should be fixed before release.

'inline-table' support is covered by bug 18217.

[ccing the usual interested parties]
Depends on: 18217
Target Milestone: M20
Status: NEW → ASSIGNED
Keywords: css1
Migrating from {css1} to css1 keyword. The {css1}, {css2}, {css3} and {css-moz}
radars should now be considered deprecated in favour of keywords.
I am *really* sorry about the spam...
Summary: {css1} 'inline-table' should not be recognised by CSS parser → 'inline-table' should not be recognised by CSS parser
Fixed. Like 'compact', 'run-in' and 'marker', a declaration containing 
'display:inline-table' is entirely ignored by the CSS parser.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
As per meeting with ChrisD today, taking QA.
QA Contact: chrisd → py8ieh=bugzilla
VERIFIED Win2K and Linux Comm M18 trunk builds 2000090609.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.