Repository navigation
Let browser starter users save edited HTML and CSS - #33
Merged
Merged
Conversation
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 browser starter could render edited HTML/CSS but offered no way to save that source. Add Save HTML and Save CSS downloads for the selected template, preserving UTF-8 text and placeholders even before a successful render. Add direct links to the complete starter and setup guide.
The example retains its pinned Fullbleed 0.4.1 / engine 2.5.22 runtime. No npm package release is needed.
Validation: 52 real Chrome checks, including six exact source downloads, design switching, failed-render recovery, PDF output, and desktop/390px/320px visual review. Existing CI also checks Firefox and Playwright WebKit. Local evidence is recorded in
verification/browser-template-downloads.json.