-
Notifications
You must be signed in to change notification settings - Fork 219
Remove fix to load our stylesheets after editor CSS. See ... #3225
Comments
🚀 Please do not change this issue title! The todo action uses it to prevent duplicate issues from being opened. If you think this is an error, please open an issue! |
1 similar comment
🚀 Please do not change this issue title! The todo action uses it to prevent duplicate issues from being opened. If you think this is an error, please open an issue! |
This issue has been marked as |
This issue has been marked as Internal: After 10 days with no activity this issue will be automatically be closed. |
This issue has been marked as Internal: After 10 days with no activity this issue will be automatically be closed. |
Is this still needed @Aljullu - I think we implemented an alternate way of handling this recently? |
In #3898 we refactored this code, but the work-around to load our stylesheets after editor CSS is still there. So I think we should keep this issue open to keep track of it. The interesting thing is that I tested removing the work-around and I was unable to reproduce #3068 anymore (tested with WP 5.5, 5.7 and latest Gutenberg). I'm not sure what changed since the work-around was implemented, but I think it might be safe to remove it now. I will take a look tomorrow. |
Remove fix to load our stylesheets after editor CSS. See #3068 for the rationale of this fix. It should be no longer github.com/WordPress/gutenberg/issues/20797).
https://github.com/woocommerce/woocommerce-gutenberg-products-block/blob/e07de12ed23db91cd977be4423132f3151573d87/src/Assets.php#L39-L51
🚀 This issue was generated by the automations bot based on a
todo
comment in e07de12 when #3219 was merged. cc @AljulluThe text was updated successfully, but these errors were encountered: