LG-5187:Implement Improvements to focus and increase pixel size#5486
LG-5187:Implement Improvements to focus and increase pixel size#5486
Conversation
There was a problem hiding this comment.
I added this class because .usa-success-message is used in different places. So until it is decided that the checkmark will be used in all success messages, I added another class.
There was a problem hiding this comment.
I added this class because
.usa-success-messageis used in different places. So until it is decided that the checkmark will be used in all success messages, I added another class.
I think we only use it within the document capture step, to my knowledge. Should be safe to update the base styles directly.
(I'm also considering this from a design system perspective, since I assume we might want to pull these styles into the design system as well)
There was a problem hiding this comment.
I just realized that this is in a ticket to come.
5bc4e19 to
8089892
Compare
| } | ||
| } | ||
|
|
||
| input:not([disabled]):focus { |
80b091e to
d3ea4ba
Compare
This is something that is also happening in production. We can investigate this further at another time. |
There was a problem hiding this comment.
Out of curiosity, do we need both of these sets of styles? I see the one added below would apply for an input with a value, but it also seems to apply for one without a value. Could we remove this set of styles altogether then?
There was a problem hiding this comment.
Yes, this can be removed. I think this was from when I was hammering away at the focus.
There was a problem hiding this comment.
6bf1d57 to
1d003da
Compare
…sful; add checkmark
Co-authored-by: Andrew Duthie <andrew.duthie@gsa.gov>
1d003da to
0e6b9a5
Compare



This ticket increases the pixel size of the focus outline and the outline offset
Why: To enhance the user experience for users