Most of the time, default spatial navigation rule is useful. However, in some cases, a web page or an app might want to customize the calculation result of spatial navigation, so the to-be-focused element may not just be the nearest one but also the most *intended* one, or even overwrite the result by application logic. We are looking for a way to allow web developer to control the logic partially and dynamically, so it's flexible to fit real cases for a better UX.
It seems this proposal fits our needs: http://dev.w3.org/csswg/css-ui/#nav-dir Since the 'auto' behavior is not defined in this spec, so it may vary from UA to UA. Our 'auto' implementation will be done in bug 1114536. Yury and Egor, as app developers, do you think this proposal is good for your cases?
Evelyn, It's not clear how we could use this approach for applications, which update the UI dynamically (e.g. for Contacts, SMS, etc.)?
No UI changes, it affects the rule of calculating the next-focus element. It's based on bug 1114536, once it's done, you will need this bug for better controlling navigating logic to fulfill some special UX requirements.
Whiteboard: [red-tai] → [red-tai] nice-to-have-2.2r
The capability of jumping to the intended "next" UI object instead of the automatically logical object is very helpful to help users avoid having to slog through headers or links that they really don't need to get to the content.
Firefox OS is not being worked on
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.