Repository navigation
Review workflow, two-file import, safer DOCX handling; release v1.7.0 - #13
Merged
Merged
Conversation
Selecting two documents in one file picker cleared the picker after the first upload, so the second file was dropped before it could be read. The intake now snapshots the selection before either upload is awaited and treats the pair as one guarded operation, which also stops a review reset from making the second upload prompt again. Beyond that: - DOCX text is read through streaming ZIP decompression instead of building the whole archive in memory, and the PDF task is destroyed on failure. - Restoring a saved session establishes a clean review baseline even when the right-hand text is unchanged. - Document replacement and paste-field changes guard pending review work; the right-side document input is resolved per side. - The landing-page drop slots and top-bar actions share one clear path. - Search metadata, start-page FAQ scope and the privacy wording settle. Docs record the browser and office verification round and its limits.
`.btn` sets `display: inline-flex`, so the user-agent `[hidden]` rule lost against it and elements stayed visible after JS marked them hidden. The worst case was a comparison without any changes: the sidebar offered "accept all, export the final Word version" right above the message saying both documents are identical. The paste entry in the overflow menu showed for the same reason. A single global rule restores the meaning of the attribute. Verified in a browser: with identical documents no action is offered, with 20 changes the accept-all action is still there, and no element carrying `hidden` renders in any checked state.
- Cancelling the unsaved-work prompt now clears both file pickers, so choosing the same file again fires a change event. - Browsers without DecompressionStream import DOCX text through Mammoth again instead of reporting every file as corrupt. - Rejected header/footer entries recompute their changed words, so a rejected group that differs only in page numbers stays one entry while substantive numeric differences still split it. - Add regression tests, release notes and bump the app version to 1.7.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
_Generated.docx; PDF pages and tasks are cleaned up.[hidden]always wins over component display values; English web app manifest for/en/; dark-mode link colour; laptop padding.DecompressionStreamimport DOCX through Mammoth again instead of reporting every file as corrupt.docs/releases/v1.7.0.md.Verification
python3 scripts/build.pyandnode scripts/check.mjspass locally: security/privacy/i18n (342 keys), SEO, worker parity (18), export builders (426 groups), core diff (51), app state (15 groups, with new regression cases for the fixes above).🤖 Generated with Claude Code