The back button skips 5 seconds, not 10. Going back is for the line of
dialogue you missed; going forward is for the opening you have seen. Forward is
unchanged at 10 seconds. A double-tap in each zone now follows its own button:
5 seconds a tap on the left, 10 on the right.

Picture in picture BUTTON is gone. Gecko has no floating-window API on Android, so
the button asked the system for the home screen and hoped — it worked on some
builds and did nothing on others. The top row is one button shorter/


Unchanged, and worth restating for review:

• Permissions are still exactly storage and activeTab. No host permissions.
• data_collection_permissions is still none.
• No network of any kind: no fetch, XMLHttpRequest, sendBeacon,
  WebSocket, EventSource.
• No code injected into the page, nothing evaluated from a string.
• The automated privacy check passes on 31 files.

A series on a Playerjs site keeps a path — the season, the dub, the episode —
and the player draws one control per step of it. Nocturne reads those and puts
them in the top-left of the player, laid out across, where a thumb reaches with
the phone held sideways: the season, then the episode. Each opens a list with
the one being watched marked, and picking an episode plays it without leaving
the player.


Film sites often carry two or three dubs, and switching them from a phone was
close to impossible. The sheet has a row for it now, reading hls.js
audioTracks, dash.js getTracksFor('audio'), Shaka's audio languages,
Playerjs's own list, and the audioTracks a browser exposes on the video
element. Like the quality row, it stays hidden when there is nothing to choose
between.

Fixed - Quality on ordinary film sites:

Sites that embed Playerjs — a large part of what people actually watch on a phone — now offer their ladder in the sheet like any other player. Playerjs keeps its streaming engine inside a closure, but it answers about itself: api('qualities') lists the rungs the site built, in the site's own words, and api('quality', label) is the call its own menu makes.

Both are reads and calls on an object the page already published; no code is injected and nothing is evaluated from a string. The chips come out auto first, then best to worst, whatever order the site listed them in.