[Tooltip] Cannot read properties of undefined (reading 'duration')
Open
Nobody has claimed this yet.
on hold
package: material-pigment-css
platform: windows
scope: tooltip
- Dominant language
- JavaScript
- Stars
- 99.1k
- Forks
- 32.5k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 106
Description
Steps to reproduce
This bug will probably only be reproduced on Windows so the live example works fine, but I'll put it below anyway, please clone the repo and run it on a Windows device.
- live example: https://codesandbox.io/p/github/Talaxy009/astro-mui-issue/main
- github repo: https://github.com/Talaxy009/astro-mui-issue.git
setps:
- run the repo on a windows device
- put cursor over the button
Current behavior
- Run on windows: put cursor over the button and it disappeared, browser will output an error:
Uncaught TypeError: Cannot read properties of undefined (reading 'duration') - Run on Linux: put cursor over the button, Tooltip work fine
https://github.com/user-attachments/assets/1d5e8309-296e-4eee-837e-7cdecd1e0930
Expected behavior
- Run on windows: put cursor over the button, Tooltip work fine
- Run on Linux: put cursor over the button, Tooltip work fine
Context
I'm using pigment-css with material-ui on Astro
Your environment
npx @mui/envinfo
System:
OS: Windows 11 10.0.26100
Binaries:
Node: 20.14.0 - ~\AppData\Local\Temp\xfs-ceeefeb9\node.CMD
npm: 10.7.0 - D:\Program Files\fnm\aliases\default\npm.CMD
pnpm: Not Found
Browsers:
Chrome: Not Found
Edge: Chromium (131.0.2903.86)
npmPackages:
@emotion/react: 11.14.0
@emotion/styled: 11.14.1
@mui/core-downloads-tracker: 7.2.0
@mui/material: ^7.2.0 => 7.2.0
@mui/material-pigment-css: ^7.2.0 => 7.2.0
@mui/private-theming: 7.2.0
@mui/styled-engine: 7.2.0
@mui/system: 7.2.0
@mui/types: 7.4.4
@mui/utils: 7.2.0
@pigment-css/react: ^0.0.30 => 0.0.30
@pigment-css/vite-plugin: ^0.0.30 => 0.0.30
@types/react: ^19.1.8 => 19.1.8
react: ^19.1.0 => 19.1.0
react-dom: ^19.1.0 => 19.1.0
Search keywords: Cannot read properties of undefined (reading 'duration')
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.