Bug 43243

Summary: Slowness and bad redraws with CSS background-size property
Product: WebKit Reporter: a.pultier
Component: CSSAssignee: Nobody <webkit-unassigned>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Normal CC: antoine.pultier, bfulgham, mikelawther, mitz, psolanki, simon.fraser, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
URL: http://bordel.unevu.com/exemple.html
Attachments:
Description Flags
Chromium Nightly build
none
Midori (old version)
none
Simper testcase
none
Just one file this time none

a.pultier
Reported 2010-07-30 05:47:05 PDT
Created attachment 63053 [details] Chromium Nightly build When background-size property is used, the background image moves, and the rendering is slow. Especially with move or dragdrop operation. I created a sample page, and I put in attachments screenshots of chromium with a recent webkit and midori with a old webkit. This bug has been verified with Chromium stable, Chromium nightly build, Safari stable, Safari nightly build, and Qt Webkit. According to tests, it would appear between version WebKit/531.2 (Midori) and AppleWebKit/532.4 version (Safari).
Attachments
Chromium Nightly build (164.46 KB, image/png)
2010-07-30 05:47 PDT, a.pultier 		no flags
Details
Midori (old version) (33.87 KB, image/png)
2010-07-30 05:47 PDT, a.pultier 		no flags
Details
Simper testcase (2.43 KB, application/octet-stream)
2010-08-02 10:13 PDT, Simon Fraser (smfr) 		no flags
Details
Just one file this time (13.83 KB, text/html)
2010-08-02 10:20 PDT, Simon Fraser (smfr) 		no flags
Details
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
a.pultier
Comment 1 2010-07-30 05:47:44 PDT
Created attachment 63054 [details] Midori (old version)
a.pultier
Comment 2 2010-07-30 05:53:26 PDT
(In reply to comment #0) > Created an attachment (id=63053) [details] > Chromium Nightly build > > When background-size property is used, the background image moves, and the rendering is slow. Especially with move or dragdrop operation. > > I created a sample page, and I put in attachments screenshots of chromium with a recent webkit and midori with a old webkit. > > This bug has been verified with Chromium stable, Chromium nightly build, Safari stable, Safari nightly build, and Qt Webkit. > > According to tests, it would appear between version WebKit/531.2 (Midori) and AppleWebKit/532.4 version (Safari). According to tests, it seems that the bug was *introduced* between version WebKit/531.2 (Midori) and AppleWebKit/532.4 version (Safari).
Simon Fraser (smfr)
Comment 3 2010-08-02 08:52:52 PDT
What does the "defaults" mean in the title?
mitz
Comment 4 2010-08-02 08:58:12 PDT
This looks like bug 26747, which <http://trac.webkit.org/changeset/46002> was supposed to fix.
Simon Fraser (smfr)
Comment 5 2010-08-02 10:13:38 PDT
Created attachment 63228 [details] Simper testcase
Simon Fraser (smfr)
Comment 6 2010-08-02 10:20:29 PDT
Created attachment 63230 [details] Just one file this time
mitz
Comment 7 2010-08-02 10:23:38 PDT
Might this be the low-quality scaling heuristic kicking in and never bothering to clean up after itself?
mitz
Comment 8 2010-08-02 11:17:07 PDT
(In reply to comment #7) > Might this be the low-quality scaling heuristic kicking in and never bothering to clean up after itself? This doesn’t appear to be the case.
Simon Fraser (smfr)
Comment 9 2010-08-02 16:26:27 PDT
I think this might be a side-effect of CG's scaling algorithm.
Mike Lawther
Comment 10 2011-10-11 18:00:02 PDT
I just tried the example on Chrome 16.0.905.0 canary on Windows 7, and I can see the same artifacts. So It doesn't seem to be CG specific.
Brent Fulgham
Comment 11 2022-07-11 17:20:30 PDT
Safari, Chrome, and Firefox show the same rendering behavior for this test case. I do not believe any further compatibility issue remains.
Radar WebKit Bug Importer
Comment 12 2022-07-11 17:21:17 PDT
<rdar://problem/96852062>
Antoine Pultier
Comment 13 2022-07-16 13:23:09 PDT
I confirm the bug has been killed at some point during the last 12 years.
Note You need to log in before you can comment on or make changes to this bug.