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
Hi. Loading too much unnecessary JS is always a concern. Human-curated meta box configuration is not sustainable.
I'm thinking we could scan via the_content filter, or possibly output buffer the whole page output, for a heuristic on whether to load our JS/CSS assets at all.
Your thoughts?
The text was updated successfully, but these errors were encountered:
This is an interesting idea. I'm not sure that scanning the_content would be robust enough as many pages could be built using meta data, widgets, etc. I'm open to reviewing a PR for this, if you have something specific in mind.
Hi. Loading too much unnecessary JS is always a concern. Human-curated meta box configuration is not sustainable.
I'm thinking we could scan via
the_content
filter, or possibly output buffer the whole page output, for a heuristic on whether to load our JS/CSS assets at all.Your thoughts?
The text was updated successfully, but these errors were encountered: