[Webkit-unassigned] [Bug 78985] New: Web Inspector: Audit rules to recommend unprefixing now standard CSS properties

[bugzilla-daemon at webkit.org]

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

           Summary: Web Inspector: Audit rules to recommend unprefixing
                    now standard CSS properties
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: Web Inspector
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: joepeck at webkit.org
                CC: timothy at apple.com, rik at webkit.org, keishi at webkit.org,
                    pmuellr at yahoo.com, joepeck at webkit.org,
                    pfeldman at chromium.org, yurys at chromium.org,
                    bweinstein at apple.com, apavlov at chromium.org,
                    loislo at chromium.org


I think it would be useful to have an audit rule that suggests unprefixing CSS properties if
the standard, unprefixed version, is now supported. I could see:

    .rounded { 
        -webkit-border-radius: 5px;
    }

producing a warning like: (wording could use some work)

  CSS: <a>foo.css:85</a> "-webkit-border-radius" is used, but "border-radius" is supported.

I would expect this to be smart enough to check the entire scope. Since having the prefix'd versions
might still exist in order to support legacy browsers. For example I would not expect a warning for:

  .rounded-with-legacy-support {
      -vender-border-radius: 5px;
      -webkit-border-radius: 5px;
      border-radius: 5px;
  }

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