You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,9 +11,9 @@ You're welcome to contribute! If you have something to say for the spatial navig
11
11
Regarding TV remote control, game console pad, IVI jog dial with 4-way keys, and Web accessibility, the spatial navigation has been a rising important input mechanism in several industries. If the Web can embrace the spatial navigation and effectively support the functionalities in Web engines and W3C APIs, it will be more promising technology for existing products as mentioned above and various upcoming products.
12
12
13
13
## Mission
14
-
Prior to the mission explanation, we are required how the arrow keys works in the Web. If you're watching this page in a normal HD monitor with PC, not mobile, please push a down key in your keyboard. What happens? Basically, scrolling downward would be triggered. That's the default behavior of arrow keys in the Web, only when the browsing context is overflowed in the direction.
14
+
Prior to the mission explanation, we need to understand how the arrow keys works currently in the Web. If you're watching this page in a normal HD monitor and desktop PC, not mobile, please push a down key in your keyboard. What happens? Basically, scrolling downward would be triggered. That's the default behavior of arrow keys in the Web, only when the browsing context is overflowed in the direction.
15
15
16
-
In spatial navigation mode, the default behavior of arrow keys is changed from scrolling to focus moving so that users can use the arrow keys to navigate between focusable elements based on their position.
16
+
In spatial navigation mode, the default behavior of arrow keys is changed from scrolling behavior to focus moving so that users can use the arrow keys to navigate between focusable elements based on their position.
17
17
18
18
To support the functionalities of the spatial navigation, we should consider the following three steps:
19
19
1. Options for enabling the spatial navigation mode
@@ -26,23 +26,23 @@ See the [implStatus](implStatus.md) for the details of the implementation in Web
26
26
27
27
## FAQ
28
28
**Q. I’m not sure how the spatial (directional) navigation behavior work.**
29
-
- You can see the video that shows the Snav behavior in the YouTube page ([link](https://www.youtube.com/watch?v=TzDtcX9urUg)).
30
-
- You can see the brief description for the Snav in Wikipedia ([link](https://en.wikipedia.org/wiki/Spatial_navigation)).
31
-
- In several references below, you can get the help to understand the Snav operations well.
29
+
- You can see the video that shows the Snav behavior in the YouTube page ([link](https://www.youtube.com/watch?v=TzDtcX9urUg)).
30
+
- You can see the brief description for the Snav in Wikipedia ([link](https://en.wikipedia.org/wiki/Spatial_navigation)).
31
+
- In several references below, you can get the help to understand the Snav operations well.
32
32
33
33
**Q. Isn’t it enough just using the relevant Web frameworks?**
34
-
- 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:
35
-
- difficult to align native scroll behavior when moving the focus to an element out of view
36
-
- difficult to align native focus method for a11y support
37
-
- performance degradation due to the expensive cost of DOM Access
38
-
- inconsistency of user experience (various sort of frameworks)
39
-
- impossible to control isolated frames like iframe and shadow DOM
34
+
- 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:
35
+
- difficult to align native scroll behavior when moving the focus to an element out of view
36
+
- difficult to align native focus method for a11y support
37
+
- performance degradation due to the expensive cost of DOM Access
38
+
- inconsistency of user experience (various sort of frameworks)
39
+
- impossible to control isolated frames like iframe and shadow DOM
40
40
41
41
**Q. The Snav seems not the general feature esp. in mobile with no physical key-based interface.**
42
-
- 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.
42
+
- 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.
43
43
44
44
**Q. Put any question on [issues](https://github.com/lgeweb/spatial-navigation/issues) of this repository :D**
0 commit comments