Last Comment Bug 649119 - remove parsing and storage of CSS 2.0 aural style sheet properties
: remove parsing and storage of CSS 2.0 aural style sheet properties
: dev-doc-complete
Product: Core
Classification: Components
Component: CSS Parsing and Computation (show other bugs)
: Trunk
: All All
P4 normal (vote)
: mozilla6
Assigned To: David Baron :dbaron: ⌚️UTC-8
: Jet Villegas (:jet)
Depends on:
Blocks: 264517
  Show dependency treegraph
Reported: 2011-04-11 14:08 PDT by David Baron :dbaron: ⌚️UTC-8
Modified: 2011-04-30 16:19 PDT (History)
6 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---

patch (57.52 KB, patch)
2011-04-11 14:49 PDT, David Baron :dbaron: ⌚️UTC-8
bzbarsky: review+
Details | Diff | Splinter Review

Description User image David Baron :dbaron: ⌚️UTC-8 2011-04-11 14:08:09 PDT
We currently parse and store the CSS 2.0 aural style sheet properties.  We've never computed the values, though (bug 47159), which means they're not useful for anything.  The support we have is also way off from the current approach to aural CSS at .

This code is getting in the way of cleaning up nsComputedDOMStyle (bug 264517), because I'd like to be able to assume that we have computed style implementations for all properties we support.
Comment 1 User image David Baron :dbaron: ⌚️UTC-8 2011-04-11 14:49:24 PDT
Created attachment 525181 [details] [diff] [review]
Comment 2 User image Boris Zbarsky [:bz] (still a bit busy) 2011-04-21 08:18:02 PDT
Comment on attachment 525181 [details] [diff] [review]

Comment 3 User image David Baron :dbaron: ⌚️UTC-8 2011-04-21 20:25:34 PDT
Comment 4 User image Jean-Yves Perrier [:teoli] 2011-04-24 01:12:57 PDT
I've added the dev-doc-needed flag as there was some documentation about this in the MDC.

See (non exhaustive list):

I think Aural should be replaced by a text saying it is deprecated and the pages for azimuth should be simply atomized.

We'll see what Sheppy thinks about this.
Comment 5 User image Eric Shepherd [:sheppy] 2011-04-24 18:33:32 PDT
Here's what I've done:

Updated with a compatibility table that explains the state of support in Firefox; also added a note that the page needs updating, and tagged it as such as well.

Also added a note to Firefox 6 for developers.

Note You need to log in before you can comment on or make changes to this bug.