Make WordPress Core

#57917 closed defect (bug) (reported-upstream)

Beta Editor slowdown on Safari when searching for new blocks to add

Reported by: astatide's profile astatide Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Editor Keywords: close
Focuses: Cc:

Description

Hi! Forgive me if this bug is a duplicate or if I need to add more info; first time reporting! Also, please let me know if this is the wrong place.

Using the beta editor on Safari 16.3 on an M1-based MacBook Air running on Ventura 13.2.1, there is a substantial slowdown to the browser tab when searching for a block type to add: it takes a lengthy bit of time for the letters to all appear, and then any search results are slow to come in and have the images load.

There doesn't appear to be anything suspicious in the console, but I'm not sure specifically what is powering the new editor so I'm not too sure where to look. I'm not running any ad blocker that might result in an improperly blocked failed call (although my network does run AdGuardHome)

So far I've tested with Firefox on both Linux (nixOS; unsure of the Firefox version) and the Mac (110.0.1) and the comparison is night and day; it's lighting fast in FireFox on both browsers.

Unsure if it's a webkit issue or whether any custom theme would be a problem here. If it's a duplicate or if I can provide more information please let me know!

Change History (6)

#1 @costdev
12 months ago

  • Keywords reporter-feedback added

Hi @astatide, welcome to Trac and thanks for opening this ticket!

Can you confirm the version number of WordPress that you're currently using? Thanks!

#2 @astatide
12 months ago

Hi!

I'm using the .com site of WordPress, which sounds like it's running a bleeding edge version judging by my random internet searches.

#3 @hellofromTonya
12 months ago

  • Keywords close added

Hello @astatide,

The Editor is developed and maintained in the Gutenberg repository. Its @wordpress packages are consumed by WordPress Core. Thus this ticket needs to be reported upstream where front-end contributors can better help investigate and diagnose.

@astatide do you mind opening an issue here? Once opened, please copy a link to it into this ticket to wire the bug reports together.

I'm adding the close keyword as when the bug is reported in Gutenberg, then this ticket can be closed.

Thank you :)

Last edited 12 months ago by hellofromTonya (previous) (diff)

#4 @astatide
12 months ago

Not at all! I would be delighted to : ). Thank you so much!

#6 @hellofromTonya
12 months ago

  • Keywords reporter-feedback removed
  • Milestone Awaiting Review deleted
  • Resolution set to reported-upstream
  • Status changed from new to closed

Awesome. Thank you @astatide :)

Closing this ticket now as reported upstream.

Note: See TracTickets for help on using tickets.