WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
74730
Web Inspector: Auto-complete transform functions for -webkit-transform
https://bugs.webkit.org/show_bug.cgi?id=74730
Summary
Web Inspector: Auto-complete transform functions for -webkit-transform
Raul Hudea
Reported
2011-12-16 11:17:28 PST
It would be nice to have WebInspector to be able to auto-complete on transforms functions.
Attachments
Patch to add completions to -webkit-transform
(1.41 KB, patch)
2011-12-16 12:08 PST
,
Raul Hudea
no flags
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Raul Hudea
Comment 1
2011-12-16 12:08:35 PST
Created
attachment 119646
[details]
Patch to add completions to -webkit-transform
Pavel Feldman
Comment 2
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.
WebKit Review Bot
Comment 3
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
>
WebKit Review Bot
Comment 4
2011-12-18 08:39:41 PST
All reviewed patches have been landed. Closing bug.
Timothy Hatcher
Comment 5
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?
Pavel Feldman
Comment 6
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.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug