stuck on "loading subtitles"

Bug
1

For a few days now im stuck on “loading subtitles”. i use Netflix, from germany, Japanese Audio, trying for German subs, but there is not a single subtitle loading. doesnt work on any content on netflix

2

Ditto.

Uruguay here, but account was registered in Croatia. It broken up around few days ago too. Apparently, Netflix is rolling out changes to the API and no longer reports video.textTracks as they used to.

Proper bug report (AI generated) follows.

Environment: Language Reactor (Pro) on Netflix web — Black Mirror “Common People” (Video ID: 81716301)

Observed Behavior

Both the LR side panel and below-video area show “— Loading subtitles… —” indefinitely. The Netflix audio/subtitle language dropdowns in LR settings are permanently stuck on “Loading…”.

Root Causes

1. JavaScript crash in redrawUI (primary)

On page load, a fatal TypeError crashes the LR rendering pipeline:

TypeError: Cannot read properties of undefined (reading 'b')
    at Module.B (pageScript_lln.min.js:8958:171681)
    at Object.redrawUI (...:8958:172956)
    at Object.loadDefaultLexaPrompts_translated (...:9024:39657)

Property b is read from an undefined object inside loadDefaultLexaPrompts_translated → redrawUI → Module.B, crashing the reactive render chain before subtitles can display.

2. Netflix subtitle tracks not accessible via HTML5 API

Netflix reports 36 subtitle/caption tracks via its internal player API, but video.textTracks.length === 0 — no tracks are attached to the <video> element. LR appears to depend on the standard HTML5 text tracks API, which Netflix no longer populates. The selected English CC track (T:2:1;1;en;0;0;0;) exists in the Netflix session but showTimedText is false and no cue data is reachable via the Web API.

Suggested Fixes

  1. Add a null guard before reading b in Module.B / redrawUI.
  2. Update subtitle interception to use Netflix’s proprietary player API (getOpenPlaybackSessions) instead of video.textTracks, which is empty.
3

p.s. I see that there are more reports on the same issue from other users, but apparently with gradual Netflix rollout it still didn’t hit the developers themselves. Drop me a line if you need to collect extra information about new shape of the API.