Olivier Tassinari
@oliviert.com
Co-founder and CEO at @MUI_hq • co-creator of @MaterialUI • studied @telecomparis • ex @doctolib
What I understand of this:
- There was a PR from an open-source contributor
- He checked out the branch.
- In the branch, there might have been a new npm dependency that ran a post-install script, which exfiltrated his npm credentials.
- There was a PR from an open-source contributor
- He checked out the branch.
- In the branch, there might have been a new npm dependency that ran a post-install script, which exfiltrated his npm credentials.
September 17, 2025 at 12:07 AM
What I understand of this:
- There was a PR from an open-source contributor
- He checked out the branch.
- In the branch, there might have been a new npm dependency that ran a post-install script, which exfiltrated his npm credentials.
- There was a PR from an open-source contributor
- He checked out the branch.
- In the branch, there might have been a new npm dependency that ran a post-install script, which exfiltrated his npm credentials.
September 16, 2025 at 11:03 PM
The 4 principles are respected.
September 16, 2025 at 5:22 PM
The 4 principles are respected.
I don't understand.
Do you have reference material from WCAG that would support this? As far as I know, this component respects www.w3.org/WAI/WCAG21/U....
Do you have reference material from WCAG that would support this? As far as I know, this component respects www.w3.org/WAI/WCAG21/U....
Introduction to Understanding WCAG 2.1 | WAI | W3C
www.w3.org
September 16, 2025 at 5:21 PM
I don't understand.
Do you have reference material from WCAG that would support this? As far as I know, this component respects www.w3.org/WAI/WCAG21/U....
Do you have reference material from WCAG that would support this? As far as I know, this component respects www.w3.org/WAI/WCAG21/U....
As I understand it, a screenreader user can't know if a link has a preview card or doesn't have one, it's invisible. The experience for them is the same.
So if they want to navigate to see the content of the link, they navigate, if they don't want to, they don't.
So if they want to navigate to see the content of the link, they navigate, if they don't want to, they don't.
September 16, 2025 at 11:57 AM
As I understand it, a screenreader user can't know if a link has a preview card or doesn't have one, it's invisible. The experience for them is the same.
So if they want to navigate to see the content of the link, they navigate, if they don't want to, they don't.
So if they want to navigate to see the content of the link, they navigate, if they don't want to, they don't.
It's a preview of the link, so the content is accessible to user who rely on assistive technology.
September 16, 2025 at 8:44 AM
It's a preview of the link, so the content is accessible to user who rely on assistive technology.
I don't understand what's not accessible about this React component?
This is to show a preview of the link that will be clicked on. It's designed to be invisible for VoiceOver, JAWS, or NVDA users.
The WCAG 2.1 success criteria seem OK, e.g.
2.1.1 Keyboard: "Enter" shows the same content.
This is to show a preview of the link that will be clicked on. It's designed to be invisible for VoiceOver, JAWS, or NVDA users.
The WCAG 2.1 success criteria seem OK, e.g.
2.1.1 Keyboard: "Enter" shows the same content.
September 15, 2025 at 9:34 PM
I don't understand what's not accessible about this React component?
This is to show a preview of the link that will be clicked on. It's designed to be invisible for VoiceOver, JAWS, or NVDA users.
The WCAG 2.1 success criteria seem OK, e.g.
2.1.1 Keyboard: "Enter" shows the same content.
This is to show a preview of the link that will be clicked on. It's designed to be invisible for VoiceOver, JAWS, or NVDA users.
The WCAG 2.1 success criteria seem OK, e.g.
2.1.1 Keyboard: "Enter" shows the same content.
We are literally trying to find a solution to this on the Material UI button loading state right now. A proper fix would be amazing.
January 10, 2025 at 3:08 PM
We are literally trying to find a solution to this on the Material UI button loading state right now. A proper fix would be amazing.
We could do more to ease the switch, e.g. github.com/mui/base-ui/..., but unclear if it's needed.
[discussion] Create deprecated props to ease Radix Primitives migration? · Issue #601 · mui/base-ui
Summary This is an idea that started from: #39 (comment). Maybe it would make sense to create deprecated props for all the APIs that are different from Radix Primitives, making the migration super ...
github.com
December 27, 2024 at 4:53 PM
We could do more to ease the switch, e.g. github.com/mui/base-ui/..., but unclear if it's needed.
The APIs were design by starting from the Radix Primitives API, and then evolving them based on:
- Learnings from Radix Primitives
- Learnings from Material UI test suite
- React 19 new API, e.g. now the ref is a regular prop
- Learnings from Radix Primitives
- Learnings from Material UI test suite
- React 19 new API, e.g. now the ref is a regular prop
December 27, 2024 at 4:53 PM
The APIs were design by starting from the Radix Primitives API, and then evolving them based on:
- Learnings from Radix Primitives
- Learnings from Material UI test suite
- React 19 new API, e.g. now the ref is a regular prop
- Learnings from Radix Primitives
- Learnings from Material UI test suite
- React 19 new API, e.g. now the ref is a regular prop
It's too easy to forget that end-users have slow hardware too.
November 23, 2024 at 9:52 PM
It's too easy to forget that end-users have slow hardware too.
I have reality appreciated working with slow hardware in the past. Any performance regressions becomes so obvious.
November 23, 2024 at 9:51 PM
I have reality appreciated working with slow hardware in the past. Any performance regressions becomes so obvious.