WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
94746
decide what (and how) we should set the tolerance for ref test pixel compares and test for that
https://bugs.webkit.org/show_bug.cgi?id=94746
Summary
decide what (and how) we should set the tolerance for ref test pixel compares...
Dirk Pranke
Reported
2012-08-22 13:47:39 PDT
See comments in
https://bugs.webkit.org/show_bug.cgi?id=94704
for background ... it's perhaps not clear if we should use the default tolerance the port specifies for pixel tests also for ref tests, or if ref tests should always require an exact match (tolerance == 0 or just hash compares), or if we should have a separate default-tolerance-for-ref-tests parameter. Once we agree on this, we should make sure this is implemented and write a test to check the behavior (we don't have a test today).
Attachments
Patch
(1.53 KB, patch)
2012-08-30 12:35 PDT
,
Dirk Pranke
no flags
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Ojan Vafai
Comment 1
2012-08-22 13:52:48 PDT
I don't see why we'd ever want a tolerance other than 0 for reftests. The point of tolerance is to handle things like different text anti-aliasing across OS releases. None of these sort of things apply to reftests.
Ryosuke Niwa
Comment 2
2012-08-22 14:00:58 PDT
Yeah, it seems like we shouldn't need any tolerance for ref tests.
Dirk Pranke
Comment 3
2012-08-22 14:15:46 PDT
I don't have any real argument against using 0. Simon, anyone else from Apple, any objections?
Simon Fraser (smfr)
Comment 4
2012-08-22 14:56:48 PDT
No objection, but I wouldn't be surprised if some ref tests are "close but not exact" and fail with a zero tolerance. We'll have to try it and see.
Ryosuke Niwa
Comment 5
2012-08-22 14:59:27 PDT
I guess 1px rounding differences are common (e.g. inline-block vs. inline) in text rendering.
Dirk Pranke
Comment 6
2012-08-22 15:00:48 PDT
it would seem a bit odd to me to have reftests that attempt to render the same string of text two different ways and hope that they would be the same, but maybe I'm not being creative enough. Do we have many of those?
Ryosuke Niwa
Comment 7
2012-08-22 15:03:32 PDT
(In reply to
comment #6
)
> it would seem a bit odd to me to have reftests that attempt to render the same string of text two different ways and hope that they would be the same, but maybe I'm not being creative enough. Do we have many of those?
I've hit that when I was converting a test for bdi because inline-block and inline have a different semantics in UBA.
Dirk Pranke
Comment 8
2012-08-30 12:35:04 PDT
Created
attachment 161534
[details]
Patch
Dirk Pranke
Comment 9
2012-08-30 12:35:32 PDT
Looks like there's general consensus that we should require exact matches. I'm adding an assertion to the test cases to enforce this.
WebKit Review Bot
Comment 10
2012-08-30 13:22:13 PDT
Comment on
attachment 161534
[details]
Patch Clearing flags on attachment: 161534 Committed
r127180
: <
http://trac.webkit.org/changeset/127180
>
WebKit Review Bot
Comment 11
2012-08-30 13:22:17 PDT
All reviewed patches have been landed. Closing bug.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug