Hi, Mike:
This is a little obscure, but it does demonstrate the problem:
First, you have to recognize that all select-on-change events are
processed by the same routine ("SlctOnChnge") . However, because of
the obfuscation, this statement cannot be isolated. But, statement #1
can be designated. When you do this and then make a selection from any
one of the selectors in the upper frameset, you will notice (by the
reaction delay) that Firebug does not react to the code execution
associated with the actual selection. Rather, it is responding to code
execution associated with a selector in the entity detail form in the
lower right.
Hope this helps ...
On Jul 6, 2:59 pm, Mike Ratcliffe <[email protected]> wrote:
> Hi Chinner
>
> Do you have a test case that explains how to trigger the problem?
>
> e.g.
> 1. Go to georgiansoftware.com
> 2. Log in using Guest:Guest2009
> 3. Select the script tag
> 4. Select script X
> 5. Set a breakpoint on line X
> etc.
>
> On Jul 6, 6:58 pm, chinner <[email protected]> wrote:
>
> > I am a long-time user of Firebug but have been working in the Android
> > world for the past 6 months or so. Now, when I return to some old code
> > and try to use Firebug, it won't respond to a breakpoint setting. [I'm
> > using v1.5.4 under Firefox v3.6.6] The only weird thing I can think of
> > is that I'm trying to debug a page with multiple frame and frameset
> > elements in it. Firebug will respond to breakpoints only in the lowest
> > visible frameset.
>
> > The architecture here can be viewed in the web site
> > georgiansoftware.com [user name: 'Guest' password:'Guest2009']
>
> > Thanks in advance ...
--
You received this message because you are subscribed to the Google Groups
"Firebug" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/firebug?hl=en.
