-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HierarchicalTermSelector: Use TextControl component #33545
HierarchicalTermSelector: Use TextControl component #33545
Conversation
Size Change: -51 B (0%) Total Size: 1.07 MB
ℹ️ View Unchanged
|
It looks like I need to update selectors for e2e tests. |
0c91b36
to
9a9d96e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! 👍
P.S. The withInstanceId HOC is no longer needed for the HierarchicalTermSelector component but left it here for backward compatibility.
I guess this is about editor.PostTaxonomyType
filter, correct?
packages/editor/src/components/post-taxonomies/hierarchical-term-selector.js
Outdated
Show resolved
Hide resolved
That's correct. I will link this comment just for future reference - #33418 (comment). |
* Update selector in e2e tests
Description
HierarchicalTermSelector
wasn't using theTextControl
component for some of its inputs. As a result, the input fields design was slightly off from the rest of the screen. PR replaces input/labels elements withTextControl
component.Fixes #28577.
P.S. The
withInstanceId
HOC is no longer needed for theHierarchicalTermSelector
component but left it here for backward compatibility.How has this been tested?
Screenshots
Types of changes
Bugfix
Checklist:
*.native.js
files for terms that need renaming or removal).