Firebug 3 : Issues

[KOLANICH]

Let's collect FB3 issues here.
I'll start
1 There is no FB statusbar button anymore.
2 Console doesn't work: I enter code, hit enter and it is echoed but not executed.
I'm using  FF 3.0.2 (Mozilla/5.0 (Windows NT 6.3; rv:33.0) Gecko/20100101 Firefox/33.0 ID:20141027150301 CSet: 7dc4a9d1b3e6)

[Sebastian Zartner]

Firebug 3.0 alpha 2 is just compatible with Firefox 35.0a2+, not with the current stable 33.0.3.

Sebastian

[Jan Honza Odvarko]

On Sunday, November 9, 2014 6:27:49 PM UTC+1, KOLANICH wrote:

Let's collect FB3 issues here.
I'll start
1 There is no FB statusbar button anymore.

The status bar button is not there for a long time already
(not even Firefox status bar itself)

Honza
 

[Jan Honza Odvarko]

On Sunday, November 9, 2014 6:35:17 PM UTC+1, KOLANICH wrote:Let's collect issues here
2 There is no DOM tab

There is main DOM panel and we are planning DOM side panel for the
Console and Inspector panel. Is there any other place you have in mind?

Honza

[KOLANICH]

Firebug 3.0 alpha 2 is just compatible with Firefox 35.0a2+, not with the current stable 33.0.3.

Ok, tested on latest nightly. Have found the button and DOM tab.
But there are still some issues. The main is that there is no search in DOM tab and that console's code box is not multiline.
Also I think that native devtools look is better than FB one (especially the dark one, which stays unmodified).
Also some ideas.
Since FB 3 is not compatible with FF 33 you shouldn't show popup with suggestion to migrate. Although, it works pretty well, though a lot of functionality got missing. Maybe it'd be better if you make it compatible with the next major release in order to get more feedback?

[Jan Honza Odvarko]

On Monday, November 10, 2014 2:23:48 PM UTC+1, KOLANICH wrote:

Firebug 3.0 alpha 2 is just compatible with Firefox 35.0a2+, not with the current stable 33.0.3.

Ok, tested on latest nightly. Have found the button and DOM tab.
But there are still some issues. The main is that there is no search in DOM tab

Yep, this is missing. Can you please file a bug in our issue list?
https://github.com/firebug/firebug.next/issues
(this should be a blocker)
Thanks!
 

 and that console's code box is not multiline.

Did you try to open a side panel in the Console panel and use the Command Editor?

 

Also I think that native devtools look is better than FB one (especially the dark one, which stays unmodified).

Also some ideas.
Since FB 3 is not compatible with FF 33 you shouldn't show popup with suggestion to migrate. Although, it works pretty well, though a lot of functionality got missing. Maybe it'd be better if you make it compatible with the next major release in order to get more feedback?

The upgrade to FB 3 is only offered in Aurora (35.0a2) channel and e10s enabled browser.

Honza
 

[Sebastian Zartner]

On Monday, November 10, 2014 3:06:37 PM UTC+1, Jan Honza Odvarko wrote:

 and that console's code box is not multiline.

Did you try to open a side panel in the Console panel and use the Command Editor?

To be more precise, to enable the Command Editor you need to click the little arrow at the top right within the panel toolbar. Furthermore note that you can create line breaks within the command line by pressing Shift+Enter.

Also I think that native devtools look is better than FB one (especially the dark one, which stays unmodified).

Also some ideas.
Since FB 3 is not compatible with FF 33 you shouldn't show popup with suggestion to migrate. Although, it works pretty well, though a lot of functionality got missing. Maybe it'd be better if you make it compatible with the next major release in order to get more feedback?

The upgrade to FB 3 is only offered in Aurora (35.0a2) channel and e10s enabled browser.

If people manually switch browser.tabs.remote and browser.tabs.remote.autostart, they'll see that popup even in Firefox 33 and 34. That may be confusing, though there may not be that many people having these preferences set in these browser versions.

Sebastian

[Jan Honza Odvarko]

On Monday, November 10, 2014 3:13:12 PM UTC+1, Sebastian Zartner wrote:

If people manually switch browser.tabs.remote and browser.tabs.remote.autostart, they'll see that popup even in Firefox 33 and 34. That may be confusing, though there may not be that many people having these preferences set in these browser versions.

If e10s is enabled FB2 doesn't work, so upgrade or switching
e10s off is the way to go (which is exactly what is offered to
the user).

Honza

[Sebastian Zartner]

Though upgrading to FB3 doesn't work either for Firefox 33 and 34 users.

Sebastian

[KOLANICH]

Did you try to open a side panel in the Console panel and use the Command Editor?

Yes. Opened side panel ... which was like "DOM" tab.

If people manually switch browser.tabs.remote and browser.tabs.remote.autostart

No, I have 'em disabled.

[Sebastian Zartner]

Please deactivate other extensions and check if you can open Firebug then. If it works, reenable one by one to find the conflicting one.
If Firebug still can't be opened even with all other extensions disabled, then it's probably some preference.

Sebastian

[KOLANICH]

It can be opened (and it is opened well), but it showed this message for my browser though it shouldn't.