3 ms·
Blink, Chrome's rendering engine, was forked from WebKit (Safari) in 2013. Since WebKit already supported the infinity value at the time of the fork [0], it's
by maxloh 1y ago
Blink, Chrome's rendering engine, was forked from WebKit (Safari) in 2013.
Since WebKit already supported the infinity value at the time of the fork [0], it's highly probable that they share the same underlying code. This would explain their similar behavior.
[0]: https://caniuse.com/?search=infinity https://caniuse.com/?search=infinity
- chrismorgan 1y agoYou’re confusing the JavaScript keyword Infinity, which has been around forever, with the CSS keyword infinity, which has only been around for 2–3 years <https://caniuse.com/mdn-css_types_calc-keyword_infinity https://caniuse.com/mdn-css_types_calc-keyword_infinity>. And actually I’d be quite surprised if the infinity keyword is even relevant here; I would expect the same results if you changed each calc(infinity * 1px) to 9999999999999999px. Firefox (and, if you go far enough back, IE) will still ignore overly large height declarations, and WebKit-heritage browsers will clamp it.
- maxloh 1y agoThanks for the clarification. However, the number is likely encoded in binary format, which is why you're seeing 2²⁵ in the article.