Bug 108954 - Incorrect rendering when translating elements inside animating boxes
Summary: Incorrect rendering when translating elements inside animating boxes
Status: RESOLVED CONFIGURATION CHANGED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL: https://zewt.org/~glenn/test-webkit-t...
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2013-02-05 10:09 PST by Glenn Maynard
Modified: 2023-05-29 03:32 PDT (History)
7 users (show)

See Also:


Attachments
test (1.19 KB, text/html)
2013-02-05 10:09 PST, Glenn Maynard
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Glenn Maynard 2013-02-05 10:09:53 PST
Created attachment 186651 [details]
test

The blue .overlay should be rendered on top of the text.  When the -webkit-transition on #box is triggered, the text ends up on top.  The text first appears when the box reaches the top, stays on top if the transition is reversed, then pops back underneath when it reaches the bottom.

To run the test, call test() from the console.  This happens in Windows 7 (r131444) and on Safari in iOS 6.
Comment 2 Simon Fraser (smfr) 2018-08-28 11:00:49 PDT
Still reproduces.
Comment 3 Radar WebKit Bug Importer 2018-08-28 11:02:13 PDT
<rdar://problem/43804856>
Comment 4 Ahmad Saleem 2023-05-27 06:59:52 PDT
I am not able to reproduce this in Safari 16.5 and WebKit ToT anymore and by opening test case and typing ('test()') to trigger animation / transition, it does but there is no text bleed or issue of text being visible anymore and it matches Chrome Canary 115 as well.

Marking this as "RESOLVED CONFIGURATION CHANGED", please reopen, if it is reproducible.
Comment 5 Glenn Maynard 2023-05-29 03:32:46 PDT
This report has been ignored for over a decade.  Is this an off-season April Fool's joke?

All this has done is remind me that I once spent the time to report a bug, putting together a clean example to help developers fix it, and was silently ignored.  Reporting bugs well takes time, and ignoring good bug reports is a silent middle finger to the user who spent his time to help you improve your product.

But thanks for bringing it back up.  What were you thinking?