Skip to content

Conversation

@anaskim
Copy link
Contributor

@anaskim anaskim commented Dec 12, 2025

V1 includes:

  • Rewording on interoperability.
  • Adds examples on current workarounds used by frameworks.
  • Adds goal to clarify the general and specific objectives of the proposal.
  • "behavior" -> "mixin", to avoid confusion with "behaviour" spelling.
  • Simplifies to add mixins to attachInternals() and avoid dynamic changes at runtime.
  • Adds mixins property to ElementInternals to query behaviors.
  • Removed "Open questions" section and expanded "Future Work" section with a "collision handling" note and 2 more proposed mixins (input and table behaviors).
  • Updated "Accessibility, Security, and Privacy Considerations" section.
  • Updated acknowledgements.

@anaskim anaskim marked this pull request as ready for review December 12, 2025 21:47

**Pros:**
- Familiar JavaScript pattern.
- Prototype-based composition.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another pro to this approach is that it allows for child classes to easily extend from mixins. e.g.

class CustomSubmitButton extends HTMLSubmitButtonMixin(HTMLElement) { ... }
class ExtraCustomSubmitButton extends CustomSubmitButton {...}

Is this possible with the current mixin proposal?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, we talked about in the meeting about child classes inheriting ElementInternals. I tested it and child classes do inherit the instance and can modify it. With the proposed approach we could have:

class ParentElement extends HTMLElement {
  #internals;

  constructor() {
    super();
    this.#internals = this.attachInternals();
    // ...
    this._internals = this.attachInternals({ mixins });
  }

  _getInternals() {
    return this.#internals;
  }
}

class ChildElement extends ParentElement {
  constructor() {
    super();
    const internals = this._getInternals();
    internals.role = 'checkbox'; 
    const isSubmit = this._internals.mixins.includes(HTMLSubmitButtonMixin);
    if (isSubmit) {
      // ...
    }
  }
}

**Cons:**
- Doesn't currently address form submission behavior.
- Scoped to specific attributes rather than general behaviors.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does it make sense to list "Extend Markup Like Customizable Select"? Or is that too different of a problem? The dealbreaking con with this approach is that it won't work for all types (or any types beyond select?).

https://developer.mozilla.org/en-US/docs/Learn_web_development/Extensions/Forms/Customizable_select

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, added it as an alternative. PTAL.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants