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
When a CSS stylesheet is loaded via style-loader and injectType: 'lazyStyleTag', and HMR is enabled, updating the stylesheet file should result in the style being hot replaced in the browser, regardless of the current state of the use/unuse ref count. (If the style is unused at the time, the changes should be visible when the style is next used.)
Actual Behavior
If the style is in use, then the change is visible, but as soon as the style is unused and then used again (or if the style is unused at the time of the HMR event), then the style reverts to its original value until the page is cold reloaded.
Code + How Do We Reproduce?
Check out https://github.com/rhendric/upgraded-spork for a minimal reproduction. Clicking the button toggles the stylesheet on and off. Edit the background color in src/index.css and then click the button a few times to reproduce the issue.
The text was updated successfully, but these errors were encountered:
Expected Behavior
When a CSS stylesheet is loaded via
style-loader
andinjectType: 'lazyStyleTag'
, and HMR is enabled, updating the stylesheet file should result in the style being hot replaced in the browser, regardless of the current state of theuse
/unuse
ref count. (If the style is unused at the time, the changes should be visible when the style is next used.)Actual Behavior
If the style is in use, then the change is visible, but as soon as the style is unused and then used again (or if the style is unused at the time of the HMR event), then the style reverts to its original value until the page is cold reloaded.
Code + How Do We Reproduce?
Check out https://github.com/rhendric/upgraded-spork for a minimal reproduction. Clicking the button toggles the stylesheet on and off. Edit the background color in
src/index.css
and then click the button a few times to reproduce the issue.The text was updated successfully, but these errors were encountered: