Skip to content

Treat DOMTokenList.toggle undefined force as omitted - #334

Open
dyk1454683243-sudo wants to merge 1 commit into
WebReflection:mainfrom
dyk1454683243-sudo:cursor/fix-tokenlist-toggle-undefined-force-277-a6f2
Open

dyk1454683243-sudo wants to merge 1 commit into
WebReflection:mainfrom
dyk1454683243-sudo:cursor/fix-tokenlist-toggle-undefined-force-277-a6f2

Conversation

@dyk1454683243-sudo

Copy link
Copy Markdown

Fixes #277

DOMTokenList.toggle(token, force) now treats force === undefined like an omitted second argument (plain toggle), matching browsers and Web IDL optional boolean.

  • Missing token + undefined force → add (same as one-arg toggle)
  • Present token + undefined force → remove
  • force true / false still force-add / force-remove

Focused change in esm/dom/token-list.js (CJS mirrored) plus regression tests.

Web IDL optional boolean means toggle(token, undefined) must
plain-toggle like a one-argument call, not coerce undefined to false.

Fixes WebReflection#277

Co-authored-by: David <dyk1454683243-sudo@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

In 'HTMLElement.classList.toggle' the 'force' attribute works uncorrectly.

2 participants