Chrome <details> broke keyboard functionality

[darkkain]

FIrst of all, great thanks for this library.
And right to the point:
Hard to explain how to reproduce, think best explanation will be codepen 😉
I create example, try to expand/colapse with keyboard in Chrome.
http://codepen.io/dkk/pen/eZPmar

[KittyGiraudel]

Hey there!

I will be honest and say I am not surprised. a11y-toggle reproduces the same kind of functionality than <summary>/<details> so it does make sense to me that there is some conflict when used simultaneously. Right now, it doesn’t work well with these elements.

Beside semantics, is there any reason you would use them?

[darkkain]

Besides semantics, only that the feature has native implementation in browser == always good (if they work well 😄)

And for now, it's available in WebKit's family, and Mozilla announced a few weeks ago, that feature landed in Nightly/Aurora build's

[KittyGiraudel]

I need to work on making it work for these elements as well.

[KittyGiraudel]

The support of details/summary is getting excellent: http://caniuse.com/#search=details. It should be compatible with the lib. I need to work on this.