Skip to content

Next v11.1#1285

Merged
fkhadra merged 11 commits into
mainfrom
next-v11.1
Apr 19, 2026
Merged

Next v11.1#1285
fkhadra merged 11 commits into
mainfrom
next-v11.1

Conversation

@fkhadra

@fkhadra fkhadra commented Apr 19, 2026

Copy link
Copy Markdown
Owner

WIP

fkhadra and others added 8 commits April 18, 2026 18:17
 Previously 'removed' fired at exit-animation-end (inside deleteToast), so observers saw events out of order when toast.dismiss() was followed quickly by another toast() call. React 19.2's concurrent rendering surfaced this more reliably.

Move the dispatchChanges('removed') call from deleteToast to markAsRemoved with an isActive guard for idempotency, and fix a latent NullPointerException in closeToast's membership check.

Closes #1275
@coveralls

coveralls commented Apr 19, 2026

Copy link
Copy Markdown

Coverage Status

Coverage is 84.954%next-v11.1 into main. No base build found for main.

`--y` is initialized as `0` (unitless), which works in bare
`translate3d(0, var(--y), 0)` contexts. However, when
`draggableDirection` is `'y'`, the drag handler builds
`calc(${delta}px + var(--y))` — and `calc()` requires compatible
units on both operands. `calc(50px + 0)` is invalid CSS, while
`calc(50px + 0px)` is valid.

This causes vertical drag to have no visible effect — the toast
fades via opacity but doesn't move, because the transform is
silently invalid.

Changing `--y: 0` to `--y: 0px` fixes vertical dragging with no
impact on existing behavior, since `0` and `0px` are identical
in all non-calc contexts.
@fkhadra fkhadra merged commit c800992 into main Apr 19, 2026
4 checks passed
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.

4 participants