- From: Philip Taylor <pjt47@cam.ac.uk>
- Date: Tue, 24 Jun 2008 13:30:05 +0100
- To: HTML WG <public-html@w3.org>
Various minor stuff that I don't want to bother sending separate emails for: isPointInPath needs to specify that "inside the current path" is based on the non-zero winding number rule, else it's unclear what "inside" means. Patterns shouldn't be optional: the optionality is harmful to authors, since they can't depend on pattern support; it's harmful for implementors, because they will be incompatible with lots of content if they don't implement patterns; and it doesn't help implementors, since it's not really harder than drawImage and all current implementors chose to support it already. The spec says for getContext: "Arguments other than the contextId must be ignored, and must not cause the user agent to raise an exception (as would normally occur if a method was called with the wrong number of arguments)". That says "must" twice, but it's only one testable assertion, so it would be a tiny bit nicer to say "... must be ignored, and not cause ..." rotate() says "If the angle argument is infinite, the method call must be ignored". That is the default behaviour for canvas methods, so the explicit sentence here should be removed. "The stroke() method must [...] fill the combined stroke area using the strokeStyle, attribute." - remove comma after "strokeStyle". putImageData: "If any of the arguments to the method are infinite or NaN, the method must raise an NOT_SUPPORTED_ERR exception." - s/an/a/ "If the anticlockwise argument is false ... or, if the anticlockwise argument is true ..." - that says "<em>true</em>" but plain non-italic "false". -- Philip Taylor pjt47@cam.ac.uk
Received on Tuesday, 24 June 2008 12:30:45 UTC