Repository navigation
InputDecorator.hintStyle should use tokens when using material3 - #120910
Renzo-Olivares wants to merge 10 commits into
Conversation
|
It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat (don't just cc him here, he won't see it! He's on Discord!). If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix? Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. |
|
The changes to |
|
Should be good to go now. |
There was a problem hiding this comment.
nit: might be better to add a space after "color:"
There was a problem hiding this comment.
good catch! thanks
There was a problem hiding this comment.
Just wonder if we also need to check the hint style for the outlined text field? Because I saw both types are using same hint style.
There was a problem hiding this comment.
Looking at the other hint tests in this file, looks like none of them set the filled property so should be the default (false). I think if they use the same hintStyle we should be alright since this is just checking that.
|
@Renzo-Olivares is this still on your radar? |
|
@Hixie This is on my radar, i'll check on google testing. |
|
Around 13 unexpected scubas I still have left to investigate. |
This adds
placeholdertokens to theinput_decorator_templatesohintStylematches m3 spec.Pre-launch Checklist
///).