Live preview sometimes ignores CSS changes, especially when Chrome was closed before #2858
Comments
|
Doesn't happen when using a server, so it seems to be a local file permissions problem. |
|
Removing 'Win only' since we now think this happens on Mac too -- it's just timing-sensitive and thus the ease of repro varies from machine to machine. |
|
This also repros in Sprint 19. We believe it actually repros in Sprint 17-18 and Edge Code preview 2 as well. We've also reproduced it at least once in an older version of Chrome. It's not clear what has changed to make it much easier to repro suddenly, but it's possible the Chrome update on 1/30 altered timing in a way that makes it easier to hit. |
…l page corresponding to the current document (not the interstitial page).
…l page corresponding to the current document (not the interstitial page).
ghost
assigned 
|
@gruehle: Reviewed - as discussed today this is an exception for Sprint 20. Consequently assigning it to Sprint 21. |
|
Marking as Medium priority as this seems somewhat intermittent and actually no data loss. |
|
Removing from sprint 21--this was moved to https://trello.com/c/R0ZFrFV4 |
|
This is in sprint 22 as part of the RESEARCH: Live Development Robustness card. No need to add to the bug card. Reassigning to @iwehrman. |
|
This was automagically closed by Github because it was mentioned in pull #3142. I'm re-opening it so someone else can confirm properly, but I can't reproduce the issue and do believe that pull fixes it. |
|
Tagged FBNC and assigning back to @RaymondLim |
|
Fix verified. |
<body>tag, Ctrl-EResult: you don't see the update in Chrome.
The text was updated successfully, but these errors were encountered: