hi... isn´t it more like percentage(divide(1, $count))? cause 100 gives eg. 333.33333% back.

hi... isn´t it more like percentage(divide(1, $count))? cause 100 gives eg. 333.33333% back.

Yes you are right. I changed it ad76686

Now the percentages are correct.

So to use Bootstrap in a project including this pull request, you can either use:
npm install --save-dev twbs/bootstrap#39030/head
or:
yarn add --dev twbs/bootstrap#39030/head
(remove --save-dev or --dev if you want to add it as a dependency rather than a dev dependency)

Bootstrap v4.6 has the same issue

@twbs/css-review we might also need to backport the fix in the rfs repo. If someone fixes the issue there, please CC me.

Another possibility is the following tested by @louismaximepiton (https://github.com/twbs/bootstrap/compare/main-lmp-abs-warning-fix + fix in twbs/rfs) which would make it transparent even for folks using divide() in their own context/project.

We tried something via #39132 but fixing divide() by handling the dividend unit doesn't seem compatible with node-sass we still maintain (see #39132 (comment)).

I suggest that we merge + ship this patch. And then, if we get rid of the node-sass compatibility in v6, go with a solution based on what's in #39132.

It means that there would be nothing to do for now in twbs/rfs.

@twbs/css-review all fine with this proposal? Thoughts?

@julien-deramond any chance to see this patch backported in BS 4.x?

@n-rodriguez Bootstrap 4 has been EOL since 2023-01-01, so unfortunately there won't be a patch backported to it.
I haven't tested it but if you're using Sass, there's prolly a way to override the part that generates the deprecation warning on your side.