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
At present the timestamp that is added at the end of the links for JavaScript/CSS auto files that appear in the <head> of each page is determined by the last modified time of any Javascript/CSS file that makes up the respective auto-generated file. However, the files included could change without any of them being modified if the inc file is edited to add or remove an ingredient. Therefore, the inc file's last modified time should be incorporated into the timestamps generated for the auto-generated JavaScript/CSS links.
N.B. There is also the possibility that an auto-generated file will change because a JavaScript file is removed. However, as there will be no last modified time to check it is impossible to determine that what the auto-generated would have changed. However, this is a sufficient edge-case and easily fixed by a hard refresh of the browser. There may be a solution but it is certainly not to update the timestamp every time a page is loaded.
The text was updated successfully, but these errors were encountered:
At present the timestamp that is added at the end of the links for JavaScript/CSS auto files that appear in the
<head>
of each page is determined by the last modified time of any Javascript/CSS file that makes up the respective auto-generated file. However, the files included could change without any of them being modified if the inc file is edited to add or remove an ingredient. Therefore, the inc file's last modified time should be incorporated into the timestamps generated for the auto-generated JavaScript/CSS links.N.B. There is also the possibility that an auto-generated file will change because a JavaScript file is removed. However, as there will be no last modified time to check it is impossible to determine that what the auto-generated would have changed. However, this is a sufficient edge-case and easily fixed by a hard refresh of the browser. There may be a solution but it is certainly not to update the timestamp every time a page is loaded.
The text was updated successfully, but these errors were encountered: