Closed (fixed)
Project:
Gutenberg
Version:
3.0.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
18 Jan 2023 at 10:53 UTC
Updated:
20 Jul 2024 at 15:49 UTC
Jump to comment: Most recent
Usually we use the same branch used for WordPress releases. Goal is to update with wp/6.4 branch https://github.com/wordpress/gutenberg/tree/wp/6.4
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
marcofernandes commentedComment #3
marcofernandes commentedComment #7
marcofernandes commentedComment #8
marcofernandes commentedComment #10
marcofernandes commentedComment #11
marcofernandes commentedComment #12
marcofernandes commentedComment #13
marcofernandes commentedComment #14
marcofernandes commentedComment #15
marcofernandes commentedComment #16
marcofernandes commentedComment #17
marcofernandes commentedComment #19
marcofernandes commentedComment #20
marcofernandes commentedComment #25
marcofernandes commentedEnough done for a beta or RC release for initial tests.
Next step is to review all issues on 2.x that are ready to commit, review and fix critical issues (and some major) and merge into 3.0.x.
Comment #31
marcofernandes commentedComment #32
marcofernandes commentedComment #35
marcofernandes commentedComment #37
codebymikey commentedThe
94e5099c9commit currently affects integrations with long grouped fields within the More Settings such as Details and Select boxes, attempting to click one of them automatically scrolls the user back to the top of the Additional Fields section, which isn't expected behaviour.Also, is there a reason we opted to handle this in PHP via:
rather than a dynamic
toggleevent listener targetting the more settings class?I would opt to remove the event listener to reduce code complexity unless the existing behaviour expand/collapase behaviour is unmanageable under certain themes. If so, I believe the following should achieve the same work without breaking things:
Otherwise, I think we're better off leaving these admin-specific UI changes to the admin theme or individual site developers to implement as they deem fit to avoid complications.
Comment #39
codebymikey commentedI've pushed an update removing the onClick event listener from the element, we may attach the
toggleevent listener referenced above in a further commit if it's still useful/necessary.Comment #40
marcofernandes commentedI think we should maintain the scroll behavior because we observe many users miss that the more settings pane is open when clicking on it. Eventually they found out about it by scrolling but I believe that by scrolling improves the user experience.
No reason at all 😁 and since it's causing that bad behavior, it should be moved to the client script has you suggested.
Comment #42
marcofernandes commentedComment #43
marcofernandes commentedComment #47
thorandre commentedComment #48
thorandre commentedComment #49
marcofernandes commented