11172 2010-10-29 19:54:10 +0000 wouldn't it be better to return the context handler instead of void, making "context.moveTo(x1,y1).lineTo(x2,y2).lineTo..." possible and easier? 2011-08-04 05:03:48 +0000 1 1 1 Unclassified HTML WG LC1 HTML Canvas 2D Context unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#the-canvas-state P3 normal --- 1 contributor ian ayg ian mike Ms2ger public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 41844 0 contributor 2010-10-29 19:54:10 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/complete.html#the-canvas-state Comment: wouldn't it be better to return the context handler instead of void, making "context.moveTo(x1,y1).lineTo(x2,y2).lineTo..." possible and easier? Posted from: 84.110.19.97 41890 1 Ms2ger 2010-10-31 16:19:34 +0000 I don't see the point. If that's what you like, use jQuery. 41892 2 Ms2ger 2010-10-31 16:19:46 +0000 *** Bug 11173 has been marked as a duplicate of this bug. *** 41927 3 ayg 2010-11-01 20:00:30 +0000 This is nice in jQuery because it sometimes lets you avoid naming extra variables, e.g. (actual code sample I was just looking at) $("body").append("<script></script>").attr("src", foo); rather than var script = document.createElement("script"); script.src = foo; document.body.appendChild(script); which is necessary when using DOM methods because "script.src = foo" and the equivalent setAttribute() call don't return the element they're operating on, so you need an explicit temporary variable. But almost any real-world canvas use is going to want to keep around a context handler anyway, so it doesn't look like there's any gain here. (Although I don't see the harm either.) 43584 4 ian 2010-12-27 23:54:48 +0000 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: Returning self isn't a good design pattern IMHO. It leads to very odd APIs that favour syntactic sugar over conveying logic. 52717 5 mike 2011-08-04 05:03:48 +0000 mass-move component to LC1