Summary: | Nested calculations using intermediate CSS Custom Properties don't work | ||
---|---|---|---|
Product: | WebKit | Reporter: | Sergio Gomes <sgomes> |
Component: | CSS | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED FIXED | ||
Severity: | Normal | CC: | hyatt, oliverjash, simon.fraser, singhthing, webkit-bug-importer |
Priority: | P2 | Keywords: | InRadar |
Version: | Safari Technology Preview | ||
Hardware: | Mac | ||
OS: | OS X 10.11 | ||
URL: | http://codepen.io/anon/pen/bZJaVO | ||
See Also: | https://bugs.webkit.org/show_bug.cgi?id=166493 |
Description
Sergio Gomes
2016-08-19 11:09:07 PDT
I think the specific problem here is Safari doesn't like nested calcs: https://bugs.webkit.org/show_bug.cgi?id=166493 @Oliver There are two separate issues that are outlined. The nested calc issue as you mentioned. But also the fact that declaring a computed value (using arthimatic operations) for a variable is valid even without wrapping it inside a calc. This is also working in FF and Chrome but not in Safari. As an update, this issue appears to be resolved in Safari Tech Preview Release 20! Fingers crossed it will make it into a stable release soon. Marking the issue as resolved for now, but I'll keep an eye out to make sure there aren't any regressions in new TP releases. (In reply to comment #4) > As an update, this issue appears to be resolved in Safari Tech Preview > Release 20! Fingers crossed it will make it into a stable release soon. > > Marking the issue as resolved for now, but I'll keep an eye out to make sure > there aren't any regressions in new TP releases. Does this also mean this bug is fixed? https://bugs.webkit.org/show_bug.cgi?id=166493 (In reply to comment #5) > (In reply to comment #4) > > As an update, this issue appears to be resolved in Safari Tech Preview > > Release 20! Fingers crossed it will make it into a stable release soon. > > > > Marking the issue as resolved for now, but I'll keep an eye out to make sure > > there aren't any regressions in new TP releases. > > Does this also mean this bug is fixed? > https://bugs.webkit.org/show_bug.cgi?id=166493 Yes, it appears to be. I'll add a note to it. |