I have a recurring problem of finding out where a particular style is
coming from.  That is, when I see a particular element, and one of its
style properties, say its width, what combination of styles are used
to determine what its width is.

Using a combination of showing the computed styles and browsing
through the non-computed view of styles (need a name for that), I can
make some guesses.  Changing the styles in various ways allows me to
experiment to determine what affects the resulting style I am
interested in.   But why all the guesswork?

One easy-to-use feature would be that when viewing the computed
styles, when I mouse over a particular property, show a mouseover
popup of how that style was computed.   If it is a width of, say,
157px, the popup might say that is computed from 50% of a 414px width
container specified by a .myDIV rule in the template.css file, for
example.  If the style is 'auto' computed, then list its immediate
constraints, whether from its parent elements or children elements.
Etc...

This might be difficult to implement, if the browser cannot tell the
debugger this information.  Recreating what the browser already does
could be a difficult task, but think how valuable this would be to the
browser developers as well, for determining whether the specified
mechanism is actually used correctly.

But maybe firefox provides more information than I would guess.  It is
able to identify which style rules have been overridden by other
rules.   Another useful feature: it would be nice to see *which* other
rules are doing the overriding.

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to