We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

Code displayed in the debugger does not match the response received from the server

  • 6 отговора
  • 1 има този проблем
  • 6 изгледи
  • Последен отговор от GNURush

more options

See the attached screenshots and note the error function that is present on line 215 in the response, but does not appear in the debugger. The issue occurs in Firefox 58.0 (64-bit) and Firefox developer edition 59.0b2 (64-bit). I have enabled the option to disable HTTP cache when the developer toolbox is open.

See the attached screenshots and note the error function that is present on line 215 in the response, but does not appear in the debugger. The issue occurs in Firefox 58.0 (64-bit) and Firefox developer edition 59.0b2 (64-bit). I have enabled the option to disable HTTP cache when the developer toolbox is open.
Прикачени екранни снимки

Всички отговори (6)

more options

Try to ask advice at the Stack Overflow forum site. That website is more suitable for questions about web development.

more options

Clearing the cache from the settings menu makes the changes show up in the debugger on the next refresh. It is tedious to clear the cache every time I make a change, so I have disabled caching in about:config, but that slows down browsing everywhere, all the time. It would be nice to have the option to disable local cache while the developer toolbox is open, but I suppose that this has turned into more of a feature request than a question, so I will try a different forum.

more options

There is a checkbox in the toolbox settings to disable the HTTP cache when the toolbox is open.

more options

As stated in my original post, the problem persists with that option enabled. Furthermore, the response from the server contains the updated code, so the caching must be happening locally. I've found an open request in Bugzilla and added what information I can to it: https://bugzilla.mozilla.org/show_bug.cgi?id=1363534

more options

FF can't change codes AFAIK. So did you contact the IT department to ask them what is going on as well?

more options

I am a part of the small IT department at our company. In the screenshots attached to my original post, you can see that the Firefox debugger is displaying different code than it received. Firefox executes the new code received from the server as expected, but I cannot set breakpoints on any new code that I add if it is not displayed in the debugger.