Closed
Bug 913588
Opened 8 years ago
Closed 7 years ago
CSS Transitions On Pseudo Elements Fails If Parent Has Overflow:Auto
Categories
(Core :: Layout, defect)
Tracking
()
VERIFIED
FIXED
mozilla31
People
(Reporter: brenton.klik, Assigned: mats)
References
Details
(Keywords: testcase)
Attachments
(1 file)
521 bytes,
text/html
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.66 Safari/537.36 Steps to reproduce: This effects all versions up to: 23.0.1 <!doctype html> <html> <head> <title>Transition Test</title> <style type="text/css"> div { overflow: auto; } div:before, div:after { color: #fff; -moz-transition: all 500ms ease; } div:before { content: '[ '; } div:after { content: ' ]'; } div:hover:before, div:hover:after { color: #000; } </style> </head> <body> <div>Element</div> <div>Element</div> <div>Element</div> </body> </html> Actual results: The browser fails to transition the font color. Expected results: If you comment out the "overflow: auto" line, the browser will transition the pseudo elements as expected.
Updated•8 years ago
|
Component: Untriaged → Layout
Product: Firefox → Core
![]() |
||
Updated•8 years ago
|
Flags: needinfo?(dbaron)
![]() |
||
Comment 1•8 years ago
|
||
FWIW, MSIE 11 behaves as Chrome 33.
Keywords: testcase
Version: unspecified → Trunk
![]() |
||
Comment 2•8 years ago
|
||
Assignee | ||
Comment 3•7 years ago
|
||
Should be fixed in Nightly in a few days, by bug 990340.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Assignee: nobody → matspal
Flags: needinfo?(dbaron)
Target Milestone: --- → mozilla31
Comment 4•7 years ago
|
||
Reproduced with Nightly 2014-02-27. Verified as fixed with Firefox 31 beta 4 (Build ID: 20140623175014) on Windows 7 x64 and Mac OS X 10.9.3: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0 Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Firefox/31.0
Status: RESOLVED → VERIFIED
Keywords: verifyme
You need to log in
before you can comment on or make changes to this bug.
Description
•