feat(webkit): give chip three kinds and hand presence to the consumer

[gabriel-lisboa-azion]

What

Chip gains a kind axis covering the three jobs it actually does in a filter surface, so a consumer never has to restyle the component to get one of them:

kind	Job	Treatment
filled (default)	a value that is applied	raised surface, border, shadow — the loudest, because it is state
outlined	a value the user could apply	same border, no fill, no shadow — recedes to an offer without becoming disabled
dashed	the control that creates a chip	dashed outline, the standing "add another one of these" convention

The breaking part: presence is the consumer's

remove used to fade the chip to opacity: 0 and only then emit, so the chip decided its own disappearance. That could serve exactly one case — where removing a value also destroys the chip. A filter bar where a removed value stays on screen as an outlined offer was impossible: the instance stayed invisible forever.

remove now fires immediately and the chip stays mounted. Exit motion, where wanted, belongs to whatever owns the list — so table-applied-filters gains the TransitionGroup that actually destroys chips. That is why it ships in this PR: split apart, one half double-animates removal and the other un-animates it.

The inline style="transition: …" the old fade needed is gone too — an inline transition beats every transition-* class a consumer puts on the same element (see #881).

Also

• The remove control is named after what it removes: aria-label="Remove Production", with a Tooltip carrying the same string, and a 24×24 target at medium (WCAG 2.5.8). A row of chips whose every button says "Remove" is unusable by voice or screen reader.
• Enter/Space dispatch a real DOM click, so a Chip works as a Popover.Trigger / Dropdown.Trigger child from the keyboard.
• Both sizes are now fixed heights (24px / 32px) rather than padding-driven, so a row of chips shares one baseline.
• Adds the missing .size-limit.json row — chip now carries Tooltip, and nothing was measuring that. 4.27 KB gzipped against a 5 KB budget.

BREAKING CHANGE

• remove no longer waits for a fade before emitting, and the chip no longer unmounts itself. A consumer relying on self-dismissal must now drop the chip from its own collection.
• small is a fixed 24px (was 20px) and medium a fixed 32px (was ~30px from padding); medium uses text-label-sm.

Verification

33 chip tests pass, including the two that pin the new contract — "stays mounted after remove" and "declares no inline transition on the root". Catalog regenerated on this branch (not carried), so catalog:check is clean.

[gabriel-lisboa-azion]

What

Chip gains a kind axis covering the three jobs it actually does in a filter surface, so a consumer never has to restyle the component to get one of them:

kind	Job	Treatment
filled (default)	a value that is applied	raised surface, border, shadow — the loudest, because it is state
outlined	a value the user could apply	same border, no fill, no shadow — recedes to an offer without becoming disabled
dashed	the control that creates a chip	dashed outline, the standing "add another one of these" convention

The breaking part: presence is the consumer's

remove used to fade the chip to opacity: 0 and only then emit, so the chip decided its own disappearance. That could serve exactly one case — where removing a value also destroys the chip. A filter bar where a removed value stays on screen as an outlined offer was impossible: the instance stayed invisible forever.

remove now fires immediately and the chip stays mounted. Exit motion, where wanted, belongs to whatever owns the list — so table-applied-filters gains the TransitionGroup that actually destroys chips. That is why it ships in this PR: split apart, one half double-animates removal and the other un-animates it.

The inline style="transition: …" the old fade needed is gone too — an inline transition beats every transition-* class a consumer puts on the same element (see #881).

Also

• The remove control is named after what it removes: aria-label="Remove Production", with a Tooltip carrying the same string, and a 24×24 target at medium (WCAG 2.5.8). A row of chips whose every button says "Remove" is unusable by voice or screen reader.
• Enter/Space dispatch a real DOM click, so a Chip works as a Popover.Trigger / Dropdown.Trigger child from the keyboard.
• Both sizes are now fixed heights (24px / 32px) rather than padding-driven, so a row of chips shares one baseline.
• Adds the missing .size-limit.json row — chip now carries Tooltip, and nothing was measuring that. 4.27 KB gzipped against a 5 KB budget.

BREAKING CHANGE

• remove no longer waits for a fade before emitting, and the chip no longer unmounts itself. A consumer relying on self-dismissal must now drop the chip from its own collection.
• small is a fixed 24px (was 20px) and medium a fixed 32px (was ~30px from padding); medium uses text-label-sm.

Verification

33 chip tests pass, including the two that pin the new contract — "stays mounted after remove" and "declares no inline transition on the root". Catalog regenerated on this branch (not carried), so catalog:check is clean.

[gabriel-lisboa-azion]

What

Chip gains a kind axis covering the three jobs it actually does in a filter surface, so a consumer never has to restyle the component to get one of them:

kind	Job	Treatment
filled (default)	a value that is applied	raised surface, border, shadow — the loudest, because it is state
outlined	a value the user could apply	same border, no fill, no shadow — recedes to an offer without becoming disabled
dashed	the control that creates a chip	dashed outline, the standing "add another one of these" convention

The breaking part: presence is the consumer's

remove used to fade the chip to opacity: 0 and only then emit, so the chip decided its own disappearance. That could serve exactly one case — where removing a value also destroys the chip. A filter bar where a removed value stays on screen as an outlined offer was impossible: the instance stayed invisible forever.

remove now fires immediately and the chip stays mounted. Exit motion, where wanted, belongs to whatever owns the list — so table-applied-filters gains the TransitionGroup that actually destroys chips. That is why it ships in this PR: split apart, one half double-animates removal and the other un-animates it.

The inline style="transition: …" the old fade needed is gone too — an inline transition beats every transition-* class a consumer puts on the same element (see #881).

Also

• The remove control is named after what it removes: aria-label="Remove Production", with a Tooltip carrying the same string, and a 24×24 target at medium (WCAG 2.5.8). A row of chips whose every button says "Remove" is unusable by voice or screen reader.
• Enter/Space dispatch a real DOM click, so a Chip works as a Popover.Trigger / Dropdown.Trigger child from the keyboard.
• Both sizes are now fixed heights (24px / 32px) rather than padding-driven, so a row of chips shares one baseline.
• Adds the missing .size-limit.json row — chip now carries Tooltip, and nothing was measuring that. 4.27 KB gzipped against a 5 KB budget.

BREAKING CHANGE

• remove no longer waits for a fade before emitting, and the chip no longer unmounts itself. A consumer relying on self-dismissal must now drop the chip from its own collection.
• small is a fixed 24px (was 20px) and medium a fixed 32px (was ~30px from padding); medium uses text-label-sm.

Verification

33 chip tests pass, including the two that pin the new contract — "stays mounted after remove" and "declares no inline transition on the root". Catalog regenerated on this branch (not carried), so catalog:check is clean.

[gabriel-lisboa-azion]

What

Chip gains a kind axis covering the three jobs it actually does in a filter surface, so a consumer never has to restyle the component to get one of them:

kind	Job	Treatment
filled (default)	a value that is applied	raised surface, border, shadow — the loudest, because it is state
outlined	a value the user could apply	same border, no fill, no shadow — recedes to an offer without becoming disabled
dashed	the control that creates a chip	dashed outline, the standing "add another one of these" convention

The breaking part: presence is the consumer's

remove used to fade the chip to opacity: 0 and only then emit, so the chip decided its own disappearance. That could serve exactly one case — where removing a value also destroys the chip. A filter bar where a removed value stays on screen as an outlined offer was impossible: the instance stayed invisible forever.

remove now fires immediately and the chip stays mounted. Exit motion, where wanted, belongs to whatever owns the list — so table-applied-filters gains the TransitionGroup that actually destroys chips. That is why it ships in this PR: split apart, one half double-animates removal and the other un-animates it.

The inline style="transition: …" the old fade needed is gone too — an inline transition beats every transition-* class a consumer puts on the same element (see #881).

Also

• The remove control is named after what it removes: aria-label="Remove Production", with a Tooltip carrying the same string, and a 24×24 target at medium (WCAG 2.5.8). A row of chips whose every button says "Remove" is unusable by voice or screen reader.
• Enter/Space dispatch a real DOM click, so a Chip works as a Popover.Trigger / Dropdown.Trigger child from the keyboard.
• Both sizes are now fixed heights (24px / 32px) rather than padding-driven, so a row of chips shares one baseline.
• Adds the missing .size-limit.json row — chip now carries Tooltip, and nothing was measuring that. 4.27 KB gzipped against a 5 KB budget.

BREAKING CHANGE

• remove no longer waits for a fade before emitting, and the chip no longer unmounts itself. A consumer relying on self-dismissal must now drop the chip from its own collection.
• small is a fixed 24px (was 20px) and medium a fixed 32px (was ~30px from padding); medium uses text-label-sm.

Verification

33 chip tests pass, including the two that pin the new contract — "stays mounted after remove" and "declares no inline transition on the root". Catalog regenerated on this branch (not carried), so catalog:check is clean.

[gabriel-lisboa-azion]

What

Chip gains a kind axis covering the three jobs it actually does in a filter surface, so a consumer never has to restyle the component to get one of them:

kind	Job	Treatment
filled (default)	a value that is applied	raised surface, border, shadow — the loudest, because it is state
outlined	a value the user could apply	same border, no fill, no shadow — recedes to an offer without becoming disabled
dashed	the control that creates a chip	dashed outline, the standing "add another one of these" convention

The breaking part: presence is the consumer's

remove used to fade the chip to opacity: 0 and only then emit, so the chip decided its own disappearance. That could serve exactly one case — where removing a value also destroys the chip. A filter bar where a removed value stays on screen as an outlined offer was impossible: the instance stayed invisible forever.

remove now fires immediately and the chip stays mounted. Exit motion, where wanted, belongs to whatever owns the list — so table-applied-filters gains the TransitionGroup that actually destroys chips. That is why it ships in this PR: split apart, one half double-animates removal and the other un-animates it.

The inline style="transition: …" the old fade needed is gone too — an inline transition beats every transition-* class a consumer puts on the same element (see #881).

Also

• The remove control is named after what it removes: aria-label="Remove Production", with a Tooltip carrying the same string, and a 24×24 target at medium (WCAG 2.5.8). A row of chips whose every button says "Remove" is unusable by voice or screen reader.
• Enter/Space dispatch a real DOM click, so a Chip works as a Popover.Trigger / Dropdown.Trigger child from the keyboard.
• Both sizes are now fixed heights (24px / 32px) rather than padding-driven, so a row of chips shares one baseline.
• Adds the missing .size-limit.json row — chip now carries Tooltip, and nothing was measuring that. 4.27 KB gzipped against a 5 KB budget.

BREAKING CHANGE

• remove no longer waits for a fade before emitting, and the chip no longer unmounts itself. A consumer relying on self-dismissal must now drop the chip from its own collection.
• small is a fixed 24px (was 20px) and medium a fixed 32px (was ~30px from padding); medium uses text-label-sm.

Verification

33 chip tests pass, including the two that pin the new contract — "stays mounted after remove" and "declares no inline transition on the root". Catalog regenerated on this branch (not carried), so catalog:check is clean.

[gabriel-lisboa-azion]

What

Chip gains a kind axis covering the three jobs it actually does in a filter surface, so a consumer never has to restyle the component to get one of them:

kind	Job	Treatment
filled (default)	a value that is applied	raised surface, border, shadow — the loudest, because it is state
outlined	a value the user could apply	same border, no fill, no shadow — recedes to an offer without becoming disabled
dashed	the control that creates a chip	dashed outline, the standing "add another one of these" convention

The breaking part: presence is the consumer's

remove used to fade the chip to opacity: 0 and only then emit, so the chip decided its own disappearance. That could serve exactly one case — where removing a value also destroys the chip. A filter bar where a removed value stays on screen as an outlined offer was impossible: the instance stayed invisible forever.

remove now fires immediately and the chip stays mounted. Exit motion, where wanted, belongs to whatever owns the list — so table-applied-filters gains the TransitionGroup that actually destroys chips. That is why it ships in this PR: split apart, one half double-animates removal and the other un-animates it.

The inline style="transition: …" the old fade needed is gone too — an inline transition beats every transition-* class a consumer puts on the same element (see #881).

Also

• The remove control is named after what it removes: aria-label="Remove Production", with a Tooltip carrying the same string, and a 24×24 target at medium (WCAG 2.5.8). A row of chips whose every button says "Remove" is unusable by voice or screen reader.
• Enter/Space dispatch a real DOM click, so a Chip works as a Popover.Trigger / Dropdown.Trigger child from the keyboard.
• Both sizes are now fixed heights (24px / 32px) rather than padding-driven, so a row of chips shares one baseline.
• Adds the missing .size-limit.json row — chip now carries Tooltip, and nothing was measuring that. 4.27 KB gzipped against a 5 KB budget.

BREAKING CHANGE

• remove no longer waits for a fade before emitting, and the chip no longer unmounts itself. A consumer relying on self-dismissal must now drop the chip from its own collection.
• small is a fixed 24px (was 20px) and medium a fixed 32px (was ~30px from padding); medium uses text-label-sm.

Verification

33 chip tests pass, including the two that pin the new contract — "stays mounted after remove" and "declares no inline transition on the root". Catalog regenerated on this branch (not carried), so catalog:check is clean.

[gabriel-lisboa-azion]

What

Chip gains a kind axis covering the three jobs it actually does in a filter surface, so a consumer never has to restyle the component to get one of them:

kind	Job	Treatment
filled (default)	a value that is applied	raised surface, border, shadow — the loudest, because it is state
outlined	a value the user could apply	same border, no fill, no shadow — recedes to an offer without becoming disabled
dashed	the control that creates a chip	dashed outline, the standing "add another one of these" convention

The breaking part: presence is the consumer's

remove used to fade the chip to opacity: 0 and only then emit, so the chip decided its own disappearance. That could serve exactly one case — where removing a value also destroys the chip. A filter bar where a removed value stays on screen as an outlined offer was impossible: the instance stayed invisible forever.

remove now fires immediately and the chip stays mounted. Exit motion, where wanted, belongs to whatever owns the list — so table-applied-filters gains the TransitionGroup that actually destroys chips. That is why it ships in this PR: split apart, one half double-animates removal and the other un-animates it.

The inline style="transition: …" the old fade needed is gone too — an inline transition beats every transition-* class a consumer puts on the same element (see #881).

Also

• The remove control is named after what it removes: aria-label="Remove Production", with a Tooltip carrying the same string, and a 24×24 target at medium (WCAG 2.5.8). A row of chips whose every button says "Remove" is unusable by voice or screen reader.
• Enter/Space dispatch a real DOM click, so a Chip works as a Popover.Trigger / Dropdown.Trigger child from the keyboard.
• Both sizes are now fixed heights (24px / 32px) rather than padding-driven, so a row of chips shares one baseline.
• Adds the missing .size-limit.json row — chip now carries Tooltip, and nothing was measuring that. 4.27 KB gzipped against a 5 KB budget.

BREAKING CHANGE

• remove no longer waits for a fade before emitting, and the chip no longer unmounts itself. A consumer relying on self-dismissal must now drop the chip from its own collection.
• small is a fixed 24px (was 20px) and medium a fixed 32px (was ~30px from padding); medium uses text-label-sm.

Verification

33 chip tests pass, including the two that pin the new contract — "stays mounted after remove" and "declares no inline transition on the root". Catalog regenerated on this branch (not carried), so catalog:check is clean.

[gabriel-lisboa-azion]

What

Chip gains a kind axis covering the three jobs it actually does in a filter surface, so a consumer never has to restyle the component to get one of them:

kind	Job	Treatment
filled (default)	a value that is applied	raised surface, border, shadow — the loudest, because it is state
outlined	a value the user could apply	same border, no fill, no shadow — recedes to an offer without becoming disabled
dashed	the control that creates a chip	dashed outline, the standing "add another one of these" convention

The breaking part: presence is the consumer's

remove used to fade the chip to opacity: 0 and only then emit, so the chip decided its own disappearance. That could serve exactly one case — where removing a value also destroys the chip. A filter bar where a removed value stays on screen as an outlined offer was impossible: the instance stayed invisible forever.

remove now fires immediately and the chip stays mounted. Exit motion, where wanted, belongs to whatever owns the list — so table-applied-filters gains the TransitionGroup that actually destroys chips. That is why it ships in this PR: split apart, one half double-animates removal and the other un-animates it.

The inline style="transition: …" the old fade needed is gone too — an inline transition beats every transition-* class a consumer puts on the same element (see #881).

Also

• The remove control is named after what it removes: aria-label="Remove Production", with a Tooltip carrying the same string, and a 24×24 target at medium (WCAG 2.5.8). A row of chips whose every button says "Remove" is unusable by voice or screen reader.
• Enter/Space dispatch a real DOM click, so a Chip works as a Popover.Trigger / Dropdown.Trigger child from the keyboard.
• Both sizes are now fixed heights (24px / 32px) rather than padding-driven, so a row of chips shares one baseline.
• Adds the missing .size-limit.json row — chip now carries Tooltip, and nothing was measuring that. 4.27 KB gzipped against a 5 KB budget.

BREAKING CHANGE

• remove no longer waits for a fade before emitting, and the chip no longer unmounts itself. A consumer relying on self-dismissal must now drop the chip from its own collection.
• small is a fixed 24px (was 20px) and medium a fixed 32px (was ~30px from padding); medium uses text-label-sm.

Verification

33 chip tests pass, including the two that pin the new contract — "stays mounted after remove" and "declares no inline transition on the root". Catalog regenerated on this branch (not carried), so catalog:check is clean.