Related core ticket: https://core.trac.wordpress.org/ticket/50328.
Explore ways in which front-end styles for blocks could be assembled based on which blocks are used in a given page response.
Note: this is a deviation from how themes and resources have operated so far, since a theme usually adds a single stylesheet including all possible HTML a user might add, as well as handling for widgets, etc, that might never be present on a page.
The granularity of blocks, and our ability to tell on the server which blocks are being used, should open up opportunities for being more intelligent about enqueueing these assets.
Considerations
This would need to have proper hooks for disabling and extending, as there will be issues with async loading of content (like infinite scroll) and caching mechanisms if the bundle is dynamic.
Furthermore, it should at least consider how theme supplied styles for blocks might interop. See #5360
Related core ticket: https://core.trac.wordpress.org/ticket/50328.
Explore ways in which front-end styles for blocks could be assembled based on which blocks are used in a given page response.
Note: this is a deviation from how themes and resources have operated so far, since a theme usually adds a single stylesheet including all possible HTML a user might add, as well as handling for widgets, etc, that might never be present on a page.
The granularity of blocks, and our ability to tell on the server which blocks are being used, should open up opportunities for being more intelligent about enqueueing these assets.
Considerations
This would need to have proper hooks for disabling and extending, as there will be issues with async loading of content (like infinite scroll) and caching mechanisms if the bundle is dynamic.
Furthermore, it should at least consider how theme supplied styles for blocks might interop. See #5360