You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my legacy build for IE 11, the built CSS chunk contains hexadecimal RGBA notation, which IE 11 does not support. Unlike the JS files, no separate legacy chunk for CSS is built.
From what I read so far, since version 2.5 vite uses esbuild to minify CSS files. Through issue #4650 there was an enhancement to respect the given target configuration in the main build. However, nothing like that seems to exist for the configuration of the legacy build. Apologies if I am missing something obvious.
Check the built CSS chunk in the dist folder. You will find hexadecimal RGBA notation, e.g. for background-color. In the source file this is in functional notation.
Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
Describe the bug
In my legacy build for IE 11, the built CSS chunk contains hexadecimal RGBA notation, which IE 11 does not support. Unlike the JS files, no separate legacy chunk for CSS is built.
From what I read so far, since version 2.5 vite uses esbuild to minify CSS files. Through issue #4650 there was an enhancement to respect the given target configuration in the main build. However, nothing like that seems to exist for the configuration of the legacy build. Apologies if I am missing something obvious.
As a result, the styling in broken in IE 11.
Reproduction
npm install
npm run build
dist
folder. You will find hexadecimal RGBA notation, e.g. forbackground-color
. In the source file this is in functional notation.System Info
Used Package Manager
npm
Logs
No response
Validations
The text was updated successfully, but these errors were encountered: