Bug 56002 – Web Inspector: [STYLES] Editing a property value adds a word for any property value that uses a paren

• Status: RESOLVED
• Resolution: FIXED
• Component: Web Inspector (Deprecated)

[Alexander Pavlov (apavlov)]

1. Open any page
2. Open the webinspector and pick and element
3. In the element style properties, try to add something like:
-webkit-transform: translateZ(0)

You'll notice that the moment you type the open parenthesis the word "initial" appears, greyed out. There is no way to remove that so by the time you're done typing you end up with:
-webkit-transform: translateZ(0)initial

If a property accepts color keywords, you can end up with the word "aliceblue" instead.

Upstreaming http://code.google.com/p/chromium/issues/detail?id=75302

[Alexander Pavlov (apavlov)]

Created attachment 85156 [details]
[PATCH] Suggested fix

[Joseph Pecoraro]

Would the suggestion still affect url()? If you input "url(i" it might suggest initial?
Any way to prevent that, or is it a separate bug I should file a new bug?

[Alexander Pavlov (apavlov)]

(In reply to comment #2)
> Would the suggestion still affect url()? If you input "url(i" it might suggest initial?
> Any way to prevent that, or is it a separate bug I should file a new bug?

I wouldn't call it a bug :) Frankly speaking, we do not parse the current value contents and only offer prefix-based suggestions with all keywords allowed in the current property values (and "initial" is one of the keywords). If that is a real nuisance, feel free to file a bug.

[Alexander Pavlov (apavlov)]

Committing to http://svn.webkit.org/repository/webkit/trunk ...
        M       Source/WebCore/ChangeLog
        M       Source/WebCore/inspector/front-end/StylesSidebarPane.js
Committed r80710

[Joseph Pecoraro]

(In reply to comment #3)
> (In reply to comment #2)
> > Would the suggestion still affect url()? If you input "url(i" it might suggest initial?
> > Any way to prevent that, or is it a separate bug I should file a new bug?
> 
> I wouldn't call it a bug :)

Sure, an enhancement. I filed:
<http://webkit.org/b/56118> Web Inspector: CSS Autocomplete Should Use More Contextual Information

The same can be done for JavaScript, but I think we already have some relevant bugs.
I had a patch for improving getElementById to autocomplete id's, but it never landed.

[Alexander Pavlov (apavlov)]

(In reply to comment #5)
> (In reply to comment #3)
> > (In reply to comment #2)
> > > Would the suggestion still affect url()? If you input "url(i" it might suggest initial?
> > > Any way to prevent that, or is it a separate bug I should file a new bug?
> > 
> > I wouldn't call it a bug :)
> 
> Sure, an enhancement. I filed:
> <http://webkit.org/b/56118> Web Inspector: CSS Autocomplete Should Use More Contextual Information
> 
> The same can be done for JavaScript, but I think we already have some relevant bugs.
> I had a patch for improving getElementById to autocomplete id's, but it never landed.

Good thing -- can you share your thoughts with me, perhaps over email? I'm curious about to what extent you think the input should be analyzed.