Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Code-Review | +1 |
Wow awesome work updating so many of the tests to modern syntax! Code looks great. Just one small thing on the test.
Bug: 442293382
nit: you can do `Fixed: 442293382` here and it'll close the bug when this lands.
// Return true if the node cannot be found.
Maybe it's safer to fail the test if the node/pseudo can't be found? I know the new tests all do `assert_false(isDisabled())` but someone could add one that checks `assert_true`. Better to just fail directly with an `assert()` here.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
nit: you can do `Fixed: 442293382` here and it'll close the bug when this lands.
Done
Maybe it's safer to fail the test if the node/pseudo can't be found? I know the new tests all do `assert_false(isDisabled())` but someone could add one that checks `assert_true`. Better to just fail directly with an `assert()` here.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
7 is the latest approved patch-set.
The change was submitted with unreviewed changes in the following files:
```
The name of the file: third_party/blink/web_tests/fast/forms/resources/common.js
Insertions: 2, Deletions: 2.
@@ -262,8 +262,8 @@
function isDisabledField(input, pseudo) {
const node = internals.shadowRoot(input).querySelector(`*[pseudo="${pseudo}"]`);
- // Return true if the node cannot be found.
- return !node || node.hasAttribute('disabled');
+ assert_true(!!node);
+ return node.hasAttribute('disabled');
}
function isYearFieldDisabled(input) {
```
Skip field disabled checks in DateTimeEditElement
`ShouldXXFieldDisabled` is over ten years old and disables fields such
as year, month, and day when min/max values fall within the same unit.
This CL introduces a runtime flag to optionally skip these legacy
checks, allowing the fields to remain enabled and aligning behavior with
Firefox’s placeholders.
Related tests have been updated, as they previously assumed the fields
would be disabled.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
LUCI Bisection has identified this change as the cause of a test failure. See the analysis: https://ci.chromium.org/ui/p/chromium/bisection/test-analysis/b/5688295234207744
Sample build with failed test: https://ci.chromium.org/b/8700667084906263265
Affected test(s):
[ninja://content/test:content_browsertests/DumpAccessibilityTreeTest.AccessibilityInputTimeWithPopupOpen/All.fuchsia](https://ci.chromium.org/ui/test/chromium/ninja:%2F%2Fcontent%2Ftest:content_browsertests%2FDumpAccessibilityTreeTest.AccessibilityInputTimeWithPopupOpen%2FAll.fuchsia?q=VHash%3A8fc6a521f60e522f)
A revert for this change was not created because the builder that this CL broke is not watched by gardeners, therefore less important. You can consider revert this CL, fix forward or let builder owners resolve it themselves.
If this is a false positive, please report it at http://b.corp.google.com/createIssue?component=1199205&description=Analysis%3A+https%3A%2F%2Fci.chromium.org%2Fui%2Fp%2Fchromium%2Fbisection%2Ftest-analysis%2Fb%2F5688295234207744&format=PLAIN&priority=P3&title=Wrongly+blamed+https%3A%2F%2Fchromium-review.googlesource.com%2Fc%2Fchromium%2Fsrc%2F%2B%2F7037611&type=BUG
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |