Fix stray NBSP indentation in src/htmx.js - #3943
Merged
MichaelWest22 merged 1 commit intoAug 2, 2026
Merged
Conversation
Collaborator
|
Yeah thanks i'm not sure how this happened. seems something went wrong with that recent edit of mine somehow! |
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.
Description
Line 1180 was indented with non-breaking-space characters (U+00A0) instead of regular
spaces — almost certainly a copy-paste typo from #3924. Harmless to JS engines (NBSP is
valid whitespace), but if both the embedding page and this script lack a declared charset,
Chromium decodes the script as Windows-1252, mangling those bytes into a stray "Â" and
throwing a SyntaxError before
window.htmxis ever defined. Reproduced live to confirm.Swapped the NBSPs for normal spaces.
Testing
Confirmed no NBSP left in the file. Reproduced the failure in real Chromium (page + script
both charset-less) before the fix, confirmed it's gone after. Full suite: 1615 passed / 2
flaky, unrelated failures (reran those two alone, both pass).
Checklist
masterfor website changes,devforsource changes)
approved via an issue
npm run test) and verified that it succeeded