Repository navigation
feat: add browser-compatibility skill - #2
Merged
Merged
Conversation
New frontend skill that keeps Open Elements apps working in every supported browser, including hardened ones such as LibreWolf: - browserslist with Firefox ESR (without Opera Mini) and eslint-plugin-compat - lint ban on unguarded localStorage/sessionStorage, safeStorage helper - what the privacy settings of hardened browsers break - Playwright cross-browser smoke tests (Chromium, Firefox, WebKit and a hardened Firefox profile) with a GitHub Actions workflow against the Docker stack and the mock OIDC server web-frontend-builder and open-elements-app-layout reference the skill from their testing sections and checklists. 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.
What
New frontend skill
browser-compatibility, so every Open Elements app gets the same setup to keep working in all supported browsers, including hardened ones such as LibreWolf:browserslistthat includes Firefox ESR and leaves out Opera Mini (otherwise everyfetchgets flagged),eslint-plugin-compat, and a ban on unguardedlocalStorage/sessionStorage(no-restricted-globalsplusno-restricted-properties).safeStoragefrom@open-elements/ui(fix: guard localStorage access and export a safeStorage helper open-elements-ui#20), or a guardedtry/catchpattern until an app is on that release.firefox-hardened), a smoke spec that logs in via the mock OIDC server and opens every page (fails on page errors, console errors and 5xx responses), a GitHub Actions workflow against the Docker stack with seeded data, and how to run it locally in the Linux container, since Playwright's Firefox does not start on recent macOS.web-frontend-builderandopen-elements-app-layoutreference the skill from their testing sections and checklists.open-elements-app-layoutalso lists open-elements-ui#19 and nextjs-app-layer#14 under known library issues. README,CLAUDE.md,CHANGELOG.md(Unreleased) and theplugin.jsondescription and keywords are updated.Why
The resource-planning app was reported as not working in LibreWolf. The investigation turned up unguarded storage access in both libraries and showed that nothing tested the apps outside Chromium. The same setup is introduced in resource-planning, where all four browser projects pass. It is written up here so every app gets it as the standard.
Notes
claude plugin validate ./ --strict.claude plugin validate ./ --strictreports the same warning onmain(rootCLAUDE.mdis not loaded) and the missing-icon notice. This PR adds no new warnings.🤖 Generated with Claude Code