It would be nice to have WebInspector to be able to auto-complete on transforms functions.
Created attachment 119646 [details] Patch to add completions to -webkit-transform
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 on attachment 119646 [details] Patch to add completions to -webkit-transform Clearing flags on attachment: 119646 Committed r103177: <http://trac.webkit.org/changeset/103177>
All reviewed patches have been landed. Closing bug.
(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?
> 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.