Bug 74730

Summary: Web Inspector: Auto-complete transform functions for -webkit-transform
Product: WebKit Reporter: Raul Hudea <rhudea>
Component: Web Inspector (Deprecated)Assignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: apavlov, bweinstein, joepeck, keishi, loislo, pfeldman, pmuellr, rik, timothy, webkit.review.bot, yurys
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
Attachments:
Description Flags
Patch to add completions to -webkit-transform none

Description Raul Hudea 2011-12-16 11:17:28 PST 
It would be nice to have WebInspector to be able to auto-complete on transforms functions.
Comment 1 Raul Hudea 2011-12-16 12:08:35 PST 
Created attachment 119646 [details]
Patch to add completions to -webkit-transform
Comment 2 Pavel Feldman 2011-12-18 06:15:20 PST 
Comment on attachment 119646 [details]
Patch to add completions to -webkit-transform

This file was once generated, I wonder if we need to re-run generator now.
Comment 3 WebKit Review Bot 2011-12-18 08:39:36 PST 
Comment on attachment 119646 [details]
Patch to add completions to -webkit-transform

Clearing flags on attachment: 119646

Committed r103177: <http://trac.webkit.org/changeset/103177>
Comment 4 WebKit Review Bot 2011-12-18 08:39:41 PST 
All reviewed patches have been landed.  Closing bug.
Comment 5 Timothy Hatcher 2011-12-18 09:20:28 PST 
(In reply to comment #2)
> (From update of attachment 119646 [details])
> This file was once generated, I wonder if we need to re-run generator now.

Why can't this be part of the CSSAgent.getSupportedCSSProperties call?
Comment 6 Pavel Feldman 2011-12-18 09:44:04 PST 
> Why can't this be part of the CSSAgent.getSupportedCSSProperties call?

I am not a great fan of the CSSAgent.getSupportedCSSProperties. Considering inspector front-end an IDE-alike tool that attaches to browsers, it should be well aware of all kinds of properties for all kinds of browsers (not only WebKit). So my view of the world is a number of css property names with potential values for particular browsers defined in the JSON form on the front-end side. I believe Alexander was going to generate front-end structures instead of using the native generator for CSSAgent.getSupportedCSSProperties.

Having said that, a protocol method that would list CSS properties backend supports sounds cool. It is just that I don't know where I would apply it today.