|
|
Created:
4 years, 2 months ago by malaykeshav Modified:
4 years, 2 months ago CC:
blink-reviews, blink-reviews-paint_chromium.org, chromium-reviews, dshwang, slimming-paint-reviews_chromium.org Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionUse scrollbar thickness to set layout
BUG=651940
COMPONENT=Paint, ScrollableArea, Scrollbar
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Committed: https://crrev.com/8d329a8b3ca5f11c064d1e109404613758dc3b45
Cr-Commit-Position: refs/heads/master@{#422706}
Patch Set 1 #Patch Set 2 : Updated Layout Test Expectations #
Messages
Total messages: 28 (15 generated)
Description was changed from ========== Use scrollbar thickness to set layout BUG=651940 COMPONENT=Paint, ScrollableArea, Scrollbar ========== to ========== Use scrollbar thickness to set layout BUG=651940 COMPONENT=Paint, ScrollableArea, Scrollbar CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 ==========
The CQ bit was checked by malaykeshav@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
malaykeshav@chromium.org changed reviewers: + oshima@chromium.org, wangxianzhu@chromium.org
PTAL
The change looks good. Can you add a test?
On 2016/10/03 at 17:03:49, wangxianzhu wrote: > The change looks good. Can you add a test? Doesn't the scrollbar width/thickness test during DPI change check for this already?
On 2016/10/03 at 17:22:47, malaykeshav wrote: > On 2016/10/03 at 17:03:49, wangxianzhu wrote: > > The change looks good. Can you add a test? > > Doesn't the scrollbar width/thickness test during DPI change check for this already? Does this CL change the behavior of the tests? If not, the tests seem not to test this CL.
On 2016/10/03 at 17:37:57, wangxianzhu wrote: > On 2016/10/03 at 17:22:47, malaykeshav wrote: > > On 2016/10/03 at 17:03:49, wangxianzhu wrote: > > > The change looks good. Can you add a test? > > > > Doesn't the scrollbar width/thickness test during DPI change check for this already? > > Does this CL change the behavior of the tests? If not, the tests seem not to test this CL. This CL changes the behavior of the test: https://storage.googleapis.com/chromium-layout-test-archives/linux_precise_bl...
On 2016/10/03 17:39:29, malaykeshav wrote: > On 2016/10/03 at 17:37:57, wangxianzhu wrote: > > On 2016/10/03 at 17:22:47, malaykeshav wrote: > > > On 2016/10/03 at 17:03:49, wangxianzhu wrote: > > > > The change looks good. Can you add a test? > > > > > > Doesn't the scrollbar width/thickness test during DPI change check for this > already? > > > > Does this CL change the behavior of the tests? If not, the tests seem not to > test this CL. > > This CL changes the behavior of the test: > https://storage.googleapis.com/chromium-layout-test-archives/linux_precise_bl... lgtm. Please remove the failure entry from TestExpectations and rebaseline it. (All green try bot results made me think the CL changed nothing.)
The CQ bit was checked by malaykeshav@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
On 2016/10/03 at 18:35:58, wangxianzhu wrote: > On 2016/10/03 17:39:29, malaykeshav wrote: > > On 2016/10/03 at 17:37:57, wangxianzhu wrote: > > > On 2016/10/03 at 17:22:47, malaykeshav wrote: > > > > On 2016/10/03 at 17:03:49, wangxianzhu wrote: > > > > > The change looks good. Can you add a test? > > > > > > > > Doesn't the scrollbar width/thickness test during DPI change check for this > > already? > > > > > > Does this CL change the behavior of the tests? If not, the tests seem not to > > test this CL. > > > > This CL changes the behavior of the test: > > https://storage.googleapis.com/chromium-layout-test-archives/linux_precise_bl... > > lgtm. > > Please remove the failure entry from TestExpectations and rebaseline it. (All green try bot results made me think the CL changed nothing.) Its already at [ NeedsRebaeline ]
The CQ bit was unchecked by wangxianzhu@chromium.org
On 2016/10/03 at 18:40:01, malaykeshav wrote: > On 2016/10/03 at 18:35:58, wangxianzhu wrote: > > On 2016/10/03 17:39:29, malaykeshav wrote: > > > On 2016/10/03 at 17:37:57, wangxianzhu wrote: > > > > On 2016/10/03 at 17:22:47, malaykeshav wrote: > > > > > On 2016/10/03 at 17:03:49, wangxianzhu wrote: > > > > > > The change looks good. Can you add a test? > > > > > > > > > > Doesn't the scrollbar width/thickness test during DPI change check for this > > > already? > > > > > > > > Does this CL change the behavior of the tests? If not, the tests seem not to > > > test this CL. > > > > > > This CL changes the behavior of the test: > > > https://storage.googleapis.com/chromium-layout-test-archives/linux_precise_bl... > > > > lgtm. > > > > Please remove the failure entry from TestExpectations and rebaseline it. (All green try bot results made me think the CL changed nothing.) > > Its already at [ NeedsRebaeline ] https://cs.chromium.org/chromium/src/third_party/WebKit/LayoutTests/TestExpec...
On 2016/10/03 18:40:01, malaykeshav wrote: > On 2016/10/03 at 18:35:58, wangxianzhu wrote: > > On 2016/10/03 17:39:29, malaykeshav wrote: > > > On 2016/10/03 at 17:37:57, wangxianzhu wrote: > > > > On 2016/10/03 at 17:22:47, malaykeshav wrote: > > > > > On 2016/10/03 at 17:03:49, wangxianzhu wrote: > > > > > > The change looks good. Can you add a test? > > > > > > > > > > Doesn't the scrollbar width/thickness test during DPI change check for > this > > > already? > > > > > > > > Does this CL change the behavior of the tests? If not, the tests seem not > to > > > test this CL. > > > > > > This CL changes the behavior of the test: > > > > https://storage.googleapis.com/chromium-layout-test-archives/linux_precise_bl... > > > > lgtm. > > > > Please remove the failure entry from TestExpectations and rebaseline it. (All > green try bot results made me think the CL changed nothing.) > > Its already at [ NeedsRebaeline ] Is it from the previous CL? This will confuse the rebaseline-bot. It examines in which CL the NeedsRebaseline was added, and will rebaseline the test to the status of that CL. You should wait for the auto-rebaseline finish for that CL and add NeedsRebaseline in this CL to let the rebaseline-bot rebaseline the test to the status of this CL.
The CQ bit was checked by malaykeshav@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
The CQ bit was checked by malaykeshav@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from wangxianzhu@chromium.org Link to the patchset: https://codereview.chromium.org/2382103006/#ps20001 (title: "Updated Layout Test Expectations")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Committed patchset #2 (id:20001)
Message was sent while issue was closed.
Description was changed from ========== Use scrollbar thickness to set layout BUG=651940 COMPONENT=Paint, ScrollableArea, Scrollbar CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 ========== to ========== Use scrollbar thickness to set layout BUG=651940 COMPONENT=Paint, ScrollableArea, Scrollbar CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Committed: https://crrev.com/8d329a8b3ca5f11c064d1e109404613758dc3b45 Cr-Commit-Position: refs/heads/master@{#422706} ==========
Message was sent while issue was closed.
Patchset 2 (id:??) landed as https://crrev.com/8d329a8b3ca5f11c064d1e109404613758dc3b45 Cr-Commit-Position: refs/heads/master@{#422706} |