Auto generate MediaFeatureNames, its macros and MediaTypeNames

Auto generate MediaFeatureNames, its macros and MediaTypeNames

As part of the review of https://codereview.chromium.org/171383002/
it was requested that the required static strings for the media features and types will be generated as part of the build system.
This CL implements that request.

BUG=

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

[Yoav Weiss, 2014-03-04 10:19:47]

As discussed on https://codereview.chromium.org/171383002/ , I'm breaking off
the .in files part to this CL

[kenneth.r.christiansen, 2014-03-04 12:09:01]

https://codereview.chromium.org/185533012/diff/1/Source/build/scripts/make_me...
File Source/build/scripts/make_media_features.py (right):

https://codereview.chromium.org/185533012/diff/1/Source/build/scripts/make_me...
Source/build/scripts/make_media_features.py:17: 'RuntimeEnabled': None,  # What
should we do for runtime-enabled features?
I guess when disabled they should be treated like unknown media query features
etc

https://codereview.chromium.org/185533012/diff/1/Source/core/css/MediaTypeNam...
File Source/core/css/MediaTypeNames.in (right):

https://codereview.chromium.org/185533012/diff/1/Source/core/css/MediaTypeNam...
Source/core/css/MediaTypeNames.in:7: braille
I guess you noticed that many of these are deprecated with MQ level 4, not sure
if you should think about the possibility of adding counters for these or
potentially removing in the future?

[Yoav Weiss, 2014-03-04 12:36:08]

On 2014/03/04 12:09:01, kenneth.r.christiansen wrote:
>
https://codereview.chromium.org/185533012/diff/1/Source/build/scripts/make_me...
> File Source/build/scripts/make_media_features.py (right):
> 
>
https://codereview.chromium.org/185533012/diff/1/Source/build/scripts/make_me...
> Source/build/scripts/make_media_features.py:17: 'RuntimeEnabled': None,  #
What
> should we do for runtime-enabled features?
> I guess when disabled they should be treated like unknown media query features
> etc

Yeah, I guess so. Since this only defines the macros enabling creation of the
eval function map,
this is not a concern here. Runtime enabled MQs would be blocked in
MediaQueryExp, and when disabled, parsed as invalid.

> 
>
https://codereview.chromium.org/185533012/diff/1/Source/core/css/MediaTypeNam...
> File Source/core/css/MediaTypeNames.in (right):
> 
>
https://codereview.chromium.org/185533012/diff/1/Source/core/css/MediaTypeNam...
> Source/core/css/MediaTypeNames.in:7: braille
> I guess you noticed that many of these are deprecated with MQ level 4, not
sure
> if you should think about the possibility of adding counters for these or
> potentially removing in the future?

Since this simply defines a single static string for each media type, I didn't
find that crucial. Do you consider it necessary?

[abarth-chromium, 2014-03-04 18:51:38]

lgtm

[Yoav Weiss, 2014-03-04 19:46:27]

The CQ bit was checked by yoav@yoav.ws

[commit-bot: I haz the power, 2014-03-04 19:46:37]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/yoav@yoav.ws/185533012/20001

[commit-bot: I haz the power, 2014-03-05 11:16:28]

Change committed as 168465