Repository navigation
Add the selectedcontent element, and release C 2.1.0, C# 2.3.0 and JS 1.3.0 - #7
Merged
Merged
Conversation
selectedcontent is the one element in the HTML standard's element index that html.json didn't have. It goes inside a customizable select's button and shows a copy of the chosen option. It has no content but still needs an end tag, so it's in "tags", not "tagsVoid". Regenerated from html.json: Selectedcontent in C and C#, and selectedcontent in JavaScript (index.js, index.d.ts, index.mjs and htmb.umd.js). The shared tests now check it in all three. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Each adds the selectedcontent tag, so each is a minor version. The readme's release table, c/README.md and the PlatformIO example pin the new tags, and the readme's tagging example moves on to js-v1.4.0 so it names a version that doesn't exist yet. 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.
selectedcontentis the only element in the HTML standard's element index (last updated 26 October 2026) thathtml.jsondidn't have. It goes inside a customizable<select>'s<button>and shows a copy of the chosen<option>. Its content model is nothing, but it isn't a void element, so it goes intagsand renders as<selectedcontent></selectedcontent>.Everything else already matches the spec. The other 112 elements are all there, nothing in
html.jsonhas been removed from the spec, and the 13 void elements match the spec's list exactly.Changes
documentation/html.json: addedselectedcontentafterselectSelectedcontent(...)/SelectedcontentAttr(...)inhtmb.hSelectedcontent/SelectedcontentAttrinHtmb.csselectedcontentinindex.js,index.d.ts,index.mjs(named export) andhtmb.umd.jsc/tests/cases.incTesting
npm testandnpm run test:typespassselect(button(selectedcontent()), option("A"))gives<select><button><selectedcontent></selectedcontent></button><option>A</option></select>in C and JSRelease
The second commit bumps each library a minor version for the new tag:
c/library.json2.1.0,HtmbLibrary.csproj2.3.0,package.json1.3.0. The readme release table,c/README.mdand the PlatformIO example pin the new tags. After merging, the merge commit gets taggedc-v2.1.0,cs-v2.3.0andjs-v1.3.0. cs-v2.3.0 is also the first NuGet release that lists the author as Larsenq.🤖 Generated with Claude Code