>
> except FF magically keeps upgrading us to the latest version of firebug
> (in spite of the fact we have specified NOT to upgrade us automatically)!
>
Did you uncheck the option *Update Add-ons Automatically* within the
Add-ons Manager?
Sebastian
On Monday, August 18, 2014 11:13:18 PM UTC+2, Sebastian Zartner wrote:
>
> I put your code into a simple test case, which I attached to this post.
> Using Firefox 31.0 + Firebug 2.0.3 on Win8.1.
> The lines are correctly marked as executable, I can set a breakpoint at
> the line containing if (x == 1) { and it also gets it when I reload the
> page.
>
> I assume you have a syntax error within your script. When there is a
> syntax error within a script, you may not be able to set a breakpoint in
> it. So please check whether there are any JavaScript errors shown within
> the *Console* panel <https://getfirebug.com/wiki/index.php/Console_Panel>
> (ensure you have the option *Show JavaScript Errors* checked).
> If you can exclude syntax errors as the cause, please provide a complete
> test case <https://getfirebug.com/wiki/index.php/Creating_a_Test_Case>
> and describe the steps to reproduce the problem.
>
> Sebastian
>
> On Friday, August 15, 2014 12:53:12 AM UTC+2, AJ123abc wrote:
>>
>> I just upgraded to 2.0.3, and I still see the issue where line numbers
>> are not in sync with the actual code.
>> That is for example:
>>
>> 1: var x = 1;
>> 2: if (x == 1) {
>> 3: someFunction(x);
>>
>> In the debugger I see line 2 as being grayed out thus not able to set a
>> break point on that line, But can do so on line 3. Except when the break
>> point happens on line 3, it is actually executing line 2 (the IF statement).
>>
>> This problem started happening in 2.0.2 and now in 2.0.3. It has impacted
>> all my team badly. We keep switching back to 1.12.8, except FF magically
>> keeps upgrading us to the latest version of firebug (in spite of the fact
>> we have specified NOT to upgrade us automatically)!
>>
>>
>>
>> On Wednesday, August 13, 2014 12:14:53 AM UTC-7, Sebastian Zartner wrote:
>>>
>>> On Tuesday, August 12, 2014 11:21:46 PM UTC+2, AJ123abc wrote:
>>>>
>>>> Frankly, I am baffled as how this works for anyone else...? Everyone in
>>>> my team has the same issue with 2.0.2 where line numbers are not in sync
>>>> with the code and hence making debugging literally impossible. We have
>>>> tried uninstall/re-install into new profile,etc. (using FF version 31).
>>>>
>>> Could it be that besides posting here you also created issue 7625
>>> <https://code.google.com/p/fbug/issues/detail?id=7625>?
>>> What do you actually mean with "line numbers are not in sync with the
>>> code"? Is it the same as described in issue 7615
>>> <https://code.google.com/p/fbug/issues/detail?id=7615>? If not, please
>>> provide a test case, so it can be reproduced what you mean.
>>>
>>> Also another issue with 2.0 is that, when adding a new variable to watch
>>>> (under watch tab) it used to get added at the top of the list, now it is
>>>> added at the bottom and user has to scroll down. Usually, you want to see
>>>> the most recent added variables to watch at the top.
>>>>
>>> FWIW this was reported earlier in another thread
>>> <https://groups.google.com/d/topic/firebug/J1s4ZApnp-s/discussion>. You
>>> should create an issue for that
>>> <https://code.google.com/p/fbug/issues/entry?template=User%20enhancement%20request>
>>> .
>>>
>>> Sebastian
>>>
>>> On Tuesday, August 12, 2014 3:02:26 AM UTC-7, Sebastian Zartner wrote:
>>>>>
>>>>> There are some problems
>>>>> <https://code.google.com/p/fbug/issues/detail?id=7615> regarding
>>>>> dynamic script display within the *Script* panel in Firebug 2.0.2.
>>>>> Instead of switching back to an earlier version of Firebug I suggest you
>>>>> wait for the next bug fix release (which should be this or next week).
>>>>> If you want to switch back anyway, you can find all Firebug versions
>>>>> on addons.mozilla.org
>>>>> <https://addons.mozilla.org/firefox/addon/firebug/versions/>.
>>>>>
>>>>> Sebastian
>>>>>
>>>>> On Tuesday, August 12, 2014 8:51:08 AM UTC+2, AJ123abc wrote:
>>>>>>
>>>>>> For me it continues to happen even with installing firebug (2.0.2)
>>>>>> into a new profile... this was working fine with 2.0. I have a hard time
>>>>>> finding from where I can go back to 2.0...?
>>>>>>
>>>>>>
>>>>>> On Friday, July 25, 2014 1:08:31 AM UTC-7, Sebastian Zartner wrote:
>>>>>>>
>>>>>>> Ok, so it's either related to the profile settings or a conflict
>>>>>>> with other extensions. Can you please investigate this further
>>>>>>> following
>>>>>>> the steps described in our first aid page
>>>>>>> <https://getfirebug.com/wiki/index.php/I_found_a_Firebug_Bug!#To_understand_the_problem_so_it_can_be_fixed>
>>>>>>> ?
>>>>>>>
>>>>>>> Sebastian
>>>>>>>
>>>>>>> On Wednesday, July 23, 2014 9:24:59 PM UTC+2, Brian Merz wrote:
>>>>>>>>
>>>>>>>> This is fixed when a new profile is created and Firebug installed
>>>>>>>> there.
>>>>>>>>
>>>>>>>> On Monday, July 21, 2014 12:49:31 AM UTC-7, Sebastian Zartner wrote:
>>>>>>>>>
>>>>>>>>> Do you have test cases for these three points, so we can reproduce
>>>>>>>>> the problem?
>>>>>>>>> Does the problem go away, if you create a new profile and just
>>>>>>>>> install Firebug
>>>>>>>>> <https://getfirebug.com/wiki/index.php/Install_Firebug_into_a_clean_profile>
>>>>>>>>>
>>>>>>>>> in it?
>>>>>>>>>
>>>>>>>>> Sebastian
>>>>>>>>>
>>>>>>>>> On Friday, July 18, 2014 8:53:45 PM UTC+2, Lomikar wrote:
>>>>>>>>>>
>>>>>>>>>> Hi Honza;
>>>>>>>>>>
>>>>>>>>>> Breakpoints seem still to have issues:
>>>>>>>>>> 1: The code vs breakpoints panes are getting out of sync.
>>>>>>>>>> 2. Spinner sometimes doesn't go away.
>>>>>>>>>> 3: And now function keys F8, F10, F11 and Ctrl/Shift+F11 don't do
>>>>>>>>>> anything. Same by clicking on them in UI.
>>>>>>>>>>
>>>>>>>>>> Thank you
>>>>>>>>>> Lumir
>>>>>>>>>>
>>>>>>>>>
--
You received this message because you are subscribed to the Google Groups
"Firebug" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/firebug.
To view this discussion on the web visit
https://groups.google.com/d/msgid/firebug/4fa8f1d3-15c1-4bc8-9d45-4477f9cec9e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
