Firebug/WeeklyUpdates/2014-05-20: Difference between revisions
< Firebug | WeeklyUpdates
Jump to navigation
Jump to search
Sebastianz (talk | contribs) (Improved formatting and added one more link) |
Sebastianz (talk | contribs) m (Clarified note to issue 1420) |
||
| Line 23: | Line 23: | ||
** We want to use a class | ** We want to use a class | ||
** We want to display it to the user (+ it should be editable) | ** We want to display it to the user (+ it should be editable) | ||
** The context should probably display both actions (<kbd>h</kbd> and <kbd>H</kbd>) | ** The context menu should probably display both actions (<kbd>h</kbd> and <kbd>H</kbd>) | ||
* [http://code.google.com/p/fbug/issues/detail?id=7445 Issue 7445]: Check extensions for breakage in combination with Firebug 2.0 | * [http://code.google.com/p/fbug/issues/detail?id=7445 Issue 7445]: Check extensions for breakage in combination with Firebug 2.0 | ||
Latest revision as of 06:56, 25 August 2014
Jan Odvarko, Sebastian Zartner, Florent Fayolle, Joe Walker, Belakhdar Abdeldjalil, Simon Lindholm
Firebug Releases
- Firebug 2 beta 7
- Let's see how much we can do till Friday
Issues
- Issue 7442: Wappalyzer extension breaks Firebug's Console logging
- Everyone: help the platform people if you can
- The problem should be fixed in 2.0
- We should test Firefox beta
- Issue 7022: Add a button for enabling Responsive Design View
- Where should we put the button?
- We agree that the main toolbar is too high visibility
- Sebastian: Having it in the HTML or CSS is weird (not related)
- Let's discuss again next time
- Issue 1420: Add an option to hide an element
- Sebastian's comment about options: https://code.google.com/p/fbug/issues/detail?id=7155#c13
- We want h for
visibility:visible - We want H for
display:none - We want to use a class
- We want to display it to the user (+ it should be editable)
- The context menu should probably display both actions (h and H)
- Issue 7445: Check extensions for breakage in combination with Firebug 2.0
- https://docs.google.com/spreadsheet/ccc?key=0ArzNE_OHjXkQdFMySmRxV2xOYjNJTDBZU1BQSk9aS3c&usp=sharing#gid=0
- Honza: tested bunch of extensions
- Others should start, too
- Issue 5765: Integrate source maps for JavaScript
- Farshid: What is the status?
- Issue 6557: Font previews don't work
- Florent: working on this, make progress this week
Firebug and Future Strategies
- Honza: https://docs.google.com/document/d/1Dr0hFqA6CP9O-Xug5DOYZrrxzsRzbc_xD0mSATn7XcE/edit#
- Florent: https://docs.google.com/document/d/1ALR7awu8nOJFQKFS6DLlMkXBOdjWI8kkf1Agl_QoYlc/edit
- Djalil: https://docs.google.com/document/d/1wlEJgKTuza5DeLayjZ-aBpJ4kQrAGFTnnfMNSUJkZNs/edit#
- Sebastian: https://docs.google.com/document/d/1Vmf_Eqb0fdfPkzn73zPxbajzb32eq8Q8jBitsWgsSFA/edit?usp=sharing
- Farshid: https://groups.google.com/d/msg/firebug-working-group/EDjhFbSuCwQ/cwHzomKOdKAJ
Suggested paths:
- Firebug 2.1 with Simon's e10s workaround
- Firebug 3.0 built on top of devtools
- Joe: suggest list of features for Firebug 3 for the next meeting.