w3c / w3c/csswg-drafts

[css-transitions] Clarify behaviors in print documents

Open
#8,012 2 comments 0 reactions 1 assignee View on GitHub

@dbaron is already working on this.

Since Nov 16, 2022.

css-transitions-1
Dominant language
Bikeshed
Stars
4.9k
Forks
816
Avg merge
2d 18h
Merged PRs (30d)
24

Description

Firefox has a bug report that CSS transitions are triggered by @media print style changes. There are two questions;

  1. CSS transitions should be triggered by style changes caused by @media print queries?
  2. On-going CSS transitions should be printed as it is?

As of now Firefox does both. Chrome doesn't either. Safari does 2 but doesn't 1.

I believe the current Firefox behavior is ideal, but I am quire unsure what the desired behavior is, from the perspective of users, I guess Safari's behavior is reasonable?

We are going to change our behavior to match Chrome one in that bug.

CC @dbaron and @birtles

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.