Skip to content

Conversation

@mkszepp
Copy link
Collaborator

@mkszepp mkszepp commented Dec 14, 2025

Similar to @triggerHtmlTag (#1033), we need to introduce @contentHtmlTag to achieve full Glint compliance in next major.
This allows addon consumers to adopt the new approach in v8 and avoid having to make this change during the migration to v9.

Before:

<BasicDropdown as |dd|>
  <dd.Trigger>Click me!</dd.Trigger>
  <dd.Content @htmlTag="span">
    Content
  </dd.Content>
</BasicDropdown>

After:

<BasicDropdown @contentHtmlTag="span" as |dd|>
  <dd.Trigger>Click me!</dd.Trigger>
  <dd.Content>
    Content
  </dd.Content>
</BasicDropdown>

@mkszepp mkszepp merged commit f2b38e2 into v8 Dec 14, 2025
23 checks passed
@mkszepp mkszepp deleted the add-content-html-tag branch December 14, 2025 06:30
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.

2 participants