Bug 177358

Summary: Speedometer: ensure all TodoMVC tests use the complete latest CSS
Product: WebKit Reporter: Mathias Bynens <mathias>
Component: JavaScriptCoreAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: addyo, buildbot, cdumez, commit-queue, mathias, rniwa, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on: 177359    
Bug Blocks: 172339    
Attachments:
Description Flags
Patch
none
Archive of layout-test-results from ews125 for ios-simulator-wk2 none

Description Mathias Bynens 2017-09-22 05:30:55 PDT
The following tests get the default unstyled checkboxes in Firefox:

- VanillaJS-TodoMVC
- Vanilla-ES2015-TodoMVC
- Vanilla-ES2015-Babel-Webpack-TodoMVC
- EmberJS-TodoMVC
- EmberJS-Debug-TodoMVC
- AngularJS-TodoMVC
- Angular2-TypeScript-TodoMVC
- VueJS-TodoMVC
- jQuery-TodoMVC
- Inferno-TodoMVC
- Elm-TodoMVC
- Flight-TodoMVC

This can be fixed by ensuring they use the latest available TodoMVC CSS.
Comment 1 Mathias Bynens 2017-09-22 12:56:46 PDT
Created attachment 321583 [details]
Patch
Comment 2 Addy Osmani 2017-09-22 15:34:37 PDT
Ensuring all implementations use the exact same set of styles cross-browser sgtm. Thanks for catching this, Mathias.
Comment 3 Ryosuke Niwa 2017-09-22 16:10:34 PDT
Any comparison of perf across browsers before/after this content change?
Comment 4 Build Bot 2017-09-22 16:43:08 PDT
Comment on attachment 321583 [details]
Patch

Attachment 321583 [details] did not pass ios-sim-ews (ios-simulator-wk2):
Output: http://webkit-queues.webkit.org/results/4632004

New failing tests:
imported/w3c/web-platform-tests/payment-request/payment-request-show-method.https.html
Comment 5 Build Bot 2017-09-22 16:43:10 PDT
Created attachment 321602 [details]
Archive of layout-test-results from ews125 for ios-simulator-wk2

The attached test failures were seen while running run-webkit-tests on the ios-sim-ews.
Bot: ews125  Port: ios-simulator-wk2  Platform: Mac OS X 10.12.6
Comment 6 Mathias Bynens 2017-09-23 09:42:08 PDT
(In reply to Ryosuke Niwa from comment #3)
> Any comparison of perf across browsers before/after this content change?

Unfortunately, I haven’t been able to compare the results yet.

Can I assume the failing build is a fluke?
Comment 7 Ryosuke Niwa 2017-09-23 20:49:40 PDT
Yeah, I don't think this can cause a test failure on iOS.
Comment 8 Mathias Bynens 2017-09-24 23:57:58 PDT
Before/after results of the entire Speedometer benchmark:

Chrome Canary v63.0.3222.0:
    63.55 ± 0.62 (0.98%)  →  64.24 ± 0.39 (0.61%)
Safari Technology Preview Release 37 (v11.1, WebKit 12605.1.4.0.1):
    73.23 ± 0.62 (0.85%)  →  73.26 ± 0.66 (0.90%)
Firefox Nightly v58.0a1 (2017-09-24) (64-bit):
    48.60 ± 0.94 (1.90%)  →  48.1 ± 0.62 (1.3%)

Turns out the rendering difference didn’t cause much of a difference. Still, it’d be good to fix it.
Comment 9 Mathias Bynens 2017-09-24 23:58:57 PDT
(In reply to Mathias Bynens from comment #8)
> Safari Technology Preview Release 37 (v11.1, WebKit 12605.1.4.0.1):

That should’ve said Safari Technology Preview Release *39*. The detailed version numbers are correct.
Comment 10 WebKit Commit Bot 2017-09-26 16:48:19 PDT
Comment on attachment 321583 [details]
Patch

Clearing flags on attachment: 321583

Committed r222534: <http://trac.webkit.org/changeset/222534>
Comment 11 WebKit Commit Bot 2017-09-26 16:48:21 PDT
All reviewed patches have been landed.  Closing bug.
Comment 12 Radar WebKit Bug Importer 2017-09-27 12:18:27 PDT
<rdar://problem/34692999>