[Webkit-unassigned] [Bug 120640] New: Web Inspector: Request to show *how* a computed property got that value

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Sep 3 10:38:05 PDT 2013


https://bugs.webkit.org/show_bug.cgi?id=120640

           Summary: Web Inspector: Request to show *how* a computed
                    property got that value
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: P2
         Component: Web Inspector
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: dwood at karelia.com
                CC: timothy at apple.com, joepeck at webkit.org,
                    webkit-bug-importer at group.apple.com, graouts at apple.com


I've frequently found myself in a situation where I'm looking at a computed property, wondering how that property got that value.  Was it a specific rule?  If so, which one?  Or is it inherited from some containing element?  If so, which, and what rule?

It would be very useful if one could, say, double-click on any property/value line in the properties list, and have the inspector jump over to the Rules tab, highlighting the specific rule that gives it that value.  Perhaps even changing the selected element so that the rule is properly highlighted for the relevant element.

Perhaps even some sort of popover display to help explain even more.  For instance, if a computed value in in pixels and the rule declares a value in em, it could explain how it came to that calculation.

Anything that might help track down *why* a property has a particular value would be extremely helpful.  Easy for WebKit to know, and hard for a human to try to figure out.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list