Firebug doesn't stop at breakpoints

[dd-12]

That's kind of the most basic requirement for me. I load up a web page
which has some JS files included. I open up Firebug 1.4.3 in my
Firefox 3.5.3, then I choose one of the script files, click on a line
of code inside a function. I get the red dot confirming the breakpoint
location was good. So I click reload in Firefox and the breakpoint is
completely ignored. The code (which is most definitely being called)
simply ignores the breakpoint. Same thing in visual studio on IE and
the breakpoint is hit every time.

--

You received this message because you are subscribed to the Google Groups "Firebug" group.
To post to this group, send email to firebug@....
To unsubscribe from this group, send email to firebug+unsubscribe@....
For more options, visit this group at http://groups.google.com/group/firebug?hl=en.

[dd-12]

On Oct 26, 7:21 pm, dd <dd4...@...> wrote:
> That's kind of the most basic requirement for me. I load up a web page
> which has some JS files included. I open up Firebug 1.4.3 in my
> Firefox 3.5.3, then I choose one of the script files, click on a line
> of code inside a function. I get the red dot confirming the breakpoint
> location was good. So I click reload in Firefox and the breakpoint is
> completely ignored. The code (which is most definitely being called)
> simply ignores the breakpoint. Same thing in visual studio on IE and
> the breakpoint is hit every time.

I *think* I know why this is happening. To cache-bust the script file
(i.e. to prevent it being cached) I load the script via a
document.write with a script tag, and appended to the path/filename I
add a query string with a random number. So my request one time might
be myscript.js?12345678 and the next time it might be myscript.js?
86849283. It seems that Firebug is not treating these as the same
file. I can understand why it might fall on the side of assuming the
file will be different because the random number could well be an
instruction to a dynamic server to use that number to generate the
script to be returned differently. It would be nice if we could
somehow make Firebug ignore query strings when it comes to
breakpoints. I know I have a myriad of options for cache-busting, but
this is what's implemented and I can't just get a whole project to
change how it's working without significant resistance.

--

You received this message because you are subscribed to the Google Groups "Firebug" group.
To post to this group, send email to firebug@....
To unsubscribe from this group, send email to firebug+unsubscribe@....
For more options, visit this group at http://groups.google.com/group/firebug?hl=en.

[Mike Ratcliffe-2]

Hi dd, thanks for this info. Can you log a bug over at:
http://code.google.com/p/fbug/issues/list

When you do then please attach a test case ... just a small HTML file
that illustrates the problem.

On Oct 26, 8:11 pm, dd <dd4...@...> wrote:

> On Oct 26, 7:21 pm, dd <dd4...@...> wrote:
>
> > That's kind of the most basic requirement for me. I load up a web page
> > which has some JS files included. I open up Firebug 1.4.3 in my
> > Firefox 3.5.3, then I choose one of the script files, click on a line
> > of code inside a function. I get the red dot confirming the breakpoint
> > location was good. So I click reload in Firefox and the breakpoint is
> > completely ignored. The code (which is most definitely being called)
> > simply ignores the breakpoint. Same thing in visual studio on IE and
> > the breakpoint is hit every time.
>
> I *think* I know why this is happening. To cache-bust the script file
> (i.e. to prevent it being cached) I load the script via a
> document.write with a script tag, and appended to the path/filename I
> add a query string with a random number. So my request one time might
> be myscript.js?12345678 and the next time it might be myscript.js?
> 86849283. It seems that Firebug is not treating these as the same
> file. I can understand why it might fall on the side of assuming the
> file will be different because the random number could well be an
> instruction to a dynamic server to use that number to generate the
> script to be returned differently. It would be nice if we could
> somehow make Firebug ignore query strings when it comes to
> breakpoints. I know I have a myriad of options for cache-busting, but
> this is what's implemented and I can't just get a whole project to
> change how it's working without significant resistance.

--

You received this message because you are subscribed to the Google Groups "Firebug" group.
To post to this group, send email to firebug@....
To unsubscribe from this group, send email to firebug+unsubscribe@....
For more options, visit this group at http://groups.google.com/group/firebug?hl=en.

[dd-12]

On Oct 26, 9:16 pm, Mike Ratcliffe <mich...@...>
wrote:
> Hi dd, thanks for this info. Can you log a bug over at:http://code.google.com/p/fbug/issues/list
>
> When you do then please attach a test case ... just a small HTML file
> that illustrates the problem.

Done. Bug 2432
http://code.google.com/p/fbug/issues/detail?id=2432

--

You received this message because you are subscribed to the Google Groups "Firebug" group.
To post to this group, send email to firebug@....
To unsubscribe from this group, send email to firebug+unsubscribe@....
For more options, visit this group at http://groups.google.com/group/firebug?hl=en.