Implementing new UX for invoking rich text Link UI #57986
Merged
Conversation
|
Size Change: +2.5 kB (0%) Total Size: 1.7 MB
ℹ️ View Unchanged
|
jeryj
reviewed
Jan 18, 2024
Contributor
jeryj
left a comment
There was a problem hiding this comment.
I have some of the other work for this issue I can push up to this branch.
| contentRef, | ||
| } ) { | ||
| const [ addingLink, setAddingLink ] = useState( false ); | ||
| const [ clickedLink, setClickedLink ] = useState( false ); |
Contributor
There was a problem hiding this comment.
Instead of managing a clickedLink state, can we set the state of the thing we want to do? I.e. - display the link preview.
Contributor
Author
There was a problem hiding this comment.
I don't see how we could do that. The Popover is within the React tree. Therefore we must setState to trigger a re-render of the component with the new state.
Contributor
There was a problem hiding this comment.
Can we use setAddingLink( true ) instead of adding clickedLink state?
Contributor
Author
There was a problem hiding this comment.
Yeh try that. Might not need two states.
ellatrix
reviewed
Jan 19, 2024
|
|
||
| useLayoutEffect( () => { | ||
| // log tagNAME of anchorElement | ||
| if ( anchorElement?.tagName?.toLowerCase() === 'a' ) { |
Member
There was a problem hiding this comment.
Also if anchorElement is defined and isActive is true, it's guaranteed to be a link no?
Contributor
Author
There was a problem hiding this comment.
No because it can be a VirtualAnchorElement returned from useAnchor.
I've ended up avoiding the useAnchor entirely now by attaching listeners to the contenteditable.
Contributor
There was a problem hiding this comment.
No because it can be a VirtualAnchorElement returned from useAnchor.
How can I test VirtualAnchorElements? What blocks use them?
Contributor
Author
There was a problem hiding this comment.
You can't 😄 Take a look at useAnchor and you'll see it returns a "virtual" anchor representing a selection within RichText. So for example, when you highlight some text and you want to make a link, the Link UI needs to have an anchor point to "attach" the Popover to, but the link (<a> TAG) doesn't yet exist in the DOM. So useAnchor will return a coordinate which approximates the selection in the richtext.
Contributor
Author
There was a problem hiding this comment.
Nice work!
We'll need some new e2e test coverage for these changes. Specifically it would be super easy for regressions to be introduced around this new behaviour so we need to validate the new expectations.
Contributor
There was a problem hiding this comment.
I think fixing all the broken e2e tests will validate it too.
Contributor
Author
Thank you Ella. @jeryj Let's refine the PR UX / UI before this gets merged |
|
Flaky tests detected in 196d888. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/7646931654
|
Contributor
Author
|
✅ Update: I implemented this in a8a418a I think the next step should be that if you are within a link and...
...then
I think we can safely trap focus and constrain tabbing. We should then consider incorporating the a11y tweaks to labelling the dialog that I started in #54063. |
Member
|
I suppose the link control in the toolbar should open/close the LinkControl, just like when the other formats are applied (and not subsequently removed upon a second click): link.mp4 |
Contributor
I've been looking at this, and it is unfortunately quite tricky due to how/when states are set. Are you OK with that behavior in a follow-up? |
Member
Sure. |
b322bbd to
e6e0e98
Compare
Contributor
Author
|
Update: I can't replicate this once I rebased and then reverted 74a3e9e @jeryj I found a bug where we show the wrong UI:
Screen.Capture.on.2024-01-24.at.09-29-54.mp4It only seems to happen if you click exactly on the point where the cursor is placed. |
29ac34b to
2783e3c
Compare
2783e3c to
2526cda
Compare
Contributor
Author
|
Rebased to bring in changes made in #57726 |
jeryj
reviewed
Jan 24, 2024
| } ) { | ||
| const [ addingLink, setAddingLink ] = useState( false ); | ||
| // We only need to store the button element that opened the popover. We can ignore the other states, as they will be handled by the onFocus prop to return to the rich text field. | ||
| const [ openedBy, setOpenedBy ] = useState( null ); |
Contributor
There was a problem hiding this comment.
I didn't want to add this openedBy state, as the popover has its own system for returning focus. For some reason, it's not working correctly with the Rich text element and split between iframe editor and toolbar in the header.
Contributor
Author
Great work @jeryj 👏
@richtabor already confirmed he's happy with this in a followup. I don't think we should block this PR further on this unless there's a very important reason why it has to be in the initial release. |
scruffian
approved these changes
Jan 25, 2024
Contributor
scruffian
left a comment
There was a problem hiding this comment.
This is testing well for me.
The state being tested is no longer possible with the new ux.
Contributor
|
Tests are hopefully fixed to account for the new states of the Link Control being visible/hidden. 🤞🏻 Also added tests to cover focus outside click sending focus to the right area and returning focus from the keyboard to the button that opened it. |
westonruter
added a commit
that referenced
this pull request
Jan 26, 2024
…zy-hydration * origin/trunk: (47 commits) Interactivity API: Break up long hydration task in interactivity init (#58227) Add supports.interactivity to Query block (#58316) Font Library: Make notices more consistent (#58180) Fix Global styles text settings bleeding into placeholder component (#58303) Fix the position and size of the Options menu, (#57515) DataViews: Fix safari grid row height issue (#58302) Try a fix (#58282) Navigation Submenu Block: Make block name affect list view (#58296) Apply custom scroll style to fixed header block toolbar (#57444) Add support for transform and letter spacing controls in Global Styles > Typography > Elements (#58142) DataViews: Fix table view cell wrapper and BlockPreviews (#58062) Workflows: Add 'Technical Prototype' to the type-related labels list (#58163) Block Editor: Optimize the 'useBlockDisplayTitle' hook (#58250) Remove noahtallen from .wp-env codeowners (#58283) Global styles revisions: fix is-selected rules from affecting other areas of the editor (#58228) Try: Disable text selection for post content placeholder block. (#58169) Remove `template-only` mode from editor and edit-post packages (#57700) Refactored download/upload logic to support font faces with multiple src assets (#58216) Components: Expand theming support in COLORS (#58097) Implementing new UX for invoking rich text Link UI (#57986) ...
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What?
Changes UX for links within rich text to require explicit activation before displaying the Link UI interface.
Closes #57821
Why?
Currently on
trunkmoving the cursor within an existing link (format) will cause the Link UI to appear. This is providing a sub par a11y experience because:How?
disables the behaviour to immediately activate the Link UI is the link format is active
adds a click handler to the contenteditable element which will trigger the Link UI when it is clicked.
changes the block toolbar button to be "Edit link" if the link format is active. Clicking this will cause the Link UI to appear.
New Post
Create a paragraph block
Add some text
Create 3 or 4 links
Click on each link and see you can activate and edit the link using the Link UI.
Using keyboard attempt the same thing but notice that you must either click the toolbar button or press
CMD + Kto edit the linkTesting Instructions
Testing Instructions for Keyboard
Screenshots or screencast
Screen.Capture.on.2024-01-18.at.21-03-34.mp4