Cannot reproduce the issue on my machine (MacOS 10.12.6, Chrome Version 65.0.3325.162). Even if I could, a user would be hard pressed to notice the issue nor would it be any serious degradation of the user experience.
Franz
added a comment - Cannot reproduce the issue on my machine (MacOS 10.12.6, Chrome Version 65.0.3325.162). Even if I could, a user would be hard pressed to notice the issue nor would it be any serious degradation of the user experience.
I don't think we should use an input element just to get the styling right. A span element would be semantically more correct. Using an input element also messes up the tab order: Pressing tab in the first date input previously correctly selected the second date input. Now it focusses the to label.
Sebastian Stamm
added a comment - I don't think we should use an input element just to get the styling right. A span element would be semantically more correct. Using an input element also messes up the tab order: Pressing tab in the first date input previously correctly selected the second date input. Now it focusses the to label.
Cannot reproduce the issue on my machine (MacOS 10.12.6, Chrome Version 65.0.3325.162). Even if I could, a user would be hard pressed to notice the issue nor would it be any serious degradation of the user experience.