• Hi Team,

    Why do I get this error in the console every time I delete an image from the Media Library?
    I only have WordPress and Storefront installed; no plugins or custom functions.

    load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,moxiejs,plupload&ver=6.8.3:2 [Violation] ‘click’ handler took 1110ms

    upload.php?item=17:1 Blocked aria-hidden on an element because its descendant retained focus. The focus must not be hidden from assistive technology users. Avoid using aria-hidden on a focused element or its ancestor. Consider using the inert attribute instead, which will also prevent focus. For more details, see the aria-hidden section of the WAI-ARIA specification at https://w3c.github.io/aria/#aria-hidden. Element with focus: li.attachment save-ready
    Ancestor with aria-hidden : div#wpwrap

Viewing 7 replies - 1 through 7 (of 7 total)
  • Moderator threadi

    (@threadi)

    I’m not sure where the quote begins in your post. To me, it looks like a timeout.

    Where exactly did you click on “Delete”? Feel free to show us with a screenshot: https://wordpress.org/support/forum-user-guide/block-editor/#adding-screenshots

    Does this happen with every file or just with one?

    Also check under Tools > Site Health to see if there are any issues listed there.

    Thread Starter Thomas

    (@thomhsb)

    Hi @threadi,

    This is : Videos | Library | Loom – 1 December 2025

    In terms of the site’s health, there’s nothing exceptional, just basic errors that are common when you’ve just installed WordPress.

    Thread Starter Thomas

    (@thomhsb)

    I just tried again on a completely fresh WordPress installation, without installing anything else, same error message.

    This is a performance warning, not a true “breakage.” WordPress’s media deletion process is sometimes a bit sluggish in the background. The browser is just saying “Hey, this click handler took over a second, that’s not great for user experience.” It’s annoying, but it likely won’t break anything on a simple site. It’s more of a WordPress core optimization thing.

    Thread Starter Thomas

    (@thomhsb)

    I didn’t assume it was serious; I just wanted to let you know.

    When one of my plugins generates this kind of error, even just a warning, I try to fix it.
    I thought it would be helpful to share it with you, that’s all.

    Thanks anyway, and congratulations on this fantastic CMS.

    Moderator threadi

    (@threadi)

    As already mentioned, this is not an error. Reporting this in the forum will not achieve anything—we read and acknowledge it. However, nothing will change, as no tickets for WordPress development are created here.

    My recommendation would be to report this in Core Trac (where tickets are created) so that the developers there can evaluate it and make adjustments if necessary. I suspect it would also be a topic for the upcoming revision of the AdminUI.

    Thread Starter Thomas

    (@thomhsb)

    I understand perfectly, and I didn’t say it was a critical error.
    Anyway, sorry to have bothered you.

Viewing 7 replies - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.