Skip to content

Commit 3d52560

Browse files
authored
Update README.md
1 parent 603190d commit 3d52560

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -44,11 +44,11 @@ The history of CSS WG discussion..
4444

4545
**Q. Isn’t it enough just using the relevant Web frameworks?**
4646
- Severel Web frameworks and extensions for the Snav have been provided so far due to no support from web engines. For examples, [js-spatial-navigation](https://github.com/luke-chang/js-spatial-navigation) made by Mozilla seems one of the frameworks and the quality would be good to support the features of Snav. [Spotlight library](https://github.com/enyojs/spotlight) made by LGE is also an instance of the frameworks for the Snav, even though it was deprecated now. However, the support of Snav from Web frameworks has some limits as follows:
47-
1. difficult to align native scroll behavior when moving the focus to an element out of view
48-
2. difficult to align native focus method for a11y support
49-
3. performance degradation due to the expensive cost of DOM Access
50-
4. inconsistency of user experience (various sort of frameworks)
51-
5. impossible to control isolated frames like iframe and shadow DOM
47+
- difficult to align native scroll behavior when moving the focus to an element out of view
48+
- difficult to align native focus method for a11y support
49+
- performance degradation due to the expensive cost of DOM Access
50+
- inconsistency of user experience (various sort of frameworks)
51+
- impossible to control isolated frames like iframe and shadow DOM
5252

5353
**Q. The Snav seems not the general feature esp. in mobile with no physical key-based interface.**
5454
- Honestly, the mobile has been a first citizen of Snav about 10 years old. Before touch-based interface, the majority of interface for mobile was key-based methods. We're familiar with kind of mobile phone named a feature phone. In the future, the input methods for smart devices will be changed to something like voice command, hand gesture, and eyes direction, but the key-based interfaces will never disappear, even though it'll be used as a secondary method. It would be the most intuitive method with a strong feedback after pushing a key, while we couldn't imagine a touch-based keyboard without any physical keys.

0 commit comments

Comments
 (0)