Opened 5 months ago
Closed 3 months ago
#62001 closed enhancement (wontfix)
Inconsistent Text Selection Color Contrast on date, time, month, week & datetime-local
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | |
Component: | Customize | Keywords: | has-screenshots reporter-feedback |
Focuses: | ui, accessibility, css, administration | Cc: |
Description (last modified by )
https://imgur.com/xScZJj7
https://imgur.com/06CC8h0
input::-webkit-datetime-edit-hour-field:focus, input::-webkit-datetime-edit-minute-field:focus, input::-webkit-datetime-edit-second-field:focus, input::-webkit-datetime-edit-ampm-field:focus, input::-webkit-datetime-edit-day-field:focus, input::-webkit-datetime-edit-week-field:focus, input::-webkit-datetime-edit-month-field:focus, input::-webkit-datetime-edit-year-field:focus { color: #fff; border-color: #0073aa; background-color: #0073aa; } input::-moz-datetime-edit-hour-field:focus, input::-moz-datetime-edit-minute-field:focus, input::-moz-datetime-edit-second-field:focus, input::-moz-datetime-edit-ampm-field:focus, input::-moz-datetime-edit-day-field:focus, input::-moz-datetime-edit-week-field:focus, input::-moz-datetime-edit-month-field:focus, input::-moz-datetime-edit-year-field:focus { color: #fff; border-color: #0073aa; background-color: #0073aa; }
Attachments (2)
Change History (15)
#1
@
5 months ago
- Component changed from General to Customize
- Description modified (diff)
- Focuses multisite removed
- Keywords needs-patch needs-design-feedback has-testing-info changes-requested has-dev-note removed
#3
in reply to:
↑ 2
@
5 months ago
Replying to hellofromTonya:
I'm doing triage for 6.6.x cycle. For the
Version
, I'm not finding CSS changes in the 6.6.1 release that introduced this issue. Thus, removing it as theVersion
.
Also removing
dev-feedback
and2nd-opinion
keywords, as it's too early in the ticket's discussion for these.
I believe it a browser bug not a wp bug, but still im reporting here as i have no control over the browser source code & i have only tested in chrome atm.
This ticket was mentioned in Slack in #accessibility by rcreators. View the logs.
5 months ago
This ticket was mentioned in Slack in #accessibility by joedolson. View the logs.
4 months ago
#6
follow-up:
↓ 7
@
4 months ago
@pressthemes1 Are both of those two screenshots from Chrome? What is the difference between those screenshots, exactly? I can see that the focus coloring is different, but I can't tell anything about the context.
#7
in reply to:
↑ 6
@
4 months ago
Replying to joedolson:
@pressthemes1 Are both of those two screenshots from Chrome? What is the difference between those screenshots, exactly? I can see that the focus coloring is different, but I can't tell anything about the context.
The text color
#8
follow-up:
↓ 10
@
3 months ago
@pressthemes1 Yes, the different text color is something I can see; but I don't know how they were produced. Are they in different browsers? What is the scenario that causes you to see these two different states? You've provided no information that I can use to reproduce the issue. And yes, I can just pull up every browser and every OS and start comparing every case, but if you can tell me which environments those screenshots are from, it would be helpful.
#10
in reply to:
↑ 8
@
3 months ago
Replying to joedolson:
@pressthemes1 Yes, the different text color is something I can see; but I don't know how they were produced. Are they in different browsers? What is the scenario that causes you to see these two different states? You've provided no information that I can use to reproduce the issue. And yes, I can just pull up every browser and every OS and start comparing every case, but if you can tell me which environments those screenshots are from, it would be helpful.
NO
This ticket was mentioned in Slack in #accessibility by joedolson. View the logs.
3 months ago
This ticket was mentioned in Slack in #accessibility by joedolson. View the logs.
3 months ago
#13
@
3 months ago
- Milestone Awaiting Review deleted
- Resolution set to wontfix
- Status changed from new to closed
Given that we are unable to reproduce this and have reason to believe that it's a browser variation, I'm going to close this as wontfix. If you're able to provide any additional information that could isolate the issue, feel free to reopen.
I'm doing triage for 6.6.x cycle. For the
Version
, I'm not finding CSS changes in the 6.6.1 release that introduced this issue. Thus, removing it as theVersion
.Also removing
dev-feedback
and2nd-opinion
keywords, as it's too early in the ticket's discussion for these.