91413[WIP][TASK] Avoid CSS Nano errors due to usage of calc()
Commit message
Review
-
Code review CR -1
- Benjamin Franzke -1
-
Verified V -1
- core-ci -1 CI
Files 8
- Build/Gruntfile.js+3 −0
- Build/package-lock.json+34 −59
- typo3/sysext/adminpanel/Resources/Public/Css/adminpanel.css+9 −9
- typo3/sysext/backend/Resources/Public/Css/backend.css+161 −161
- typo3/sysext/dashboard/Resources/Public/Css/dashboard.css+6 −6
- typo3/sysext/form/Resources/Public/Css/form.css+13 −13
- typo3/sysext/styleguide/Resources/Public/Css/styleguide-frontend.css+27 −27
- typo3/sysext/workspaces/Resources/Public/Css/preview.css+2 −2
Review log 67
-
Benni Mack uploaded patch set 1 11/03/25, 16:57
-
Benjamin Franzke commented on patch set 1 CR -1 11/03/25, 16:59
Yes, this avoids the warnings, but also disabled all optimizations for those `calc()` statements that are understood. We should keep them, even if the situation is not nice. -
Benjamin Franzke commented on patch set 1 11/03/25, 17:02
Reply
So if this is blocking someone and to be constructive (😜), we should try to add "ignore" statements… I haven't looked up how that works in this case, but still wanted to mention that as a possibility. -
core-ci voted on patch set 1 V -1 11/03/25, 17:05 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/88402
-
Benni Mack commented on patch set 1 11/03/25, 17:07
Reply
The reason why I created it: Well, it shows up every time when I build the CSS with " Lexical error on line 1: Unrecognized text." so I assume this is an error, I'd like to have no errors when handling CSS. I had 10 contributors last week where I told them "Yes, there are errors, but don't look at it too closely, this is "normal" makes it hard to teach them when there is an error they should look out to, or errors we should keep. -
Benni Mack abandoned the change 11/03/25, 17:07
-
Benjamin Franzke commented on patch set 1 11/03/25, 17:12
Reply
Yup, I see and agree with the hurdle . Therefore I wrote: > we should try to add "ignore" statements