On 8 April 2014 21:54, Tab Atkins Jr. jackalm...@gmail.com wrote:
I still don't understand. Do you think that what Hixie is saying
(about clicking on non-interactive text in summary toggling the
details) is wrong?
nope.
The behavior that Hixie describes is roughly what implementations
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 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
--
Regards
SteveF
HTML 5.1 http://www.w3.org/html/wg/drafts/html/master/
On 6 April 2014 05:11, Ian Hickson i...@hixie.ch wrote:
On Sat, 5 Apr 2014, Steve Faulkner wrote:
The summary itself is not interactive, so only the triangle provides
the actionable control.
The spec doesn't
On Sun, 6 Apr 2014, Steve Faulkner wrote:
On 6 April 2014 05:11, Ian Hickson i...@hixie.ch wrote:
On Sat, 5 Apr 2014, Steve Faulkner wrote:
The summary itself is not interactive, so only the triangle
provides the actionable control.
The spec doesn't disallow making clicks on
--
Regards
SteveF
HTML 5.1 http://www.w3.org/html/wg/drafts/html/master/
On 6 April 2014 21:08, Ian Hickson i...@hixie.ch wrote:
On Sun, 6 Apr 2014, Steve Faulkner wrote:
On 6 April 2014 05:11, Ian Hickson i...@hixie.ch wrote:
On Sat, 5 Apr 2014, Steve Faulkner wrote:
The
On Mon, 7 Apr 2014, Steve Faulkner wrote:
All that should be necessary is:
details
summary Foo /summary
...
/details
Adding two attributes and an elements is thus more complicated than
necessary. This seems pretty unambiguous to me.
for the case
details
summary
On Sat, 5 Apr 2014, Steve Faulkner wrote:
The summary itself is not interactive, so only the triangle provides
the actionable control.
The spec doesn't disallow making clicks on (non-interactive) parts of the
summary defer to the disclosure triangle. Browsers should just match
platform
