https://treeherder.mozilla.org/logviewer.html#?job_id=140637234&repo=try&lineNumber=3600 1133905-* runs on Android only (it needs <meta viewport> and APZ). 1133905-4-v-rtl.html and 1133905-4-v-rtl.html are always failure because viewport is incorrect?. I don't know root cause yet.
This might be same failure for /layers/apz/test/reftest/async-scrollbar-1-v-rtl.html and /gfx/layers/apz/test/reftest/async-scrollbar-1-vh-rtl.html.
I think this test passes with enabling layout.css.servo.chrome.enabled, no?
(In reply to Hiroyuki Ikezoe (:hiro) from comment #2) > I think this test passes with enabling layout.css.servo.chrome.enabled, no? It seems not.
I have no idea what's going on there but take a look.
Assignee: nobody → hikezoe
Status: NEW → ASSIGNED
I'd say Stylo does render scrollbar correctly, whereas Gecko doesn't.
(In reply to Makoto Kato [:m_kato] from comment #1) > This might be same failure for > /layers/apz/test/reftest/async-scrollbar-1-v-rtl.html and > /gfx/layers/apz/test/reftest/async-scrollbar-1-vh-rtl.html. To me it looks they are the same reason, gecko does not render scrollbar correctly.
Unassigning since this is due to gecko's bug, I don't think it's worth fixing it.
Assignee: hikezoe → nobody
Status: ASSIGNED → NEW
status-firefox57=wontfix unless someone thinks this bug should block 57
It sounds like we can resolve this bug as FIXED when we enable Stylo on Android.
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.