If bug 1114536 could be landed on m-c in 2.5 timeline, then it would be included in the build of 2016 model but maybe pref off because as David said, it's made for flip phones so maybe we need to polish it a bit for TV case.
For TV core apps, we made a generic spatial navigation library in the shared folder, and it could be copied and used for 3rd-party app. :-) https://github.com/mozilla-b2g/gaia/blob/master/shared/js/smart-screen/spatial_navigator.js On Mon, Sep 28, 2015 at 9:08 AM, Dietrich Ayala <[email protected]> wrote: > Ok, thanks! > > Is that spatial nav solution coming in the 2016 model? > > Is there any library for doing this in Web content in 3rd party apps that > we can provide to developers? > > > On Mon, Sep 28, 2015 at 5:59 PM Shih-Chiang Chien <[email protected]> > wrote: > >> Hi Dietrich, >> >> FWIK navigation cursor is only supported in TV browser app in 2015 model >> and there is no way to turn on for 3rd-party apps. The real solution should >> be supporting spatial navigation for 3rd-party apps and apps need to >> optimize for non-touch devices as well. >> >> Best Regards, >> Shih-Chiang Chien >> Mozilla Taiwan >> >> On Mon, Sep 28, 2015 at 5:25 PM, Dietrich Ayala <[email protected]> >> wrote: >> >>> Thanks David! >>> >>> Yes, I mean the navigation cursor. >>> >>> When I load web content in the Firefox browser app on the tv, it is >>> visible, and uses the arrow keys on the tv to control. >>> >>> But for apps, it is not visible. >>> >>> On Thu, Sep 24, 2015 at 6:25 PM David Flanagan <[email protected]> >>> wrote: >>> >>>> Bug 1114536 is possibly related. It is about "spatial navigation" on >>>> flip phones. There is a giant patch from a partner attached that would be >>>> great to have some more eyeballs on. I imagine that flip phone keypads and >>>> tv remotes should have similar behavior for navigating within apps. >>>> (Though I suspect that apps that have the best UX will handle the arrow >>>> keys themselves rather than leaving this to a generic navigation >>>> mechanism.) >>>> >>>> But more to Dietrich's point, don't we have things like focus rings >>>> turned off in our CSS (or even at a lower level) for touchscreens? Perhaps >>>> the TV apps were using building blocks that explicitly prevented the >>>> display of the currently focused element? >>>> >>>> Dietrich: I'm assuming that when you say "cursor" you mean navigation >>>> cursor or focus ring. But if you're talking about the text input cursor, >>>> then I've got not clue. >>>> >>>> David >>>> >>>> On Thu, Sep 24, 2015 at 8:56 AM, Joe Cheng <[email protected]> wrote: >>>> >>>>> \o/ thanks for sharing Dietrich >>>>> Can't wait to hear more of your experience and feedback from more >>>>> events >>>>> >>>>> There is a newly posted article on MDN, perhaps this will help with >>>>> app development on TV >>>>> >>>>> https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/TVs_connected_devices/TV_remote_control_navigation >>>>> >>>>> I'm interested to understand cursor needs on TV app development. >>>>> Thought that most TV apps will have better experience if the app supports >>>>> arrow key events with a traditional TV remote? >>>>> >>>>> The cursor in the TV browser is a special implementation. There are >>>>> some gecko work that's still needed for cursor support in general but i'm >>>>> not the best person to talk about the technical details. I will let others >>>>> chime in >>>>> >>>>> >>>>> Re, >>>>> Joe Cheng >>>>> —————————— >>>>> Mozilla Corp. >>>>> [email protected] >>>>> >>>>> >>>>> On Fri, Sep 25, 2015 at 12:38 AM, Dietrich Ayala <[email protected]> >>>>> wrote: >>>>> >>>>>> We spent all day building TV apps with tons of people at RejectJS in >>>>>> Berlin, and it was AWESOME. >>>>>> >>>>>> However, we ran into a problem very quickly: In apps pushed to the >>>>>> TV, the cursor doesn't show up, and focus was not working as expected. >>>>>> For >>>>>> example, calling focus() on an <a> tag did not focus the element. Form >>>>>> elements were able to receive focus. >>>>>> >>>>>> The cursor did work in web content in the Firefox browser app. >>>>>> >>>>>> People worked around this by writing their own navigation systems >>>>>> with arrow key events. >>>>>> >>>>>> What is required for cursor visibility in 3rd party apps? >>>>>> >>>>>> _______________________________________________ >>>>>> dev-fxos mailing list >>>>>> [email protected] >>>>>> https://lists.mozilla.org/listinfo/dev-fxos >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> dev-fxos mailing list >>>>> [email protected] >>>>> https://lists.mozilla.org/listinfo/dev-fxos >>>>> >>>>> >>>> >>> _______________________________________________ >>> dev-fxos mailing list >>> [email protected] >>> https://lists.mozilla.org/listinfo/dev-fxos >>> >>> >> > _______________________________________________ > dev-fxos mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-fxos > > -- Evelyn Hung Front-end Engineering Lead, Firefox OS Devices Mozilla Corporation
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
