Closed Bug 1917602 Opened 1 year ago Closed 8 months ago

CSS zoom property is animatable contrary to what spec says

Categories

(Core :: CSS Transitions and Animations, defect, P3)

defect

Tracking

()

RESOLVED INVALID

People

(Reporter: vmakeev, Unassigned, Mentored)

References

()

Details

(Keywords: good-first-bug)

Attachments

(2 files)

Attached file zoom-animation.html

The CSS Viewport Module Level 1 spec lists the zoom property as not animatable. Though it can be animated in Firefox:

p {
    zoom: 2;
    animation: zoom 1s linear infinite alternate;
}

@keyframes zoom {
    from {
        zoom: 2;
    }
    to {
        zoom: 4;
    }
}

Chrome does discrete animation without transitions in between, while Safari doesn’t do anything at all. I’m not sure which behavior is correct (Chrome or Safari), but according to the spec, there should be no smooth animation.

Emilio, I believe you were involved in the implementation.

Flags: needinfo?(emilio)

Hmm, well, I guess.

I think we should at least do discrete animation. I don't think it matters much in practice.

This should be a matter of adding animation_type="discrete" to here, and adding a test.

Blocks: csszoom
Mentor: emilio
Severity: -- → S3
Flags: needinfo?(emilio)
Keywords: good-first-bug
Priority: -- → P3

Filed https://github.com/w3c/csswg-drafts/issues/10872 to clarify if the spec really intends this property to be non-animatable. Once that's resolved I might have a contributor I'm looking to onboard who can take this.

Assignee: nobody → tannal2409
Status: NEW → ASSIGNED
Attachment #9426398 - Flags: approval-mozilla-beta?
Attachment #9426398 - Flags: approval-mozilla-beta?
Pushed by ealvarez@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/f3cc65f111ef Make CSS zoom property discrete animatable. r=emilio
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/48339 for changes under testing/web-platform/tests
Pushed by emilio@crisal.io: https://hg.mozilla.org/integration/autoland/rev/d5d237db3e73 Fix test_transitions_per_property.html

Shouldn't we have gotten the spec fixed or at least agreed upon before landing this?

Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 132 Branch

(In reply to Brian Birtles (:birtles) from comment #8)

Shouldn't we have gotten the spec fixed or at least agreed upon before landing this?

Yeah sorry, I had missed your csswg issue. I added it to the agenda.

Status: RESOLVED → REOPENED
Flags: needinfo?(tannal2409)
Resolution: FIXED → ---
Target Milestone: 132 Branch → ---
Upstream PR was closed without merging

No need to do anything yet, let's wait for the spec issue.

Flags: needinfo?(tannal2409)

This good-first-bug hasn't had any activity for 2 months, it is automatically unassigned.
For more information, please visit BugBot documentation.

Assignee: tannal2409 → nobody
Status: REOPENED → NEW

There is an r+ patch which didn't land and no activity in this bug for 2 weeks.
:tannal2409, could you have a look please?
If you still have some work to do, you can add an action "Plan Changes" in Phabricator.
For more information, please visit BugBot documentation.

Flags: needinfo?(tannal2409)
Flags: needinfo?(emilio)

The spec got resolved to our current behavior.

Status: NEW → RESOLVED
Closed: 1 year ago8 months ago
Flags: needinfo?(tannal2409)
Flags: needinfo?(emilio)
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: