Android: setting 'defaultValue' of input type=date from script does not cause UI update |
|||||
Issue descriptionChrome Version: 68.0.3416.0 (and earlier) OS: Android What steps will reproduce the problem? (1) Create an input type=date (2) From script, set the 'defaultValue' to a value (3) Observe the input element's rendered UI What is the expected result? The UI should update to show the default value (since there was no previous selection). This happens on desktop Chrome. What happens instead? The UI doesn't update; the date picker is blank. However if you select it, the date picker widget appears and shows that the default value is set. See test case http://output.jsbin.com/vocunov
,
May 3 2018
Tested the issue in Android and able to reproduce the issue. Similar behavior is observed since Chrome #60.0.3072.0 Steps Followed: 1. Launched the Chrome Browser. 2. Navigate to the URL: http://output.jsbin.com/vocunov 3. Observed that, default date (07/25/2015) is not displayed. From the date picker, tap on the default date and tap on 'Set', still date is not displayed. However, if the user selects any other date, selected date is displayed. Chrome versions tested: 60.0.3072.0, 66.0.3359.126(Stable), 68.0.3416.0(Canary) OS: Android 8.1.0 Android Devices: Pixel 2 XL This seems to be a Non-Regression issue as same behavior is seen since M-60. Untriaged for further input's on this issue. Please navigate to below link for log's and screen cast-- go/chrome-androidlogs/838898 Note: 1. This issue is not observed in Desktop. 2. Issue is not observed on FireFox mobile version.
,
May 14 2018
,
May 14 2018
,
May 15 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/a17bbb370bf5597c6d00f2ef6a8bea3ca6e16e38 commit a17bbb370bf5597c6d00f2ef6a8bea3ca6e16e38 Author: Kent Tamura <tkent@chromium.org> Date: Tue May 15 12:13:56 2018 Android: input[type=date]: Update view if the value is updated by defaultValue setter Thew new test is added to SmokeTests in order that Android build bots run it. Bug: 838898 Change-Id: I18f8320550a82fb5fddc0c98f0b8f0417f1e4d80 Reviewed-on: https://chromium-review.googlesource.com/1056947 Reviewed-by: Yoshifumi Inoue <yosin@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#558667} [modify] https://crrev.com/a17bbb370bf5597c6d00f2ef6a8bea3ca6e16e38/third_party/WebKit/LayoutTests/SmokeTests [add] https://crrev.com/a17bbb370bf5597c6d00f2ef6a8bea3ca6e16e38/third_party/WebKit/LayoutTests/fast/forms/date/date-chooseronly-defaultValue-expected.html [add] https://crrev.com/a17bbb370bf5597c6d00f2ef6a8bea3ca6e16e38/third_party/WebKit/LayoutTests/fast/forms/date/date-chooseronly-defaultValue.html [modify] https://crrev.com/a17bbb370bf5597c6d00f2ef6a8bea3ca6e16e38/third_party/blink/renderer/core/html/forms/chooser_only_temporal_input_type_view.cc [modify] https://crrev.com/a17bbb370bf5597c6d00f2ef6a8bea3ca6e16e38/third_party/blink/renderer/core/html/forms/chooser_only_temporal_input_type_view.h
,
May 16 2018
,
Jul 9
Issue 737387 has been merged into this issue.
,
Oct 5
> Note that this comes from a React bug that they found and worked around, sadly without informing us at the time :( smcgruer@: (I work on React.) We weren't contacted about this Chrome workaround for React: https://chromium-review.googlesource.com/c/chromium/src/+/844324. Let's call it even? In general we do try to file browser bugs when we notice them and hope you'll do the same for us. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by smcgruer@chromium.org
, May 2 2018