It appears that Chrome caches stylesheet files regardless of whether the server would return a newer one. This messes up the display when trying different examples (For example first Chat.hs, then BarTab.hs) or when developing an application.
I don't know how to fix this right now, but it probably involves setting sone sort of "no-cache" header in the HTTP response. This should be done not only for style files, but for all other files (JS, loadFile) as well. We assume that the server runs on localhost anyway.
It appears that Chrome caches stylesheet files regardless of whether the server would return a newer one. This messes up the display when trying different examples (For example first Chat.hs, then BarTab.hs) or when developing an application.
I don't know how to fix this right now, but it probably involves setting sone sort of "no-cache" header in the HTTP response. This should be done not only for style files, but for all other files (JS, loadFile) as well. We assume that the server runs on localhost anyway.