Bug 118837 - [Qt][WK2] transforms/3d/point-mapping/3d-point-mapping pixel tests failing
Summary: [Qt][WK2] transforms/3d/point-mapping/3d-point-mapping pixel tests failing
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: Qt
Depends on:
Blocks: 79666
  Show dependency treegraph
 
Reported: 2013-07-18 01:46 PDT by Zoltan Arvai
Modified: 2014-02-01 19:01 PST (History)
5 users (show)

See Also:


Attachments
point-mapping results (486.50 KB, application/x-gzip)
2013-07-18 01:46 PDT, Zoltan Arvai
no flags Details
3d-point-mapping-deep-actual.png (53.36 KB, image/png)
2013-07-18 01:47 PDT, Zoltan Arvai
no flags Details
3d-point-mapping-deep-expected.png (28.30 KB, image/png)
2013-07-18 01:47 PDT, Zoltan Arvai
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Zoltan Arvai 2013-07-18 01:46:17 PDT
Created attachment 206966 [details]
point-mapping results

It seems some detail / contour missing  from the actual results after changing "non-composited contents" in CoordinatedLayerTreeHost.

transforms/3d/point-mapping/3d-point-mapping-2.html
transforms/3d/point-mapping/3d-point-mapping-3.html
transforms/3d/point-mapping/3d-point-mapping-coplanar.html
transforms/3d/point-mapping/3d-point-mapping-deep.html
transforms/3d/point-mapping/3d-point-mapping-overlapping.html
transforms/3d/point-mapping/3d-point-mapping-preserve-3d.html
transforms/3d/point-mapping/3d-point-mapping.html

Test results are attached to this bug.

Also I add other guys to cc for this bug whose worked on 3d-point-mapping in the past in bug 80315 and 104308.
Comment 1 Zoltan Arvai 2013-07-18 01:47:24 PDT
Created attachment 206967 [details]
3d-point-mapping-deep-actual.png
Comment 2 Zoltan Arvai 2013-07-18 01:47:58 PDT
Created attachment 206969 [details]
3d-point-mapping-deep-expected.png
Comment 3 Zoltan Arvai 2013-07-18 06:51:26 PDT
Sorry, I was wrong about r149292, the problem just turned out after that patch. After running more tests, it seems the failure already existed before the changes.