Keys ↑ and ↓ mapped onto chapters, then on playlist

[dascritch]

No description provided.

[dascritch]

• Focus plane/point magement
  • el.CPU.focusPoint(planeName,pointName) (focus on plane, else on track, else... error ?)
  • planeAndPointNamesFromId( el.CPU.focusedId() ) => [ planeName, pointName ] or null
  • is there a el.CPU method to get which chapter is played / time positionned ? yes : el.CPU._activecue_id
  • el.CPU.prevFocus() // for key management
  • el.CPU.nextFocus() // for key management
• util.js, utility to browse in a (supposedly) ordered object
  • util adjacentKey(object, key, offset) // on document.CPU for tests purposes
• add some trigger, cabled on eventual shadow button
  • trigger prevcue previous chapter
  • trigger nextcue next chapter
  • trigger prevtrack previous track in playlist
  • trigger nexttrack next track in playlist (rewrite trigger event end of track)
• map key
  • up CPU.el.prevFocus()
  • down CPU.el.nexrFocus()
  • pageup on focusPoint / previousInObj plane
  • pagedown on focusPoint / nextInObj plane

[dascritch]

Remark : for keys, we WON'T immediately change audio position, let's way for "enter" key (to check too)

[dascritch]

strangely , element.focus() doesn't gives ":focus" pseudoelement but ":active" . Not what I want, at all

[dascritch]

Linked to WICG/webcomponents#830 ...????

[dascritch]

We need to separate cues (which relly on chapters) and keys ↑ and ↓ , why is about focus between panels

[dascritch]

prevcue may blink chapter panel, as the download strategy from the browser to go upper in the audio may go a second too early, blinking a previous chapter.

[dascritch]

Still a strange bug where a click on playlist make lose focus, so losing ↑ and ↓ keys.
I know why : when you have the playlist panel, you're con the controller. Clicking will give focus to the cpu-audio instance of the chosen audio.
Annoying, but I don't see how elegantely not losing focus .... as it is controlled via an hashchange event ....

[dascritch]

pageup/pagedown should be used to change cpu-audio / cpu-controller among playlists

[dascritch]

The focus is lost when changing sound in the cpu-controller because we redraw all the panels. Perhaps we mustn't redraw the one linked to the component.

[dascritch]

Note for later : using "insertAdjacentElement" to move a DOM tree will remove focus to elements.

[dascritch]

I need an "all possible buttons" theme, with a specific panel in controller for playlist. Mainly for tests and showcases