Update dependency semantic-forms to v5.3.10 - #229
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/semantic-forms-5.x
branch
from
September 14, 2026 22:14
3fe5bcb to
dbefd4d
Compare
renovate
Bot
force-pushed
the
renovate/semantic-forms-5.x
branch
from
September 18, 2026 21:58
dbefd4d to
bf23338
Compare
renovate
Bot
force-pushed
the
renovate/semantic-forms-5.x
branch
from
September 21, 2026 20:24
bf23338 to
aa94a7b
Compare
This branch has not been deployed
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.
This PR contains the following updates:
5.3.5→5.3.10Release Notes
rooseveltframework/semantic-forms (semantic-forms)
v5.3.10Compare Source
v5.3.9Compare Source
v5.3.8Compare Source
v5.3.7Compare Source
v5.3.6Compare Source
switchattribute on checkboxes. Browsers with native support render their own switch; elsewhere Semantic Forms draws one, applies theswitchARIA role, and supports dragging the thumb to toggle it.col-1throughcol-5classes for placing a field in a particular grid column, which can be combined withcolspan-#. Like spans, positions fall back to normal flow when the form narrows to fewer columns than the class asks for.--semanticFormsInputColumnMaxWidthvariable, defaulting to1fr, which sets the widest an input column in the layout grid may grow.--semanticFormsInputMaxWidthis unchanged and still caps the field itself within its column.tabsclass holding one<fieldset>per tab becomes a tab strip, titled by each fieldset's<legend>, with thetabandtabpanelroles and arrow key navigation. Without JavaScript the fieldsets stay stacked and readable.data-display-valueattribute for range inputs, matching how every other per-field option is set. ThedisplayValueclass it replaces still works.<div>containing a checkbox rather than the one wrapping it, so every field inside such a container lost the space above its label.<dl>, which pushed anything the enhancer leaves alone, such as a<dd>containing only a button, to the top. Fields now stay where they were written.--semanticFormsInputHeightor--semanticFormsInputFontSizeis overridden.semanticForms()now takes an optional document or shadow root to search, so forms inside a shadow root can be enhanced withsemanticForms(myElement.shadowRoot). Each tree is watched separately, andreinitialize()works out which tree a form belongs to. Labels are now looked up in the form's own tree rather than the document, which is what previously stopped fields in a shadow root from being enhanced at all.readonlyordisabledattribute being given a clear button, which could empty a field the visitor is not meant to be able to change. A field made readonly after the enhancement has run has its clear button hidden by the stylesheet instead.fieldsetselector gave every fieldset on the host page a container context, which then applied the responsive grid to any<dl>inside any fieldset, and the.checkboxes/.radioslist rule was not scoped to the form either.Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.