|
|
DescriptionAlign position of unstyled list items' bullet point with IE firefox
BUG=590094
TEST=Load https://jsfiddle.net/2qgcuofg/2/
R=skobes@chromium.org,nainar@chromium.org
Patch Set 1 #Patch Set 2 : Align position of unstyled list items' bullet point with IE firefox #Messages
Total messages: 22 (13 generated)
Description was changed from ========== Align position of unstyled list items' bullet point with IE firefox BUG=590094 TEST=Load https://jsfiddle.net/2qgcuofg/2/ R=skobes@chromium.org,nainar@chromium.org ========== to ========== Align position of unstyled list items' bullet point with IE firefox BUG=590094 TEST=Load https://jsfiddle.net/2qgcuofg/2/ R=skobes@chromium.org,nainar@chromium.org ==========
Hi, please help to review. BTW, in the previous implementation, it comments "If we are not in a list, tell the layoutObject so it can position us inside. We don't want to change our style to say "inside" since that would affect nested nodes." Do you have any background for this?
On 2016/09/25 at 13:43:18, xing.xu wrote: > Hi, please help to review. > > BTW, in the previous implementation, it comments "If we are not in a list, tell the layoutObject so it can position us inside. We don't want to change our style to say "inside" since that would affect nested nodes." Do you have any background for this? Hi, Just checking have you run the LayoutTests on this change? Also I am scheduling it for CQ dry run. So I can get an idea of how this fares on the bots. Also any change in code base should also have a LayoutTest for it so please add one here. The change seems ok - will l*tm once the due diligence is done. I'm not well versed in DOM stuff but will look into this and get back to you.
The CQ bit was checked by nainar@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: Try jobs failed on following builders: linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
On 2016/09/25 at 16:55:22, nainar wrote: > On 2016/09/25 at 13:43:18, xing.xu wrote: > > Hi, please help to review. > > > > BTW, in the previous implementation, it comments "If we are not in a list, tell the layoutObject so it can position us inside. We don't want to change our style to say "inside" since that would affect nested nodes." Do you have any background for this? > > Hi, > > Just checking have you run the LayoutTests on this change? Also I am scheduling it for CQ dry run. So I can get an idea of how this fares on the bots. > > Also any change in code base should also have a LayoutTest for it so please add one here. > > The change seems ok - will l*tm once the due diligence is done. I'm not well versed in DOM stuff but will look into this and get back to you. Yup definitely looks like you need to look into the failing LayoutTests...
Thanks. Will look into these tests. BTW, it seems some regression cases are platform dependent, does it possible change these to RefTests as https://trac.webkit.org/wiki/Writing%20Reftests?
Yup feel free to changes those tests. You can even chnage them to use the testharness API in LayoutTests/resources.
The change lgtm but please do fix up the tests, OWNERS lgtm. You can't CQ until that anyway.
The CQ bit was checked by xing.xu@intel.com 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: Try jobs failed on following builders: ios-device on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device/builds...) ios-simulator on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator/bui...) mac_chromium_compile_dbg_ng on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_comp...)
The CQ bit was checked by xing.xu@intel.com 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: Try jobs failed on following builders: win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)
Hi, nainar@, is there any plan to refactor all these platform dependent tests to reftests or jstests?
Hi xing.xu, Unfortunately I don't think there are any short term plans to undergo that refactor. I would talk to dpranke@ or ojan@ in this regard.
OK, thanks. Summary all failed webkit_tests here: win_chromium_rel_ng unexpected_failures: fast/text/font-weight.html fast/text/textIteratorNilRenderer.html paint/invalidation/scrolled-iframe-scrollbar-change.html fast/text/font-stretch-variant.html paint/invalidation/do-not-paint-below-image-baseline.html fast/text/sub-pixel/text-scaling-pixel.html fast/text/international/bidi-listbox.html fast/text/international/bidi-listbox-atsui.html fast/text/international/lang-glyph-cache-separation.html fast/text/font-stretch.html fast/text/drawBidiText.html paint/invalidation/transform-rotate-and-remove.html fast/text/font-features/caps-native-synthesis.html linux_chromium_rel_ng unexpected_failures: paint/invalidation/transform-rotate-and-remove.html paint/invalidation/scrolled-iframe-scrollbar-change.html paint/invalidation/do-not-paint-below-image-baseline.html mac_chromium_rel_ng unexpected_failures: paint/invalidation/transform-rotate-and-remove.html paint/invalidation/scrolled-iframe-scrollbar-change.html paint/invalidation/do-not-paint-below-image-baseline.html |