debugger doesn't reload javascript code.

[Erik Krause]

Hello,

please forgive if this is not the right place for this question. If so
please point me to the right one.

I develop web pages on a local apache server on windows 10. Now if I
change some javascript code and reload the page, the code in the
debugger tab in developer tools is not updated, while the changed code
is properly executed in the page. So if I fix a bug the functionality is
there in the browser but I can't step through the code, because the
debugger shows an older version.

Not even closing and re-opening the relevant tab solves this issue, I
have to shutdown firefox and start it again to see the changed code.
This happens in both 64-Bit versions 58.0.1 and 59.0b5 and also in safe
mode. So it should be unlikely that an extension is to blame.

However, I searched both google and bugzilla and found nothing recent
about this problem, so it could still be only me. Do you have an idea in
which direction I could go on? Or is this a bug?

--
Erik Krause
Herchersgarten 1
79249 Merzhausen

[Brian Grinstead]

Hi Erik,
I haven’t heard of this issue before but it definitely sounds like a bug. Could you try testing this in a new profile just to be sure it’s not profile-related (as you mention since it reproduces in safe mode that's probably not the problem but worth double checking). Also, could you open the Browser Console (Ctrl+Shift+J) and see if there are any errors coming from the debugger when you reload the page?

Thanks,
Brian

> _______________________________________________
> dev-developer-tools mailing list
> dev-devel...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-developer-tools

[Erik Krause]

Am 31.01.2018 um 22:07 schrieb Brian Grinstead:

> Could you try testing this in a new profile just to be sure it’s not
> profile-related (as you mention since it reproduces in safe mode
> that's probably not the problem but worth double checking).

Well, it seems to be profile related. I tested in a new profile and it
worked as expected. No problems there, the correct code is shown, it
changes on reload.

> Also, could you open the Browser Console (Ctrl+Shift+J) and see if
> there are any errors coming from the debugger when you reload the
> page?

No errors in the Browser Console.

Now of course I could proceed with the new profile. But that would
involve a day or two of work to reestablish all extensions, settings
etc. So I'd be very grateful if there was a shorter solution. Any ideas
where I could search?

[Erik Krause]

Am 31.01.2018 um 22:59 schrieb Erik Krause:
>> Could you try testing this in a new profile just to be sure it’s not
>> profile-related (as you mention since it reproduces in safe mode
>> that's probably not the problem but worth double checking).

> Well, it seems to be profile related. I tested in a new profile and it
> worked as expected. No problems there, the correct code is shown, it
> changes on reload.

It is not profile related. It depends on the setting of "Disable HTTP
cache (when toolbox is open)". In the new profile this was unchecked,
hence it worked. In both other profiles (for FF 58 and 59) it was
checked, hence it didn't work. So if I uncheck this setting it works as
expected in all profiles.

Do I misunderstand this sertting or is this a bug?

[Erik Krause]

Hello!

I'd like to stress this point again.

If I *check* "Disable HTTP cache (when toolbox is open)" the debugger
does *not* reload javascript code if the page is reloaded.

If this is *unchecked*, the debugger does reload javascript code.

Is this really the way it is intended to work?

For my understanding a disabled cache would mean the content is always
reloaded from source.

[Jason Laster]

Thanks Erik! I agree that this is not intuitive and likely broken.

I'm curious what Honza, bgrins, or Jim think?

[J. Ryan Stinnett]

Erik, do you happen to be debugging inline scripts in an HTML document? Or
are you seeing this issue with separate JS files?

There is some known confusion around inline scripts, see
https://bugzilla.mozilla.org/show_bug.cgi?id=1248498.

- Ryan

[Erik Krause]

Am 27.02.2018 um 00:21 schrieb J. Ryan Stinnett:
> Erik, do you happen to be debugging inline scripts in an HTML document? Or
> are you seeing this issue with separate JS files?

It happens for inline scripts only. separate JS files are refreshed on
page reload.

> There is some known confusion around inline scripts, see
> https://bugzilla.mozilla.org/show_bug.cgi?id=1248498.

I see. So the debugger loads from cache even if caching is disabled, in
which case the cache isn't refreshed and I see the old source?

[J. Ryan Stinnett]

On Tue, Feb 27, 2018 at 11:20 AM, Erik Krause <erik....@gmx.de> wrote:

>
> There is some known confusion around inline scripts, see
>> https://bugzilla.mozilla.org/show_bug.cgi?id=1248498.
>>
>
> I see. So the debugger loads from cache even if caching is disabled, in
> which case the cache isn't refreshed and I see the old source?
>

Yes, that's what I recall from looking at this issue last. I'll see if we
can nudge the bug forward. Please follow there for updates.

- Ryan