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

Known issues to be addressed

Other tasks

Issue fork gutenberg-3334499

Command icon Show commands

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

marcofernandes created an issue. See original summary.

marcofernandes’s picture

Issue summary: View changes
marcofernandes’s picture

Issue summary: View changes

  • marcofernandes committed dd8efb2b on 3.0.x
    Issue #3334499 fix: Temporary fix for missing node form action buttons
    

  • marcofernandes committed 3391e2a4 on 3.0.x
    Issue #3334499 fix: Add missing properties when loading synced patterns...

  • marcofernandes committed 98b61076 on 3.0.x
    Issue #3334499: Remove Bartik and Seven related styles; Update compiled...
marcofernandes’s picture

Issue summary: View changes
marcofernandes’s picture

Issue summary: View changes

marcofernandes’s picture

Issue summary: View changes
marcofernandes’s picture

Issue summary: View changes
marcofernandes’s picture

Issue summary: View changes
marcofernandes’s picture

Issue summary: View changes
marcofernandes’s picture

Issue summary: View changes
marcofernandes’s picture

Issue summary: View changes
marcofernandes’s picture

Issue summary: View changes
marcofernandes’s picture

Issue summary: View changes

marcofernandes’s picture

Issue summary: View changes
marcofernandes’s picture

Issue summary: View changes

  • marcofernandes committed 1c7228d6 on 3.0.x
    Issue #3334499 by marcofernandes: Fix flickering when transitioning from...

  • marcofernandes committed 94e5099c on 3.0.x
    Issue #3334499 by marcofernandes: Improve behaviour when clicking More...
marcofernandes’s picture

Issue summary: View changes
Status: Active » Needs review

Enough 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.

  • marcofernandes committed 96a5a641 on 3.0.x
    Issue #3334499 by marcofernandes: fetch API changed a bit for media...

marcofernandes’s picture

Issue summary: View changes
Status: Needs review » Needs work
marcofernandes’s picture

Issue summary: View changes

  • marcofernandes committed f65a5da7 on 3.0.x
    Issue #3334499 by marcofernandes: Update Gutenberg library - update...

marcofernandes’s picture

Issue summary: View changes
Status: Needs work » Needs review

codebymikey’s picture

The 94e5099c9 commit 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:

'onclick' => 'moreSettingsClick(this);',

rather than a dynamic toggle event 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:

$('details.more-settings', context).on('toggle', function () {
  if (this.open) {
    this.scrollIntoView({
      behavior: 'smooth',
      block: 'start',
      inline: 'nearest',
    });
  }
});

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.

codebymikey’s picture

I've pushed an update removing the onClick event listener from the element, we may attach the toggle event listener referenced above in a further commit if it's still useful/necessary.

marcofernandes’s picture

I 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.

Also, is there a reason we opted to handle this in PHP

No reason at all 😁 and since it's causing that bad behavior, it should be moved to the client script has you suggested.

marcofernandes’s picture

Issue summary: View changes
marcofernandes’s picture

Issue summary: View changes

thorandre credited helderm.

thorandre’s picture

thorandre’s picture

marcofernandes’s picture

Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.