-
Notifications
You must be signed in to change notification settings - Fork 12k
CSS Extracted/Optimized Incorrectly With Prod Flag #13814
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi, can you kindly try to update to the latest version of |
I updated |
Hi, I looked into this and it seems that the bug is in clean-css. Please contact the author(s) of the clean-css project or file an issue on their issue tracker. Thanks |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
🐞 Bug report
Command (mark with an
x
)Is this a regression?
Unknown.
A new third-party library was added to the application. The new library is what is affected.
Description
A CSS stylesheet included in a third-party library is incorrectly rendered when the
ng build --prod
command is used.🔬 Minimal Reproduction
Because this seems file dependent I have created a basic repo to reproduce this issue at:
https://github.com/mcavagnaro/dhtmlxgantt-css-issue
Two changes were made after using the
ng new
command:src/third-party/dhtmlxgantt.css
was added.angular.json
file was added to include this new CSS file.After downloading the app run
ng build --prod
and compare the CSS file in thedist
folder to what is in the original file. The rule that is changed is.gantt_task_line.gantt_milestone .gantt_task_content
.🔥 Exception or Error
The
border
property is what changed. It starts off asborder: inherit;
and becomesborder: 1px inherit inherit;
. It looks like it's being merged with theborder-width
property, but I'm not sure where the secondinherit
is coming from.Original:
Rendered:
🌍 Your Environment
Anything else relevant?
Similar to #12408
The text was updated successfully, but these errors were encountered: