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 24428 - Add parser support for feDropShadow
Summary: Add parser support for feDropShadow
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Robin Berjon
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: CR
Depends on: 24424
Blocks:
  Show dependency treegraph
 
Reported: 2014-01-28 18:28 UTC by Edward O'Connor
Modified: 2014-03-14 10:07 UTC (History)
10 users (show)

See Also:


Attachments

Description Edward O'Connor 2014-01-28 18:28:46 UTC
If SVG continues down this path, we should merge any HTML parser changes into both 5.1 and 5.0.

+++ This bug was initially created as a clone of Bug #24424 +++

https://dvcs.w3.org/hg/FXTF/raw-file/e1ae5deb9fa8/filters/index.html specifies <feDropShadow> in violation of the expectation that no new camel-case  names would be added to SVG.

Since camel-casing this is consistent with the existing filter effects, please add a mapping from fedropshadow to feDropShadow  to the parsing spec.
Comment 1 Edward O'Connor 2014-01-30 18:35:35 UTC
Ian's updated the parser in 07fb982; we should merge that to both master and CR.
Comment 2 Edward O'Connor 2014-02-07 18:26:09 UTC
Merged to 5.1 by Robin: http://lists.w3.org/Archives/Public/public-html/2014Feb/0021.html

We should take this parser change for 5.0.
Comment 3 Robin Berjon 2014-03-14 10:07:52 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the Editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the Tracker Issue; or you may create a Tracker Issue
yourself, if you are able to do so. For more details, see this document:

   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Accepted
Change Description: Applied change to CR
Rationale: Required for the parser.