Closed Bug 1362499 Opened 8 years ago Closed 12 days ago

Support unit-less values for CSS -webkit-perspective (for interop)

Categories

(Core :: CSS Parsing and Computation, enhancement, P3)

enhancement

Tracking

()

RESOLVED FIXED
147 Branch
Webcompat Priority P3
Tracking Status
firefox147 --- fixed

People

(Reporter: mstange, Assigned: sickl8)

References

Details

(Keywords: dev-doc-complete, good-first-bug, Whiteboard: [webcompat], [wptsync upstream])

Attachments

(2 files, 1 obsolete file)

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)
Attached file testcase 1
Priority: -- → P3
Mike, is this something that should be in the Compat spec?
Flags: needinfo?(miket)
(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).
Flags: needinfo?(miket)
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?
Flags: needinfo?(ericwilligers)
Chrome does have a use counter: unitless -webkit-perspective non-zero length https://www.chromestatus.com/metrics/feature/timeline/popularity/1671
Flags: needinfo?(ericwilligers)
(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?
Flags: needinfo?(kdubost)
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
Flags: needinfo?(kdubost)
Flags: webcompat?
Whiteboard: [webcompat]

Depending on how this goes, we might need to make sure this is documented properly.

Keywords: dev-doc-needed

Migrating Webcompat whiteboard priorities to project flags. See bug 1547409.

Webcompat Priority: --- → ?

See bug 1547409. Migrating whiteboard priority tags to program flags.

It seems like we found a real site relying on this, but they updated it and it's working now (https://webcompat.com/issues/21898).

Webcompat Priority: ? → revisit
Webcompat Priority: revisit → P3
Flags: webcompat?
Severity: normal → S3

hi there, I notice this bug while trying to find a good-first-issue and I'd like to work on it though, with reading through this bugzilla and the whatwg/compat issue, I'm not sure if Firefox would like to support unit-less values for -webkit-perspective. May I confirm it before trying to work on it? Thank you.

https://www.chromestatus.com/metrics/feature/timeline/popularity/1671
use counter is down to less than 0.6% from the 10% reported in 2017-2019, should we still fix this? if so how do we make -webkit- variant have custom behavior different from the standard perspective? Is there an example in the servo folder for a similar CSS property?

Flags: needinfo?(emilio)

We'd have to make -webkit-perspective a shorthand of perspective rather than a plain alias, and accept unitless units there. It's not hard but given we haven't seen compat bugs due to this in 5 years I think it's probably not worth it.

Flags: needinfo?(emilio)
Assignee: nobody → sickl8
Status: NEW → ASSIGNED
Attachment #9529330 - Attachment is obsolete: true
Pushed by ealvarez@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/b15cf7f3d998 https://hg.mozilla.org/integration/autoland/rev/02434507f7aa Add compat support for unitless perspective for webkit transform and perspective properties. r=emilio,firefox-style-system-reviewers
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/56336 for changes under testing/web-platform/tests
Whiteboard: [webcompat] → [webcompat], [wptsync upstream]
Status: ASSIGNED → RESOLVED
Closed: 12 days ago
Resolution: --- → FIXED
Target Milestone: --- → 147 Branch
Upstream PR merged by moz-wptsync-bot

I've added a Firefox 147 rel note to cover this change on MDN, in https://github.com/mdn/content/pull/42275. I don't think the actual perspective documentation needs any changes.

QA Whiteboard: [qa-triage-done-c148/b147]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: