This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 23812 - Validator says feComposite needs in2, implementations say it doesn't, and the spec doesn't seem to care either way.
Summary: Validator says feComposite needs in2, implementations say it doesn't, and the...
Status: NEW
Alias: None
Product: Validator
Classification: Unclassified
Component: check (show other bugs)
Version: HEAD
Hardware: All All
: P2 major
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: qa-dev tracking
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-12 22:24 UTC by aaron
Modified: 2013-11-13 19:16 UTC (History)
0 users

See Also:

Attachments
An SVG which triggers the issue. (2.77 KB, image/svg+xml)
2013-11-12 22:24 UTC, aaron 		Details

Description aaron 2013-11-12 22:24:09 UTC 
Created attachment 1414 [details]
An SVG which triggers the issue.

I've noticed when running an svg through the validator, it tells me that in2 is a required attribute for feComposite.

After reading the appropriate parts of the spec (http://www.w3.org/TR/SVG/filters.html#feCompositeIn2Attribute), it appears to be defined to inherit its default from `in', in which case it is not required, and has defined behaviour (namely considering the immediately preceding filter primitive's result to be the input). This seems to be the conclusion that implementors have drawn, since implementations handle it this way as well.

As you can see though, it isn't that way according to the validator.
http://validator.w3.org/unicorn/check?ucn_uri=magnifi.ca%2Fphotos%2Frnd%2Fdms_w3c.svg&tests=markup-validator&warning=1&profile=svg&usermedium=all&ucn_lang=en&ucn_task=custom#