Closed Bug 537143 Opened 14 years ago Closed 1 year ago

support CSS transitions on and inside 'display:none' elements

Categories

(Core :: CSS Parsing and Computation, defect)

defect

Tracking

()

RESOLVED WONTFIX

People

(Reporter: dbaron, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: dev-doc-needed)

We should support CSS transitions on and inside 'display:none' elements, which can have their computed style queried or can be unhidden in the future.

See the thread:
http://groups.google.com/group/mozilla.dev.tech.layout/browse_thread/thread/b9982ceccf864478/fdf61cb2fdc54cd5
("CSS transitions on and inside 'display:none'")
Blocks: 683696
I added some automated tests for this in bug 625289, marked as failing, in https://hg.mozilla.org/mozilla-central/rev/51037224ba03 .

Note that supporting transitions *on* display:none elements should be straightforward; it involves adding calls to RestyleManager::TryStartingTransition from ElementRestyler::RestyleUndisplayedChildren.

But supporting transitions *inside* display:none elements is substantially harder; it would involve figuring out how to decide when to compute style for entire display:none subtrees because they might have transitions in them.

I'm not sure that we should try to fix the first without also having a fix for the second.
Severity: normal → S3

The severity field for this bug is relatively low, S3. However, the bug has 4 duplicates.
:emilio, could you consider increasing the bug severity?

For more information, please visit auto_nag documentation.

Flags: needinfo?(emilio)

I don't think we want this. We don't want to have to do rendering work inside display: none subtrees.

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