The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
ionic-framework	Ready	Preview, Comment	Jan 20, 2026 9:08pm

Great work — thank you for this improvement!

I noticed one potential limitation: since dual-knobs is not reflected in the DOM, using [dualKnobs]="true" makes this approach difficult to use in practice. We may want to think about how dual-knobs should be handled.

Two possible options could be:

1. Also set a .use-dual-knobs class (this would be the quickest solution).
2. When dual-knobs is enabled, provide part="knob knob-a" / part="knob knob-b".

ex:

  &:not(.dual-knobs).range-pressed {
    &.range-value-min::part(knob) {}
    &.range-value-max::part(knob) {}
  }

  &.dual-knobs.range-pressed {
    &.range-value-min::part(knob-a) {}
    &.range-value-max::part(knob-b) {}
  }

Either of these would greatly expand how this can be leveraged.

Thank you for the feedback @rdlabo! I am actually working on adding knob-a and knob-b parts this week to resolve #29862 and it will also go in the v8.8 release. I will take a look at adding a dual-knobs class too though either on this PR or the one for that feature. I may reach out to you on Discord with a question on how the knobs should act when they switch places. 🙂

This is a fantastic improvement — it really expands the customization possibilities a lot. 🙌
Let’s discuss dual-knobs and how the knobs should behave separately!