Open Bug 1362499 Opened 5 years ago Updated 2 years ago
Support unit-less values for CSS -webkit-perspective (for interop)
One of the first 3d transform demos, https://webkit.org/blog-files/3d-transforms/morphing-cubes.html , does not work correctly in Firefox because the #container element has -webkit-perspective: 800; with a unit-less number.
Reclassifying as CSS Parsing & Computation -- the fix here would be in the CSS Parser.
Component: Layout → CSS Parsing and Computation
Summary: Should we support unit-less -webkit-perspective? → Support unit-less values for CSS -webkit-perspective (for interop)
Mike, is this something that should be in the Compat spec?
(In reply to Cameron McCormack (:heycam) from comment #3) > Mike, is this something that should be in the Compat spec? Yeah, if need to implement it, it should be. I'll file a bug (if one doesn't already exist).
See Also: → https://github.com/whatwg/compat/issues/100
If we want to implement this, it can be a good first bug I think.
Err, disregard my previous comment. Still I think it's not worth unless we find a real website which is broken that isn't webkit.org. Eric, looks like Chromium still parses -webkit-perspective: <integer>. Does the Chrome team have any use counter for it by any chance?
Chrome does have a use counter: unitless -webkit-perspective non-zero length https://www.chromestatus.com/metrics/feature/timeline/popularity/1671
(In reply to Eric Willigers from comment #8) > Chrome does have a use counter: > unitless -webkit-perspective non-zero length > https://www.chromestatus.com/metrics/feature/timeline/popularity/1671 Ouch, that use counter is quite high. I guess it doesn't account for fallback, i.e., something like -webkit-perspective: 800; perspective: 800px; But still... :)
I'd prefer to at least get a single report of a broken page because of this before going ahead and implementing it, but I guess if it breaks websites we'd need to implement this quirk...
I agree. I filed this bug only based on the Webkit demo and I haven't seen breakage caused by it elsewhere.
Karl, have you seen any real-world bustage related to this?
The two places I thought about were: https://www.google.com/logos/2014/rubiks/iframe/ https://zacqary.github.io/rubix but no issue. so… 0 bustage to my knowledge and/or memory
Webcompat Priority: --- → ?
Webcompat Priority: ? → revisit
You need to log in before you can comment on or make changes to this bug.