Filters on pattern archive page not working

[gaeldenysiak]

When you are on the patterns archive page and your want to filter sync or not sync pattern, the back office crash with this js error :

DOMException: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.

[gaeldenysiak]

Oh sorry, i knew this kind of error but i just want to notice this for the twenty twenty four theme on fresh install of WP6.6. Is there another way to notice that kind of error for contributor, or maybe i make a mistake configuring the ticket.

[flutterdevpro]

@gaeldenysiak Do not know another way to notice that kind of error for contributor. Maybe somebody else :)

[poena]

Hi @gaeldenysiak
I am not able to reproduce this problem, using 6.6.0, 6.6.1 RC, and Twenty Twenty-Four. Can you add any more details and step by step instructions for how to reproduce it?

I went to Appearance > Editor
Selected Patterns
Then I clicked on the grey button that says "Sync status".

• I selected synced from the drop down -no error shows.
• I selected not synced from the drop down -no error shows

I tested both grid and table layouts.
Then I created a new synced pattern and repeated the tests, and I do not see any errors.

I am using Chrome on Windows 11.
I understand that you tested on a fresh installation, and I assume that means you have no plugins active, did you also disable browser extensions?
Are you using any other browser tools such as the React developer tools?

[gaeldenysiak]

Oh that's my browser.. I'm on Brave, i tried on FF and works well. If i identified the extension of part of Brave that create that i would share here.

Thanks Carolina

[hellofromTonya]

Reproduction Report

This report validates that the issue can be reproduced.

Environment

• OS: macOS
• Web Server: Nginx
• PHP: 7.4.29
• WordPress:
  • 6.5.5
  • 6.6.2
  • c
• Browser:
  • Firefox 131.0
  • Brave 1.70.123
• Theme: Twenty Twenty-Four
• Active Plugins: None

Steps to Reproduce

Repeat these steps for each WP version and browser.

Using the same steps provided by @poena in comment:5:

1. Go to Appearance > Editor.
2. Select Patterns.
3. Click/trigger the "Sync Status" button.
4. Select "Synced" in the dropdown.
5. 🐞 Bug should occur here.
6. Repeat step 3.
7. Select "No synced" in the dropdown.
8. 🐞 Bug should occur here.

Expected Results

When reproducing a bug:

• ❌ Error should occur at Step 5.
• ❌ Error should occur at Step 8.

Actual Results

Results of testing with the Brave browser, fresh install of WP 6.5.5, 6.6.2, and 6.7-beta1-59152-src:

• ❌ Unable to reproduce the error at Step 5.
• ❌ Unable to reproduce the error at Step 8.

Same results with Firefox and Chrome browsers.

Additional Notes

I'm not able to reproduce the reported error with the Brave browser.

No error happens in my testing with a fresh install of the Brave browser (no extensions) and WP 6.5.5, 6.6.2, and 6.7-beta1-59152-src.

[hellofromTonya]

Hello @gaeldenysiak,

Welcome to WordPress Core's Trac. I'm sorry to hear you are having difficulty with your site after updating to 6.6.x.

Thank you sharing more information that it's not working for you with the Brave browser, but does with Firefox.

Like @poena, I too am unable to reproduce this issue. I tested it with the Brave browser (no extensions and a fresh download/install). It works for me and has the same results with WP 6.5.5, 6.6.2, and 6.7-beta1-59152-src.

With 2 unable to reproduce reports and you noting it's only with the Bravo browser, seems to be an issue Currently, it does not appear to be an issue related to the browser. The conflict could be from an extension or something else. But it doesn't appear to be a bug in WordPress Core's software.

Please note, this Trac is used for the development of the WordPress software itself, not for support or assistance with individual sites, themes, frameworks, or plugins.

You can find people who are able to assist with your site in the ​WordPress support forums.

I've closed this ticket as invalid, which is Trac's unfriendly term to indicate I've referred you to the support team.