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
+10-8Lines changed: 10 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,12 +3,12 @@ This is the repository for making the Web excellently embrace the spatial naviga
3
3
4
4
This repository consists of the basic description for spatial navigation, landscapes of the relevant industries, and the current status for [W3C standardization](explainer.md) and [Web engine implementation](impl.md) such as Blink, WebKit, Gecko, and EdgeHTML, while the relevant issues would be discussed in W3C working groups and Web engine open source communities.
5
5
6
-
You're welcome to contribute! If you have something to say for the spatial navigation, please kindly put it on the issues of this repository. Let's make the Web to be extensible!
6
+
You're welcome to contribute! If you have something to say for the spatial navigation, please kindly put it on [issues](https://github.com/lgeweb/spatial-navigation/issues) of this repository. Let's make the Web to be extensible for the several industries!
7
7
8
8
## Overview
9
9
**Spatial navigation (aka Snav)** is the ability to navigate between focusable elements based on their position within a structured document. Spatial navigation is often called the directional navigation which enables four directional navigation. Users are usually familiar with the 2-way navigation using tab key for the forward direction and shift+tab key for the backward direction, but not familiar with the 4-way navigation using arrow keys.
10
10
11
-
Regarding TV remote control, game console pad, IVI jog dial with 4-way keys, and accessibility, 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.
11
+
Regarding TV remote control, game console pad, IVI jog dial with 4-way keys, and Web accessibility, 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
## Motivation
14
14
Technical description
@@ -22,23 +22,25 @@ explainer link
22
22
The history of WebKit, Blink, Gekco, and W3C
23
23
24
24
## FAQ
25
-
Q. I’m not sure how the spatial (directional) navigation behavior work.
25
+
**Q. I’m not sure how the spatial (directional) navigation behavior work.**
26
26
- You can see the video that shows the Snav behavior in the YouTube page ([link](https://www.youtube.com/watch?v=TzDtcX9urUg)).
27
27
- You can see the brief description for the Snav in Wikipedia ([link](https://en.wikipedia.org/wiki/Spatial_navigation)).
28
28
- In several references below, you can get the help to understand the Snav operations.
29
29
30
-
Q. Isn’t it enough just using the relevant Web frameworks?
31
-
- Due to no support from web engine, severel Web frameworks and extensions for the Snav exist for now. [js-spatial-navigation](https://github.com/luke-chang/js-spatial-navigation) 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) by LGE is an instance of the frameworks for the Snav, even though it'll deprecated soon. However, the support of Snav from Web frameworks has some limits. blahblah (aligning scrolling, particularily using native focus method for a11y)
30
+
**Q. Isn’t it enough just using the relevant Web frameworks?**
31
+
- Due to no support from web engine, severel Web frameworks and extensions for the Snav exist for now. [js-spatial-navigation](https://github.com/luke-chang/js-spatial-navigation) 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) by LGE is an instance of the frameworks for the Snav, even though it'll deprecated soon. However, the support of Snav from Web frameworks has some limits. blahblah (aligning scrolling, particularily using native focus method for a11y)
32
32
33
-
Q. The Snav seems not the general feature esp. in mobile with no physical key-based interface.
33
+
**Q. The Snav seems not the general feature esp. in mobile with no physical key-based interface.**
34
34
- 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 the kind of mobile phone named feature phone. In the future, the input methods for smart devices will be changed a lot, but the basic interfaces like key based will never disappear. 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.
35
35
36
-
Q. The future input methods such as voice command, hand gesture, eyes direction will be promising. Why we should consider the new key-based input methods for the 4-way directional key navigation.
37
-
- As AI would be more and more promising technologies these days, the voice command has been anticipated to be used widely. It's true, but...
36
+
**Q. The future input methods such as voice command, hand gesture, eyes direction will be promising. Why we should consider the new key-based input methods for the 4-way directional key navigation.**
37
+
- As AI would be more and more promising technologies these days, the voice command has been anticipated to be used widely. It's true, but...
0 commit comments