Proof of concept that CSSPropertyAPI*::parseSingleValue may need more tahn 2 arguments

Proof of concept that CSSPropertyAPI*::parseSingleValue may need more tahn 2 arguments

This patch is just to show a proof of concept that the h file generator
for CSSPropertyAPI* will need to incorporate the fact that
CSSPropertyAPI*::parseSingleValue has three input arguments and not two.

[nainar, 2017-01-20 08:18:30]

nainar@chromium.org changed reviewers:
+ aazzam@google.com, sashab@chromium.org

[nainar, 2017-01-20 08:18:31]

Hi Anna, Sasha 

I was working on a patch to move code for BackgroundComponents over to
CSSPropertyAPIBackgroundComponent. And seems like the template for
parseSingleValue only incorporates CSSParserTokenRange& range, const
CSSParserContext* context. Whereas in this case CSSPropertyID
unresolvedProperty, CSSParserTokenRange& range, const CSSParserContext* context
are the input arguments passed. 

I think either the template needs to be changed or this case needs to forego the
template. Let me know if you need me to explain this to you IRL. 

Thanks!

[aazzam, 2017-01-20 22:53:35]

On 2017/01/20 at 08:18:31, nainar wrote:
> Hi Anna, Sasha 
> 
> I was working on a patch to move code for BackgroundComponents over to
CSSPropertyAPIBackgroundComponent. And seems like the template for
parseSingleValue only incorporates CSSParserTokenRange& range, const
CSSParserContext* context. Whereas in this case CSSPropertyID
unresolvedProperty, CSSParserTokenRange& range, const CSSParserContext* context
are the input arguments passed. 
> 
> I think either the template needs to be changed or this case needs to forego
the template. Let me know if you need me to explain this to you IRL. 
> 
> Thanks!

hey naina!! thanks for taking a look at this :) if you look at my design doc,
you'll see that i've decided that for the (few) properties where unresolved
properties are needed, the alias should be implemented for these properties. if
there is an eventual aim to remove CSSPropertyID's from the codebase, it's
probably best that we dont' pass this in to the API. 

here's my design doc, have a look at the "aliases and shorthand properties"
section, and let me know your thoughts :)
https://docs.google.com/document/d/1R2qiaQJ-SKkTTvnoUkuT9f-dmk5GlhzcvzeQj3iQa...