Add support for additional blend modes to SVGFEBlendElement

Add support for additional blend modes to SVGFEBlendElement

New modes to be supported are:

  overlay,
  color-dodge,
  color-burn,
  hard-light,
  soft-light,
  difference,
  exclusion,
  hue,
  saturation,
  color and
  luminosity

Since the new modes don't have any corresponding IDL constants exposed
on the SVGFEBlendElement interface, a mechanism is added to be able to
differentiate between "internal" and "exposed" enumeration values, and
reject those that are "internal-only" from being read or written
through SVGAnimatedEnumeration.

Test feBlend-all-modes.html evolved from test in WebKit commit
http://trac.webkit.org/changeset/170433 by Dirk Schulze.

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

[Erik Dahlström (inactive), 2014-08-07 09:33:45]

Just a rebase of https://codereview.chromium.org/435623002/. Not sure how (or if
it's possible) to credit fs for the patch commit using codereview/CQ.

[pdr., 2014-08-07 17:37:23]

On 2014/08/07 09:33:45, Erik Dahlström wrote:
> Just a rebase of https://codereview.chromium.org/435623002/. Not sure how (or
if
> it's possible) to credit fs for the patch commit using codereview/CQ.

LGTM.

You can upload a patch to an existing review by running "git cl issue [issue
number]" and then uploading with "git cl upload". I don't knoe of a way to
credit fs with this patch though. I agree that the chromium address limitation
is ridiculous :( Can you comment on the bug about it to remind them?

[pdr., 2014-08-07 17:37:53]

The CQ bit was checked by pdr@chromium.org

[commit-bot: I haz the power, 2014-08-07 17:40:08]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/ed@opera.com/447193002/1

[commit-bot: I haz the power, 2014-08-07 17:47:27]

Change committed as 179732

[Erik Dahlström (inactive), 2014-08-08 07:19:37]

On 2014/08/07 17:37:23, pdr wrote:
...
> You can upload a patch to an existing review by running "git cl issue [issue
> number]" and then uploading with "git cl upload". I don't knoe of a way to
> credit fs with this patch though. I agree that the chromium address limitation
> is ridiculous :( Can you comment on the bug about it to remind them?

Yeah, I tried that first, but it failed saying that I'm not the owner of the
review. Are you saying it would work if I had a chromium (or google) mail
address?

[krit, 2014-08-08 07:24:28]

On 2014/08/08 07:19:37, Erik Dahlström wrote:
> On 2014/08/07 17:37:23, pdr wrote:
> ...
> > You can upload a patch to an existing review by running "git cl issue [issue
> > number]" and then uploading with "git cl upload". I don't knoe of a way to
> > credit fs with this patch though. I agree that the chromium address
limitation
> > is ridiculous :( Can you comment on the bug about it to remind them?
> 
> Yeah, I tried that first, but it failed saying that I'm not the owner of the
> review. Are you saying it would work if I had a chromium (or google) mail
> address?

The daily discrimination :)

[pdr., 2014-08-12 02:27:16]

On 2014/08/08 07:19:37, Erik Dahlström wrote:
> On 2014/08/07 17:37:23, pdr wrote:
> ...
> > You can upload a patch to an existing review by running "git cl issue [issue
> > number]" and then uploading with "git cl upload". I don't knoe of a way to
> > credit fs with this patch though. I agree that the chromium address
limitation
> > is ridiculous :( Can you comment on the bug about it to remind them?
> 
> Yeah, I tried that first, but it failed saying that I'm not the owner of the
> review. Are you saying it would work if I had a chromium (or google) mail
> address?

I tried this today for the rollout of this patch and it failed for me as well (I
couldn't upload a patch to your review). It looks like it is no longer possible
to upload an issue to someone else's review; probably for security reasons.