-
Notifications
You must be signed in to change notification settings - Fork 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
Reader sidebar - allow default selections for expanding submenu stream groups. #99477
base: trunk
Are you sure you want to change the base?
Reader sidebar - allow default selections for expanding submenu stream groups. #99477
Conversation
Jetpack Cloud live (direct link)
Automattic for Agencies live (direct link)
|
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser: Sections (~70 bytes added 📈 [gzipped])
Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to. Async-loaded Components (~260 bytes added 📈 [gzipped])
React components that are loaded lazily, when a certain part of UI is displayed for the first time. Legend What is parsed and gzip size?Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory. Generated by performance advisor bot at iscalypsofastyet.com. |
This PR modifies the release build for the following Calypso Apps: For info about this notification, see here: PCYsg-OT6-p2
To test WordPress.com changes, run |
…default-selections
I guess thats a matter of opinion. The edge cases will be there regardless, I think we need to determine the best approach and most acceptable trade offs in general for it.
The downside here is we then have a button that stops doing anything under certain conditions. If im understanding that case, click "Recent" would:
Is that button being inert at times a UX concern? (Im honestly not sure, maybe its fine). Do we see that as better than the current state where clicking "Recent" would:
|
Yeah... You're right. I'm tempted to say let's just close this out. |
It seems like having the key functionality be reachable in one click would be more important than the edge cases you mentioned. I will see if I can test it. |
Thanks for the testing help. My thoughts:
|
…nality - prototype
This latest change feels nice @Addison-Stavlo. One thing I noticed was the selected state is different between Recent and the other dropdowns in the left nav. Recent uses bold and the others don't. Thought on making it bold consistently for all of them? |
Im confused how you tested them because I think the calypso build is still building. 😅 |
The calypso live branch is still being generated, but I did push a commit to prototype the proposed functionality. I still might need to refactor a little, and need to hide the cursor pointer style on the "red" area when it is inert. But curious for thoughts on the behavior now, this should currently behave as:
|
The live branch should be up now. Im wondering if clicking "Recent" when the menu is already expanded and has one of its items currently selected should either: B might be a little more consistent maybe? |
Yeah, i didn't have the latest... :-)
Sorry, I think we're talking about two different things. I'm talking about the sub menu active links: vs. It feels weird that they're styled differently. I like the bold one better. The blue link doesn't look selected to me.
This seems to work. To Rob's point, it remedies the double click issue.
Yeah, I like B. |
Related to # #97993
Proposed Changes
!!?? - in testing/review - Consider if the changes and conditions for applying selection and toggling the menu open or closed make sense. Are there any behavioral cases we can adjust that would make this better?
Adds the ability for our expandable menu items to direct to a defaultSelection when being opened and not being marked as already selected. This should not have any behavioral changes for implementations not using the new props.
defaultSelection
andisSelected
props to the expandable menu component.defaultSelection
exists, the menu is not already open, a child of the menu is not already selected (handled by theisSelected
prop).onClick
functionality (toggling the expandable menu without any selection functionality).defaultSelection
andisSelected
support from the various expandable areas in the reader - Recent, lists, tags, organizations.BEFORE
![reader-selection-before](https://private-user-images.githubusercontent.com/28742426/411694217-ffad61c5-cbb6-407e-b97f-35fa490bd43f.gif?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkzMzMzMjksIm5iZiI6MTczOTMzMzAyOSwicGF0aCI6Ii8yODc0MjQyNi80MTE2OTQyMTctZmZhZDYxYzUtY2JiNi00MDdlLWI5N2YtMzVmYTQ5MGJkNDNmLmdpZj9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEyVDA0MDM0OVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWM1ODk5YTFhMGM2MzRmODM2ZDRjYmU2OTYzNGI0NDcxZjc1NjJjMGUzMzJiMTY4ZmI3YjM2OTUwNWE2ZTQyYWEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.Rc1Wg7vDlfb62GAXeCyXqDQkSwu2ITspYXhbbjcSuFA)
AFTER
![reader-selection-after](https://private-user-images.githubusercontent.com/28742426/411694248-c71d6bdc-aeee-4e44-989a-c6acadee363e.gif?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkzMzMzMjksIm5iZiI6MTczOTMzMzAyOSwicGF0aCI6Ii8yODc0MjQyNi80MTE2OTQyNDgtYzcxZDZiZGMtYWVlZS00ZTQ0LTk4OWEtYzZhY2FkZWUzNjNlLmdpZj9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEyVDA0MDM0OVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWY1ZjE4ZjBiZDcxN2M5ZTFiYTRhMDlkNDdhZmNjZDdmNzVkNmFmOTMzYWFmZjk2MzIzYjM2MWZhN2VkYmI0YjcmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.uZgJPSltex0Fv_NYHI4L4NKqUG-vxeljtrilNoPFNuI)
Why are these changes being made?
Testing Instructions
Go to the reader:
Go to the site sidebar:
Pre-merge Checklist