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
[4.0-dev] Fixing SCSS issues with division deprecation and math.div() #35648
Conversation
Mirror commit for 4.0-dev from joomla#35645
Co-authored-by: Tobias Zulauf <zero-24@users.noreply.github.com>
* Add a new Icon for com_tags to the quicicon module * Update administrator/language/en-GB/com_tags.ini Co-authored-by: Brian Teeman <brian@teeman.net> Co-authored-by: Brian Teeman <brian@teeman.net>
…omla#31675) * Actionlogs: Added parameter to disable relative timestamps. * Update administrator/components/com_actionlogs/config.xml Co-authored-by: Quy <quy@fluxbb.org> * Apply suggestions from code review Co-authored-by: Quy <quy@fluxbb.org> Co-authored-by: Quy <quy@fluxbb.org>
* log:logDeprecated * use new log method * new log method, improve callStack lookup * phpcs * phpcs * Check deprecation logging on boot * trigger_error everywhere * use namespaced classes
* add Joomla! Accessibility Team to the code owners * add cassiopeia * add everything in the templates
a fix for joomla#35639
|
@brianteeman I've completed the PR for [4.0-dev] it should be a valid build. After this merge, the same changes are required for [4.1-dev] asap. I've updated the description. Please let me know if this PR needs anything. |
|
I tried to test this but in order to do so I need to be able to replicate the problem that this is fixing. I have been unable to replicate the problem |
|
@brianteeman it may be impossible to replicate the issue right now. The I can try to write a step-by-step guide on how you might replicate the problem, but once
I think that for a minor SCSS consistency can pass through the |
|
@brianteeman @dgrammatiko what's up with this appveyor issue? |
|
I'm tempted to sit on the FA Fix until they fix upstream (it is 1.5 months out which is a bit annoying per FortAwesome/Font-Awesome#18371 ) - but saves us overriding warnings for the sake of it. Obviously the rest of the fixes are good. |
|
Well thanks for someone finally say anything. Cheers |
|
The math.div issue can be resolved locally by applying (and fiddling with) the recommendations in the article mentioned earlier (https://sass-lang.com/documentation/breaking-changes/slash-div), even the fontawesome-free issue. This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/35648. |
|
@wilsonge maybe you should press the green button here? |
|
@thednp could you please have a look here and resolve conflicts? |
|
@chmst unfortunately this is too late for me to do anything, I don't have write access here anymore. |
|
You never did - that message is related to who can merge the file into core. |
|
Not true, if changes after my PR would have been into less than 3 files, I could resolve conflicts. I used to do that for the package-lock.json for the color-picker PR. Both resolve cases are for you to resolve. |
|
@thednp @brianteeman @chmst I could rebase this PR for 4.1 but are you willing to test it so it could be finally merged? |
|
@dgrammatiko I took a look at doing it but the 8 files here are only a small number of the ones that need updating |
|
@brianteeman you mean there are still deprecation notices after applying these changes? |
|
Deleted my post as its the same thing I posted earlier and I think it might have been my fault |
|
actually no idea. The error report AFTER my version of this pr is the same as #35648 (comment) from september |
|
@dgrammatiko IDK man, I'm out of touch with this lately. I would say go ahead and if you get more deprecation notice, have a look at my changes and apply same methods. |
|
#36906 should fix this but:
|
|
This pull request has automatically rebased to 4.2-dev. |
|
This was already fixed with another pr |
|
Fixed per #37255 |

Pull Request for PR #35639 .
Important
This PR could be merged into [4.1-dev] as well.
Summary of Changes
The fontawesome icon library haven't marked their
$fa-fw-widthvariable with!default, see #17482 which uses(20em / 16)expression which is deprecated in dart-sass 2.0 and also largely reported in the fontawesome issues.Other changes in this PR also address other dart-sass issues, but we don't replace for instance
24 / 16withmath.div(24, 16)as recommended by the compiler, but with24 * 0.0625(which is the result of 1/16) and the reason for that is the libsass compiler still largely used and this approach is also widely adopted. I suspect scssPhp also might not havemathimplemented.See this PR in fontawesome for more info. Briefly, Bootstrap core devs also continue to support libsass, so should we.
Testing Instructions
Check SASS compiler output. You should see all SCSS compiled. If the npm build is green, there is no need to test anything else.
Actual result BEFORE applying this Pull Request
The SCSS compiler just won't do division via the
/(forward slash) operator, the build will simply failhttps://ci.joomla.org/joomla/joomla-cms/47599
Expected result AFTER applying this Pull Request
All SCSS files compiled successful.
Documentation Changes Required
No.