1267303 - (important-firebug-gaps) [meta] Most important Firebug gaps

Status: NEW

(DevTools :: General, enhancement, P3)

Description

[Bryan Clark (DevTools PM) [:clarkbw]]

Tracking the Firebug work for Q2.  Expecting feedback from the community to fill the majority of work here.

Comment 1

[Sebastian Zartner [:sebo]]

(In reply to Bryan Clark (DevTools PM) [@clarkbw] from comment #0)
> Expecting feedback from the community to fill the majority of work here.

Where's the place to provide that feedback? Here?

Sebastian

Comment 2

[Bryan Clark (DevTools PM) [:clarkbw]]

I've been asking people to provide feedback and discuss in the firebug group.
https://groups.google.com/forum/#!forum/firebug

This bug is for tracking the work we decide to take on.  Thanks!

Comment 3

[Sebastian Zartner [:sebo]]

(In reply to Bryan Clark (DevTools PM) [@clarkbw] from comment #2)
> I've been asking people to provide feedback and discuss in the firebug group.
> https://groups.google.com/forum/#!forum/firebug

Your post doesn't appear on the discussion group.
Honza, does it require moderation?

Sebastian

Comment 4

[Jan Honza Odvarko [:Honza] (always need-info? me)]

(In reply to Sebastian Zartner [:sebo] from comment #3)
> (In reply to Bryan Clark (DevTools PM) [@clarkbw] from comment #2)
> > I've been asking people to provide feedback and discuss in the firebug group.
> > https://groups.google.com/forum/#!forum/firebug
> 
> Your post doesn't appear on the discussion group.
> Honza, does it require moderation?
There is no pending message.
Honza

Comment 5

[Sebastian Zartner [:sebo]]

(In reply to Jan Honza Odvarko [:Honza] from comment #4)
> (In reply to Sebastian Zartner [:sebo] from comment #3)
> > (In reply to Bryan Clark (DevTools PM) [@clarkbw] from comment #2)
> > > I've been asking people to provide feedback and discuss in the firebug group.
> > > https://groups.google.com/forum/#!forum/firebug
> > 
> > Your post doesn't appear on the discussion group.
> > Honza, does it require moderation?
> There is no pending message.
> Honza

So, I'm now asking at https://groups.google.com/forum/#!topic/firebug/Q6eyvGt6hyI.

Sebastian

Comment 6

[Tim Nguyen :ntim]

I've added all the bugs inside the link in comment 5. Please feel free to remove any of them.

Comment 7

[Sebastian Zartner [:sebo]]

Bryan, we're almost in quarter four, so I suggest this bug should either be renamed into something like 'Most wanted Firebug features' or be closed. Please decide what to do with this bug.

Unfortunately none of the blocking bugs was closed so far, though Firebug users will very soon need to switch to the DevTools, because Firebug doesn't work with e10s enabled. Those people will miss the features and may turn their back on Firefox if they are not available, especially when other DevTools provide those features, like the DOM breakpoints, for example.
Therefore I think they deserve some higher priority.

Sebastian

Comment 8

[Bryan Clark (DevTools PM) [:clarkbw]]

I usually try to make new ones such that we have some tracking for what we did in the different quarters (not much here).  And since we don't have a Q3 bug we might as well go straight for Q4.  I will have to check on the priority for the gap bugs in Q4, Q3 shifted to mostly devtools.html projects.

Comment 9

[Sebastian Zartner [:sebo]]

I see. So, please provide some feedback once you checked the priority.
So I guess we have two options once the priority is clarified. Either we reuse this bug for Qx or close it and create a duplicate (as the blockers are still the same).

Sebastian

Comment 10

[Patrick Brosset <:pbro>]

No activity here. Let's keep this bug and rename it. The bugs it depends on are an interesting sub list of what people really need among the larger Firebug Gaps bug (bug 991806).

Comment 11

[Sebastian Zartner [:sebo]]

I've revised the list of bug 991806 comment 20 at the beginning of March in regard of the feedback I got so far (reading through all messages I got via mail, the Firebug discussion group and Stack Overflow, excluding my personal preferences). I missed to post it earlier. Sorry for that! Also, it should get updated again, though I'm currently missing the time to do so.
Here are the results (the x's indicate the number of comments asking for a feature or bugfix):

Features:
1. Advanced XPath support (bug 963933, bug 987877, bug 1032855) xxxxxxxx
2. Multi-line mode for command line (bug 1133849) xxxxx
3. Live preview of changes in markup view (bug 815464, bug 1067318) xxxxx
4. Command history list (bug 1358383) xxx
5. DOM side panel for Inspector (bug 704094) xx
6. Console log message display improvements (bug 1269730) xx
7. UX improvement for CSS auto-completion (bug 1166963 and regarding autocompletion of values) xx
8. UX improvement for leaving edit mode (bug 1067323) xx
9. Edit width and height in box model (bug 1061823) xx FIXED in 55
10. Break on DOM and XHR mutations (bug 1004678, bug 1267144) x
11. Events side panel (bug 1226640) x
12. Option to add cookies (bug 1231452) x
13. Command line auto-completion improvements (bug 1267140, bug 1270015) x
14. Rule view validity feedback as you type (bug 1227054) x
15. Tab through values in box model x FIXED in 53
16. Improved syntax highlighting (bug 1273130, bug 1281118) x
17. Copy full CSS selector path (bug 1323700) x
18. Improved debugger search x
19. Edit button in Inspector to switch to edit mode (bug 1067323) x

Bug fixes:
1. Slow UI, especially 'Inspect Element' (bug 1324254) xxx
2. 'Inspect Element with Firebug' not working xx FIXED in Firebug 2.0.19
3. CSS auto-completion (bug 1337918) xx (Mostly already FIXED by bug 1156019)
4. Source file not reopened in the debugger x
5. Scrolling via scrollbar in debugger is not possible (bug 1265807) x FIXED in 53
6. Fonts inconsistency on Linux (bug 1319079) x FIXED in 53
7. Debugger reloads when hovering a variable in source view x
8. Keep expansion of watch variables after reload x
9. Pseudo-class lock goes away when selecting other element (bug 985517) x FIXED in 52

Patrick, should we update the blocking bugs accordingly? And if so, all of these lists or only the ones with higher ranking? And should I include my personal preferences, too? (Will result in different waying.)

Sebastian

Comment 12

[Patrick Brosset <:pbro>]

(In reply to Sebastian Zartner [:sebo] from comment #11)
> Features:
> 1. Advanced XPath support (bug 963933, bug 987877, bug 1032855) xxxxxxxx
> 2. Multi-line mode for command line (bug 1133849) xxxxx
> 3. Live preview of changes in markup view (bug 815464, bug 1067318) xxxxx
> 4. Command history list (bug 1358383) xxx
> 5. DOM side panel for Inspector (bug 704094) xx
> 6. Console log message display improvements (bug 1269730) xx
> 7. UX improvement for CSS auto-completion (bug 1166963 and regarding
> autocompletion of values) xx
> 8. UX improvement for leaving edit mode (bug 1067323) xx
> 9. Edit width and height in box model (bug 1061823) xx FIXED in 55
> 10. Break on DOM and XHR mutations (bug 1004678, bug 1267144) x
> 11. Events side panel (bug 1226640) x
> 12. Option to add cookies (bug 1231452) x
> 13. Command line auto-completion improvements (bug 1267140, bug 1270015) x
> 14. Rule view validity feedback as you type (bug 1227054) x
> 15. Tab through values in box model x FIXED in 53
> 16. Improved syntax highlighting (bug 1273130, bug 1281118) x
> 17. Copy full CSS selector path (bug 1323700) x
> 18. Improved debugger search x
> 19. Edit button in Inspector to switch to edit mode (bug 1067323) x
> 
> Bug fixes:
> 1. Slow UI, especially 'Inspect Element' (bug 1324254) xxx
> 2. 'Inspect Element with Firebug' not working xx FIXED in Firebug 2.0.19
> 3. CSS auto-completion (bug 1337918) xx (Mostly already FIXED by bug 1156019)
> 4. Source file not reopened in the debugger x
> 5. Scrolling via scrollbar in debugger is not possible (bug 1265807) x FIXED
> in 53
> 6. Fonts inconsistency on Linux (bug 1319079) x FIXED in 53
> 7. Debugger reloads when hovering a variable in source view x
> 8. Keep expansion of watch variables after reload x
> 9. Pseudo-class lock goes away when selecting other element (bug 985517) x
> FIXED in 52
> 
> Patrick, should we update the blocking bugs accordingly?
Yes, I've done this. This looked like a really good list.
> And if so, all of these lists or only the ones with higher ranking?
I've included them all, except the debugger ones because they are tracked on GitHub, and except the ones that were already fixed (there was also a duplicate in your list). I haven't added bug 1273130 and bug 1281118 because I don't think they are Firebug gaps.
> And should I include my personal preferences, too? (Will result in different waying.)
Would that really change things a lot? Feel free to comment your personal preferences here, and we'll see if adjustments are needed.
But I feel like there are enough high ranked bugs here to occupy people who want to work on this.

Comment 13

[Sebastian Zartner [:sebo]]

(In reply to Patrick Brosset <:pbro> from comment #12)
> (In reply to Sebastian Zartner [:sebo] from comment #11)
> > Features:
> > 1. Advanced XPath support (bug 963933, bug 987877, bug 1032855) xxxxxxxx
> > 2. Multi-line mode for command line (bug 1133849) xxxxx
> > 3. Live preview of changes in markup view (bug 815464, bug 1067318) xxxxx
> > 4. Command history list (bug 1358383) xxx
> > 5. DOM side panel for Inspector (bug 704094) xx
> > 6. Console log message display improvements (bug 1269730) xx
> > 7. UX improvement for CSS auto-completion (bug 1166963 and regarding
> > autocompletion of values) xx
> > 8. UX improvement for leaving edit mode (bug 1067323) xx
> > 9. Edit width and height in box model (bug 1061823) xx FIXED in 55
> > 10. Break on DOM and XHR mutations (bug 1004678, bug 1267144) x
> > 11. Events side panel (bug 1226640) x
> > 12. Option to add cookies (bug 1231452) x
> > 13. Command line auto-completion improvements (bug 1267140, bug 1270015) x
> > 14. Rule view validity feedback as you type (bug 1227054) x
> > 15. Tab through values in box model x FIXED in 53
> > 16. Improved syntax highlighting (bug 1273130, bug 1281118) x
> > 17. Copy full CSS selector path (bug 1323700) x
> > 18. Improved debugger search x
> > 19. Edit button in Inspector to switch to edit mode (bug 1067323) x
> > 
> > Bug fixes:
> > 1. Slow UI, especially 'Inspect Element' (bug 1324254) xxx
> > 2. 'Inspect Element with Firebug' not working xx FIXED in Firebug 2.0.19
> > 3. CSS auto-completion (bug 1337918) xx (Mostly already FIXED by bug 1156019)
> > 4. Source file not reopened in the debugger x
> > 5. Scrolling via scrollbar in debugger is not possible (bug 1265807) x FIXED
> > in 53
> > 6. Fonts inconsistency on Linux (bug 1319079) x FIXED in 53
> > 7. Debugger reloads when hovering a variable in source view x
> > 8. Keep expansion of watch variables after reload x
> > 9. Pseudo-class lock goes away when selecting other element (bug 985517) x
> > FIXED in 52
> > 
> > Patrick, should we update the blocking bugs accordingly?
> Yes, I've done this. This looked like a really good list.

Great, thanks a lot!

> > And if so, all of these lists or only the ones with higher ranking?
> I've included them all, except the debugger ones because they are tracked on
> GitHub, and except the ones that were already fixed

Good.

> (there was also a duplicate in your list).

Oops, sorry! Obviously missed that when summarizing the feedback.

> I haven't added bug 1273130 and bug 1281118 because I don't think they are Firebug gaps.

Just copied them over from the Firebug forum[1], but you're right, they are unrelated to Firebug.

> > And should I include my personal preferences, too? (Will result in different waying.)
> Would that really change things a lot? Feel free to comment your personal
> preferences here, and we'll see if adjustments are needed.
> But I feel like there are enough high ranked bugs here to occupy people who
> want to work on this.

I agree that these are already enough bugs to fix and I think my most important bugs are already covered by this list. So, my vote doesn't really change much.
I just hope that those bugs really get some priority and get tackled soon.

Sebastian

[1] https://groups.google.com/d/msg/firebug/Q6eyvGt6hyI/7h8WCpM1BgAJ