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
