Skip to content

changelog: record the colon fix under 0.7.10 #378

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
brainkim merged 1 commit into from
Aug 12, 2026
Merged

changelog: record the colon fix under 0.7.10 #378

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 12 additions & 10 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,16 +25,6 @@
and as a real line break in a `<pre>`. Whitespace adjacent to an element, an
expression, or the template edge is still stripped as layout.

- **`jsx` template tag now accepts colons in prop and tag names.**
`attr:`/`prop:` prefixes and other XML namespace prefixes (`xlink:href`,
`xmlns:xlink`, a namespaced tag like `svg:circle`) previously threw a parse
error (“Unexpected text `:`”) even though the DOM and HTML renderers already
understood them. The template tag now parses these to the same props object
compiled JSX produces. A leading, trailing, or repeated colon (`:foo`,
`foo:`, `a:b:c`) is a parse error, since none of those forms are meaningful
namespaced names; colons in text and quoted attribute values (`3:1`,
`style="color: red"`) are unaffected.

### Changed
- **`window.Crank` (the UMD/CDN browser global) now ships authoring templates and a default renderer.**
The browser build exposes the `jsx`/`html` tagged templates and `Crank.renderer`
Expand All @@ -45,6 +35,18 @@
`Crank.htmlRenderer` (server HTML), with `Crank.DOMRenderer`/`Crank.HTMLRenderer`
for the classes.

## [0.7.10] - 2026-08-12
### Bug Fixes
- **`jsx` template tag now accepts colons in prop and tag names.**
`attr:`/`prop:` prefixes and other XML namespace prefixes (`xlink:href`,
`xmlns:xlink`, a namespaced tag like `svg:circle`) previously threw a parse
error (“Unexpected text `:`”) even though the DOM and HTML renderers already
understood them. The template tag now parses these to the same props object
compiled JSX produces. A leading, trailing, or repeated colon (`:foo`,
`foo:`, `a:b:c`) is a parse error, since none of those forms are meaningful
namespaced names; colons in text and quoted attribute values (`3:1`,
`style="color: red"`) are unaffected.

## [0.7.9] - 2026-03-31
### Performance
- **Make User Timing API profiling opt-in via `setProfiling()`**
Expand Down
Loading