New API

[gregziegan]

Implementation of all the notes from #26

You can see what brought me to this API from this video

TODO:

• API that allows the consumer to own the data
• Support keydowns via subscription
• Support sections
• Allow for a single selection state (mouse & key unified)
• Fix tests
• Documentation

WAI-ARIA Compliance

Key and Mouse navigation:

Sections:

[maximsch2]

Really excited to move to the new API. Out of curiosity: why did you require a new native module for a simple map function? Is it just a way to force-convert the type?

[gregziegan]

Correct! Talked w/ Evan about the strategy to get this published sooner than later. Attribute.map will be coming in the next release, so the native module is just an intermediary trick.

Won't have much time to merge and clean this up until the weekend. But also looking into subscriptions for menu only key events, may remove the input depending on the success of the subscriptions, and finally: menu sections like seen in react autosuggest.

I will also default as many attributes as possible to default WAI-ARIA compliance and do some screen reader testing.

[gregziegan]

Tests are currently not useful: Having a silent error on import. Looking into getting an sscce for elm-test. Not going to block a release on tests, though.

[gregziegan]

Just got whitelisted
elm/package.elm-lang.org#199

So of course i'm going to wreak havoc with runtime errors 😈

Working on documentation now and want to have a WAI-ARIA support example, since I don't provide an input. I want to see when making that example if there's a way to provide a convenience function.

[gregziegan]

PR is getting too old, will make small PRs for the last points addressing issues directly