Repository navigation
Redesign the interface and expand browser planning - #36
Merged
Merged
Conversation
Replace the landing-page layout with a rotary protection selector and nine browser support tracks. Keep source-derived outcomes, missing information and individual explanations visible, with equivalent keyboard controls and a static fallback when scripting is unavailable. Introduce a nested open-contact mark, a graphite and silver palette, copper controls and locally served vector artwork. Rewrite page introductions and organise the navigation around planning, inspection, reference and sources. Separate minimum-version discovery into its own page, group the feature index, add contents navigation to longer references and paginate the update log while retaining its complete static contents and truthful totals. Add browser regressions for source-result parity, dial controls, keyboard navigation, no-script use, pagination, mobile layouts and accessibility. Preserve the existing evaluation, evidence, privacy and publication boundaries. Validation: complete verification with one unit worker (396 tests), the full browser suite (49 checks), optional engine workflows (69 checks), and the publication-path build, audit and navigation smoke all passed locally.
Add six directive-level controls and exact-release support timelines, and advance the catalogue with regenerated source history that retains earlier snapshots and change events. Introduce editable plan comparisons, suggested minimum-version increases, and a bounded opt-in library of named plans. Connect minimum calculations, planning and header inspection through validated transient plan transfers. Keep scope changes, source gaps and declaration evidence explicit. Provide interactive deployment circuits with alternative routes, browser support readings and separate application review checks. Retain bounded published test results with exact run provenance, separate harness and subtest totals, and an offline import command. Extend unit and browser regressions for incomplete source data, storage failures, malformed imports, stale results, complete comparison totals, responsive layouts, accessibility and preserved privacy boundaries. Update public usage, privacy and attribution notices for the resulting behaviour.
Allow long page headings to wrap inside their available width when the preferred display font is unavailable. Preserve the strict viewport limit and internal scrolling for wide support tables. Add route-labelled diagnostics with bounded element and ancestor sizing, include comparison and circuit pages at 320 pixels, and exercise the two headings whose fallback fonts previously expanded the document width.
Accept the exact zero-count, empty-status missing-run slot while retaining the required aggregate flag and rejecting substantive legacy results. Preserve run rebinding, exact suite filtering and the strict retained schema. Cover missing slots on retained and discarded rows, reversed run order, unchanged companion results, and rejection of non-zero or incomplete slots. Leave the retained source snapshot unchanged.
Give saved-plan changes one comparison handler so a bubbling form event cannot replace a load error with a result from previous field values. Report entries removed since selection began and invalidate comparisons, export controls, transfer links and proposed upgrades before each load. Exercise stale entries deleted in another tab, unavailable releases on both sides, successful saved selections, and recovery through manual field edits. Keep validation ahead of field updates and preserve the unaffected plan.
Label aggregate statuses as file outcomes so harness and non-harness tests are described accurately. Keep completed harness status, missing results and subtest counts distinct without changing any retained data or totals. Cover mixed OK, Pass and Fail outcomes with a focused unit regression and verify the terminology beside the complete retained browser results. Focused validation passed 21 unit tests and one browser check.
Map camera, microphone, geolocation, cache, cookies and storage to reviewed test files at the retained run revision. Show selected-file totals and exact source links alongside the scope of reporting, clearing and storage checks. Keep missing files and browser results explicit, reject selections from different source revisions, and preserve the separation between public test outcomes and application evidence. Publish both source-review revisions in the reference pages and attribution notices. Allow long compatibility notes to wrap within narrow release timelines. Final validation passed 442 unit tests across 47 files, 71 browser and accessibility checks, 14 additional engine checks, eight publication-prefix routes, the complete verification suite and a zero-vulnerability application audit.
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
1 participant
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.
The site now connects browser planning, source exploration and header review through an electrical instrument interface. The redesign replaces the landing page and logo, reorganises navigation, and makes browser choices reusable across tools.
Compatibility, supplied declaration evidence and public browser-test results remain separate. Persistence stays opt-in, and the website makes no runtime source requests.
Local validation of
60391b9aa1d10bf73072a2bb6895f125cf71bc98, using Node 26.4.0 and the reviewed npm 12.2.0 toolchain:VITEST_MAX_WORKERS=1 npm run verify: passed, including 413 unit tests across 46 files, coverage thresholds, lint, formatting, types, build and repository/public/language audits.npm run test:e2e -- --workers=1: 58 Chromium tests passed.CONTROLCURRENT_BROWSER_WORKFLOWS=1 npm run test:e2e -- --workers=1 --grep '@smoke|@workflow': 93 tagged workflow tests passed, 31 per engine across Chromium, Firefox and WebKit. No failures, retries or skips in the final browser runs.npm audit --audit-level=high: zero vulnerabilities./controlcurrent/with no external requests, page errors or persistent writes.The retained public test results were imported and validated; those upstream tests were not executed locally. These results describe local validation, not hosted CI or deployment.