JavaScript Cache Bug(?)



  • Has someone noticed this? This is not particular a new bug to the latest Vivaldi release. I actually noticed this bug even since last year because I do some web development.

    Not sure if it's a Chrome issue.

    When I do development in Vivaldi I noticed that changes to some JavaScript files are never updated in Vivaldi, but in Firefox they do. It seems Vivaldi is caching JavaScripts way beyond the normal time or has a problem detecting when they changed or have new content.

    I even closed the browser, come back a day later, open the same page where the JS is linked and Vivaldi is still loading the old version. If I you then manually open the JS file url, and hit Reload in Vivaldi, its now properly loads the new and updated version and then the site also is loading the new from that point on, but unless you do this, Vivaldi catches it seems like for ever. It seems to only happen with JavaScript files linked in a page where the changes where minimal.

    I can imagine that tons of web apps bugs and sites could potentially be caused by this if they are sending a small change in a JS file and Vivaldi is not detecting it.



  • Cache bug? Really?

    How do you do your Web development?

    The file stays in browser cache for the period which is set in your webserver's HTTP headers (Expires, Last-Modified, ETag, Cache-Control).



  • Not a bug. I tested it on my server. My server sends for the JS file a Expire of access plus 5 seconds.
    And every time i start Vivaldi, it fetches the new content.



  • No need to be rude Gwen-Dragon.

    I have experienced the same problem where local changes in my javascript file are not shown when I access my server through Vivaldi. But as terere said, if I use Firefox it updates straight away. If it was a server setting surely there shouldn't be a difference between Firefox and Vivaldi.



  • @DanielWa Are you talking about changes in your files on you local PC or in Developer Tools? If you talk about Developer Tools the Mozilla and Chromium are not the same.

    I cant guess what you mean:

    same problem where local changes in my javascript file are not shown when I access my server through Vivaldi

    Local changes in your JS file do not affect the caching on your server.



  • You can disable caching in Vivaldi's Developer Tools for the page you test.
    In Developer Tools you can find it in Network tab.
    Then you will not have any problems with not detected changes.

    If that does not solve the problem, please create reproducible testcase and report it as a bug. We will check this.


    How to do a bugreport for Vivaldi
    Report the bug at https://vivaldi.com/bugreport/
    Describe the issue as precise as you can.
    If you use any extensions please give information which ones you use.
    If you have a URL or a own testpage which can checked, add it to the bugreport.
    If you have own testcase files (HTML, CSS, JS etc.) add them to the confirmation mail you get after report.
    If you have a screenrecording video, you can attach it to give the developers a hint how this might happen or look like.
    You will get a bug confirmation mail and in a reply to this mail you can add more information and files as attachments for the testers and bug tracking team.

    Thanks in advance for helping us to make Vivaldi better!


    Please give me a description, i do not understand how to test the problem.
    The information to reproduce it is not enough for me. Perhaps i have a problem in understanding or we use different words to describe problems an techniques or i have a problem in understanding your english (i am not grown up with english people -- sorry).


Log in to reply
 

Looks like your connection to Vivaldi Forum was lost, please wait while we try to reconnect.