Open raashika03 opened 3 years ago
I think the reason is that html/css file were opened directly by the browser (file://....), while here the index.html is served by a webserver (http://...). I think that caching resources is disabled when loading local files, while fortunately css/js files are cached when querying webserver.
@bryan-brancotte how do you solve this problem in general? Do you disable cache somehow? (many ways are there, I looked) or just you use CTRL+F5 solution every time. Just asking for easeness for next time. I'm closing this issue cause this seems to be a general problem. I was unaware :(
Reopening this, cause I think documenting such kind of general issues somewhere in a separate document named as "general question and their answers" that will contain answer to general questions asked by contributors and the issues which they generally face while contributing to edamontology. And providing the link to this queries.md file somewhere in the contribution.md will be a nice thing ig. This's a thing which might be faced by many newcomers, but finding out the reason for the same may be tricky for them, saying this from my experience :face_with_head_bandage:
While I was working with index.html and index.css, many times my most recent content didn't get reflected locally. Was not able to figure out the reason for the same for two days, that was frustrating as like I mentioned here #46 in the 5th comment.
So, adding this thing somewhere in some file (may be in contribution.md), may be helpful for contributors because most of the people simply reloads using F5 or CTRL+R.
Issue: Recent changes are not reflecting in the internet browser locally on reloading using F5 or CTRL + R. Reason: Your browser isn't ignoring stored cache history. Solution: Use SHIFT + F5 or CTRL + F5 or CTRL + SHIFT + R Instead of using F5 or CTRL + R to reload the current page.
I think this's a general issue, but I worked with other similar projects (changing HTML and CSS files together) and never came across this issue. I'm unable to figure out the reason why this appeared in this project only.