docs(changelog): the two review fixes users would notice
Publish Documentation / Build & publish docs to gitea-pages (push) Successful in 6m5s
Traceability Validation / Check Requirement Traces (push) Successful in 19s
Build & Release / Run Tests (push) Successful in 15m20s
Build & Release / Build Linux (push) Successful in 21m22s
Build & Release / Build Windows (push) Successful in 16m11s
Build & Release / Build Android (push) Successful in 31m49s
Build & Release / Create Release (push) Successful in 1m3s
Publish Documentation / Build & publish docs to gitea-pages (push) Successful in 6m5s
Traceability Validation / Check Requirement Traces (push) Successful in 19s
Build & Release / Run Tests (push) Successful in 15m20s
Build & Release / Build Linux (push) Successful in 21m22s
Build & Release / Build Windows (push) Successful in 16m11s
Build & Release / Build Android (push) Successful in 31m49s
Build & Release / Create Release (push) Successful in 1m3s
The tag message counted twelve defects while the changelog described ten. Both of the missing ones are user-visible and belong in the user-facing artifact: a quality ceiling that outlived the episode it was chosen for, and a seek that outlived the file it was meant for. The third review fix — collapsing two identical URL helpers — is not here on purpose. Nobody using the app can tell.
This commit is contained in:
@@ -82,6 +82,17 @@ fact about the platform rather than asking the thing that would know.
|
||||
code that had stopped being Linux-only, and the Android build had not compiled
|
||||
since. (DR-247)
|
||||
|
||||
- **A quality you chose for one episode no longer caps every episode after it.**
|
||||
Dropping the quality mid-episode is meant to describe that episode. When the
|
||||
next one started in the background, nothing reset it — so the ceiling stayed
|
||||
in force indefinitely, with nothing in the interface saying why later episodes
|
||||
looked worse. (DR-254)
|
||||
|
||||
- **Skipping to the next item no longer starts it part-way through.** Scrubbing
|
||||
near the end of a converted stream re-opens it, and the position being waited
|
||||
for was not discarded if you skipped onward first — so the next item began
|
||||
wherever you had dragged to in the previous one. (DR-253)
|
||||
|
||||
### 🧹 Under the hood
|
||||
|
||||
- The conformance suite can be run on its own: `bun run test:player` for the
|
||||
|
||||
Reference in New Issue
Block a user