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 10786 - I think it would make more sense to apply shadows to individual sections of stroke() and fill() functions in the same context much the way stroke an fill colors can be changed inline between stroke() and fill() functions. This way you could apply differen
Summary: I think it would make more sense to apply shadows to individual sections of s...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML Canvas 2D Context (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-27 23:02 UTC by contributor
Modified: 2010-10-05 12:58 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2010-09-27 23:02:01 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/complete.html#shadows

Comment:
I think it would make more sense to apply shadows to individual sections of
stroke() and fill() functions in the same context much the way stroke an fill
colors can be changed inline between stroke() and fill() functions. This way
you could apply different shadows to different shapes in one canvas. The
global shadow can be cumbersome.

Posted from: 17.207.14.223
Comment 1 Ian 'Hixie' Hickson 2010-09-30 08:08:02 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: Rejected
Change Description: no spec change
Rationale: While in principle I think the suggestion makes sense, it's too late to change this API. It's already shipped widely.