You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
async style loading is different from async js loading. async doesn’t exist for styles, it’s a hack. it sets the stylesheet as a print stylesheet, which allows it to load but keeps the browser from applying the styles. then once the file is loaded, the print media attribute is replaced, at which point the browser applies the styles.
Use Case
Stylesheet assets added by this plugin appear in Query Monitor, just like assets added by wp_enqueue_style. Even though they have different implementations, they should be visible to a developer.
The text was updated successfully, but these errors were encountered:
I'm currently testing an approach in a client site, that essentially means adding the file to WP_Dependencies, faking its addition without actually enqueuing it. But need to confirm any possible side effects .
Description
In a project, while adding the following asset, I noticed it is not registed in Query Monitor:
@goodguyry confirmed here the reason.
Use Case
Stylesheet assets added by this plugin appear in Query Monitor, just like assets added by
wp_enqueue_style
. Even though they have different implementations, they should be visible to a developer.The text was updated successfully, but these errors were encountered: