On Mon, Apr 7, 2014 at 3:35 PM, Ian Hickson i...@hixie.ch wrote:
On Wed, 12 Mar 2014, Rik Cabanier wrote:
On Wed, Mar 12, 2014 at 3:44 PM, Ian Hickson wrote:
On Thu, 28 Nov 2013, Rik Cabanier wrote:
On Thu, Nov 28, 2013 at 8:30 AM, Jürg Lehni wrote:
I meant to say that it I
On 7 April 2014 20:06, Ian Hickson i...@hixie.ch wrote:
Should there be a particular need for an accessible name for the details
control, ARIA can be used to set the name. But I must admit to not
understanding why you would need that in practice, if the page is well
written. (I find most
On Mon, Apr 7, 2014 at 3:35 PM, Ian Hickson i...@hixie.ch wrote:
So this is not how most implementations currently have it defined.
I'm unsure what you mean. Browser implementations? If so, they
definitely do store the path in user coordinates. The spec currently
says
(Note: I started responding to this feedback last week, so this is missing
responses to feedback sent in the last few days. Sorry about that. I'll
get to that feedback in due course as well!)
On Mon, 3 Mar 2014, Justin Novosad wrote:
Say you create a new document using
On Mon, Apr 7, 2014 at 3:35 PM, Ian Hickson i...@hixie.ch wrote:
So this is not how most implementations currently have it defined.
I'm unsure what you mean. Browser implementations? If so, they
definitely do store the path in user coordinates. The spec currently
says
On Tue, Apr 8, 2014 at 5:25 AM, Steve Faulkner faulkner.st...@gmail.com wrote:
avoiding unnecessary recourse to web component use is a reasonable and
expected goal - built in vs bolt on accessibility is better. Having to use
a web component to overcome the inability to make a html control
On Tue, Apr 8, 2014 at 12:25 PM, Justin Novosad ju...@google.com wrote:
On Mon, 17 Mar 2014, Justin Novosad wrote:
Yes, but there is still an issue that causes problems in Blink/WebKit:
because the canvas rendering context stores its path in local
(untransformed) space, whenever
On Mon, Apr 7, 2014 at 3:35 PM, Ian Hickson i...@hixie.ch wrote:
...
Stroking will be completely wrong too, because joins and end caps
are drawn separately, so they would be stroked as separate paths.
This will not give you the effect of a double-stroked path.
I don't
On Tue, Apr 8, 2014 at 4:50 PM, Rik Cabanier caban...@gmail.com wrote:
On Mon, Apr 7, 2014 at 3:35 PM, Ian Hickson i...@hixie.ch wrote:
...
Stroking will be completely wrong too, because joins and end caps
are drawn separately, so they would be stroked as separate paths.
This
