Thanks for your reply. What you are thinking of doing sounds like it will be useful, but for a different problem than I was thinking of. And I think none of those ideas will necessarily address the problem I was thinking of.
Your ideas will help with the dynamic changing of a style, to determine which JS code is associated with a style change. That is a difficult problem to address and good solutions will be appreciated. But my problem is about how the browser computes a style property for a particular element regardless of any JS code. There is a static relationship between the styles of each element and other elements it is dependent on, its siblings, parent and children hierarchy. How the browser arrives at a particular static state may involve some dynamic cycling until things stabilize, but that dynamic process is probably irrelevant to anything we might be able to debug. The problem involves inheritance - where does a particular style property get its computed value from? The problem is particularly challenging when relative and auto properties are used. Relative to what specifically? Auto-computed from what inputs? I hope you have some ideas to help address these problems. Thanks. dan On Aug 3, 3:58 pm, johnjbarton <[email protected]> wrote: > We are going to try three things in this area: > break on style-change: we may firefox help for some for this > history: way to zero in on the event > filtered tracing: a automatic log that you filter. > Some start in 1.5 we hope. > > jjb > > On Aug 3, 12:23 pm, liberte <[email protected]> wrote: > > > 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 -~----------~----~----~----~------~----~------~--~---
