Cleanup WebKit prefixed names for classes in css directory.

Cleanup WebKit prefixed names for classes in css directory.

Make sure we don't use prefixed naming inside Blink. The features are still exposed prefixed
to the web, unprefixing them is a different story.

This is part one of the renaming.

R=eseidel@chromium.org, kenneth.r.christiansen@intel.com

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=151418

[kenneth.r.christiansen, 2013-05-29 19:47:27]

lgtm, but it's a big change, easy to miss something

[kenneth.r.christiansen, 2013-05-29 19:47:35]

https://codereview.chromium.org/15797004/diff/1/Source/core/css/CSSRegionRule...
File Source/core/css/CSSRegionRule.idl (right):

https://codereview.chromium.org/15797004/diff/1/Source/core/css/CSSRegionRule...
Source/core/css/CSSRegionRule.idl:32: InterfaceName=WebKitCSSRegionRule
the interface name doesn't need to change here? Doe to it still being
unprefixed?

[darktears, 2013-05-29 19:57:33]

On 2013/05/29 19:47:35, kenneth.r.christiansen wrote:
>
https://codereview.chromium.org/15797004/diff/1/Source/core/css/CSSRegionRule...
> File Source/core/css/CSSRegionRule.idl (right):
> 
>
https://codereview.chromium.org/15797004/diff/1/Source/core/css/CSSRegionRule...
> Source/core/css/CSSRegionRule.idl:32: InterfaceName=WebKitCSSRegionRule
> the interface name doesn't need to change here? Doe to it still being
> unprefixed?

I do not change it. InterfaceName is what JS reflect to the public API as a
name. It's just that the implementation is now in a unprefixed filename. We do
not want to change what we expose for now, unprefixing these things to the
public is different from unprefixing the files.

[darktears, 2013-05-29 19:58:13]

On 2013/05/29 19:47:27, kenneth.r.christiansen wrote:
> lgtm, but it's a big change, easy to miss something

And I divided it in two.

[darktears, 2013-05-29 20:02:56]

On 2013/05/29 19:57:33, darktears wrote:
> On 2013/05/29 19:47:35, kenneth.r.christiansen wrote:
> >
>
https://codereview.chromium.org/15797004/diff/1/Source/core/css/CSSRegionRule...
> > File Source/core/css/CSSRegionRule.idl (right):
> > 
> >
>
https://codereview.chromium.org/15797004/diff/1/Source/core/css/CSSRegionRule...
> > Source/core/css/CSSRegionRule.idl:32: InterfaceName=WebKitCSSRegionRule
> > the interface name doesn't need to change here? Doe to it still being
> > unprefixed?
> 
> I do not change it. InterfaceName is what JS reflect to the public API as a
> name. It's just that the implementation is now in a unprefixed filename. We do
> not want to change what we expose for now, unprefixing these things to the
> public is different from unprefixing the files.

Not sure it was what you asked. When you name a IDL Foo.idl, its implementation
has to be in Foo.h and Foo.cpp. Now as I don't want to expose to the Web the
unprefixed Foo I use InterfaceName to expose the prefixed Foo.

[eseidel, 2013-05-29 20:07:55]

lgtm

I would like haraken or one of the bindings experts to give a lgtm (but that can
be post-commit).  But lgtm2. :)  Since we don't have very good "stable
configuration" coverage yet, it's easy to change what we expose by accident.

I would expect a zillion tests to fail if you missed one as I expect the  tests
use the WEbKIt* names.

[commit-bot: I haz the power, 2013-05-29 20:08:07]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/alexis.menard@intel.com/15797004/1

[darktears, 2013-05-29 20:10:57]

On 2013/05/29 20:07:55, eseidel wrote:
> lgtm
> 
> I would like haraken or one of the bindings experts to give a lgtm (but that
can
> be post-commit).  But lgtm2. :)  Since we don't have very good "stable
> configuration" coverage yet, it's easy to change what we expose by accident.
> 
> I would expect a zillion tests to fail if you missed one as I expect the 
tests
> use the WEbKIt* names.

Indeed it's covered by a bunch of tests. Let's land that through the cq so we're
safe.

[darktears, 2013-05-29 21:14:02]

Committed patchset #1 manually as r151418 (presubmit successful).