Issues in 1.13a5

[Tim Ryan]

Since upgrading, I'm seeing some new issues

1) In the script panel, objects are no longer expandable.  No plus sign is present and clicking the value takes you to the DOM tab where it expands the top level.  You can click on another property and it updates the DOM panel to drill down to that level.  This doesn't make much sense - you can't see the entire expanded object in on place and if you are looking at multiple objects, you have to constantly switch back & forth between tabs.   This problem also affects the Net tab when trying to drill down in JSON response objects.

2) When hitting the first breakpoint, the script tab doesn't always go to the breakpoint. You have to 'step into' to get to the executing line of code.

3) I've also seen some cases where the tab you're currently on get cleared on a reload and doesn't update it's display until you switch to a different tab and then back again.

[Tim Ryan]

I should also add that i was seeing this on FF24 and now on FF25.0.1

[Simon Lindholm]

I believe the first point should be fixed by https://code.google.com/p/fbug/issues/detail?id=6979; it was fallout from adding "use strict" in too many places. For the others precise STR would be great, of course...

[Tim Ryan]

First point is fixed on both Script and Net tabs

The third point maybe somehow related to setting breakpoints.  I can repro this issue by going to the Net tab, then reloading.  The Net tab is now blank unless I switch focus to another tab and then back to Net, then it's fine.
However if I set a BP, and then go to Net and reload, the Net tab is displayed - maybe something related to updating display to indicate BP is waiting is triggering refresh of current tab.

#2 still seems to be an issue.

[Tim Ryan]

Sorry, forgot to mention this update is based on a6 release.