28217 2015-03-15 14:18:28 +0000 <canvas>: not clear if two polygon paths with a common edge should have no line visible 2019-03-29 21:33:03 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other All RESOLVED MOVED https://html.spec.whatwg.org/multipage/canvas.html#dom-context-2d-fill P3 normal Unsorted 1 contributor ian annevk d junov mike contributor oldest_to_newest 118608 0 contributor 2015-03-15 14:18:28 +0000 Specification: https://html.spec.whatwg.org/multipage/scripting.html Multipage: https://html.spec.whatwg.org/multipage/#drawing-paths-to-the-canvas:dom-context-2d-fill Complete: https://html.spec.whatwg.org/#drawing-paths-to-the-canvas:dom-context-2d-fill Referrer: https://html.spec.whatwg.org/multipage/scripting.html Comment: It's not clear from the spec if two paths which describe two poligons with a common edge, when render as a single solid polygon when using fill() on them. In particular the spec does not seem to explain what implementation of anti-aliasing should be used on edges, to make sure that there is no gap between incident shapes. For example http://jsfiddle.net/xgd03fyb/ in Chrome shows two triangles with a visible artifact between them, while clearly the intention was to draw them as a square. Is it a bug or a feature? Posted from: 78.8.147.90 User agent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.89 Safari/537.36 129056 1 annevk 2018-01-29 14:30:24 +0000 As all browsers show two triangles I suspect that's what we should define. Not sure how though. 129700 2 d 2019-03-29 21:33:03 +0000 https://github.com/whatwg/html/issues/4485