note to self:
check the wpt.fyi results to see if firefox passes the test. if not, then relax the test and maybe make an internal test which asserts the webkit-like special behavior i added.
also add subtests for type=datetime-local and type=time
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | Gerrit |
Exportable changes to web-platform-tests were detected in this CL and a pull request in the upstream repo has been made: https://github.com/web-platform-tests/wpt/pull/45792.
When this CL lands, the bot will automatically merge the PR on GitHub if the required GitHub checks pass; otherwise, ecosystem-infra@ team will triage the failures and may contact you.
WPT Export docs:
https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md#Automatic-export-process
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | Gerrit |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | Gerrit |
note to self:
check the wpt.fyi results to see if firefox passes the test. if not, then relax the test and maybe make an internal test which asserts the webkit-like special behavior i added.
also add subtests for type=datetime-local and type=time
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | Gerrit |
SetUserHasEditedTheFieldAndBlurred();
I am slightly nervous that this function is called SetFocused() yet we are setting the blurred first. Should the order be:
```
TextControlElement::SetFocused(is_focused, focus_type);
if (!input_type_view_->IsMultipleFieldsTemporal() &&
UserHasEditedTheField()) {
SetUserHasEditedTheFieldAndBlurred();
}
```
await test_driver.send_keys(date, `1${tabKey}1${tabKey}1234${tabKey}${tabKey}`);
This is cool. Should we add an assert that the document.activeElement isn't the date anymore?
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | Gerrit |
SetUserHasEditedTheFieldAndBlurred();
I am slightly nervous that this function is called SetFocused() yet we are setting the blurred first. Should the order be:
```
TextControlElement::SetFocused(is_focused, focus_type);
if (!input_type_view_->IsMultipleFieldsTemporal() &&
UserHasEditedTheField()) {
SetUserHasEditedTheFieldAndBlurred();
}
```
Yeah we probably shouldn't call SetUserHasEditedTheFieldAndBlurred when the input gains focus, so I added a check to only run it if !is_focused, which means that the input is actually being blurred. I also moved the super call up front like you asked.
await test_driver.send_keys(date, `1${tabKey}1${tabKey}1234${tabKey}${tabKey}`);
This is cool. Should we add an assert that the document.activeElement isn't the date anymore?
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | Gerrit |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | Gerrit |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | Gerrit |
Support :user-valid/:user-invalid on multifield inputs
This patch makes :user-valid and :user-invalid start working on inputs
with type date, datetime-local, and time.
I matched the webkit behavior for when to start matching in response to
keyboard input, and added a separate tentative test for that behavior.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | Gerrit |
The WPT PR for this CL has been merged upstream! https://github.com/web-platform-tests/wpt/pull/45792
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | Gerrit |