See section 6.4.3 of the CSS2 spec http://www.w3.org/TR/CSS2/cascade.html#specificity --ed
On Sep 8, 10:01 am, ColinFine <[email protected]> wrote: > On Sep 8, 6:12 am, John J Barton <[email protected]> wrote:> On Sep > 7, 4:00 pm, bsmither <[email protected]> wrote: > > > > I have a need to debug CSS-derived displays. The issue can be asked, > > > "Why is that CSS rule taking priority over this rule?" > > > What is a "priority"? > > I think he's talking about the cascade: he would like FB to show in > some way why this rule took precedence over that rule (I would like > this too). > > > > > > Also, as a bonus, a click on the score would delineate exactly how > > > that score was achieved in terms of specificity (or whatever). > > This confirms it: specificity is part of the cascade. > > I don't know whether this information is available to FB, or whether > FF just gives you the effective rules; but the fact that you display > overridden items crossed out suggests that the information might be > available. Alternatively, FB could have its own set of cascade rules > and apply them; but what would happen if it disagreed with the > browser? > > > > > > Also, as *really* special bonus, drag-n-drop (copy) a low-priority CSS > > > rule above a higher priority rule and automatically rewrite the > > > selector with the proper specificity. (I know this is badly expressed, > > > but maybe a think-tank can make something of it.) > > I agree that this would be useful, but I can't see a way to express it > (never mind implement it). There are no free variables in the cascade, > other than !IMPORTANT. -- You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/firebug?hl=en.
