Migration to 'Firefox devtools', and Firebug's status as 'no longer being developed' needs posting on Firebug landing pages

[Christopher James Francis Rodgers]

It would be very helpful if the fact that Firebug is being migrated to Firefox DevTools, and is no longer being actively developed, were prominently displayed on all of the most popular Firebug landing pages (including being posted, and 'sticky' at the top of-- if possible, the Firebug section 'Recent news'), so that users are aware of that.

That information would greatly benefit users by steering them to the relevant pages they need to immediately start using the new system. ...and would, among other things, eliminate users from continuing to post 'Firebug' issues, or following old issues, unwittingly hoping for resolution of them.

===

Suggested links to post on multiple Firebug pages:

 - Devtools Home:
"(URL unknown by me)"

- Starting point for Devtools functionality specifically comparable to Firebug
"(URL unknown by me)"

- Demonstration video on using Devtools functionality specifically comparable to Firebug
"(URL unknown by me)"

 - Migration discussion page:
"Unifying Firebug & Firefox DevTools"
https://blog.getfirebug.com/2016/06/07/unifying-firebug-firefox-devtools/

===

Thank you kindly for your time, attention, and help on this issue,
which I assume will require a great effort on your part
to accept the apparently inevitable demise of Firebug,
a tool which I had found absolutely indispensable
given my webmaster knowledge-base
limited to only HTML and CSS.

I can not thank you enough.

 - Chris

"All the best; intended."

[Sebastian Zartner]

On Tuesday, November 8, 2016 at 3:44:09 PM UTC+1, Christopher James Francis Rodgers wrote:

It would be very helpful if the fact that Firebug is being migrated to Firefox DevTools, and is no longer being actively developed, were prominently displayed on all of the most popular Firebug landing pages (including being posted, and 'sticky' at the top of-- if possible, the Firebug section 'Recent news'), so that users are aware of that.

That information would greatly benefit users by steering them to the relevant pages they need to immediately start using the new system. ...and would, among other things, eliminate users from continuing to post 'Firebug' issues, or following old issues, unwittingly hoping for resolution of them.

I totally agree with you, Christopher.
I think it is time to offer Firebug users some migration path to the DevTools on getfirebug.com. A prominent hint on the landing pages directing web developers to the DevTools would be a good start.

Suggested links to post on multiple Firebug pages:

 - Devtools Home:
"(URL unknown by me)"

That's https://developer.mozilla.org/en-US/docs/Tools.
 

- Starting point for Devtools functionality specifically comparable to Firebug
"(URL unknown by me)"

- Demonstration video on using Devtools functionality specifically comparable to Firebug
"(URL unknown by me)"

There is no such reference yet, as far as I know. Honza, Brian, Will, what about creating a page on MDN for this?

Sebastian

[Jan Odvarko]

On 17 Nov 2016, at 05:33, William Bamberg <wbam...@mozilla.com> wrote:

On Thu, Nov 10, 2016 at 4:33 AM, Sebastian Zartner <sebastia...@gmail.com> wrote:

On Tuesday, November 8, 2016 at 3:44:09 PM UTC+1, Christopher James Francis Rodgers wrote:

It would be very helpful if the fact that Firebug is being migrated to Firefox DevTools, and is no longer being actively developed, were prominently displayed on all of the most popular Firebug landing pages (including being posted, and 'sticky' at the top of-- if possible, the Firebug section 'Recent news'), so that users are aware of that.

I’ll take care of this. I think I can modify the header used on all getfirebug.com pages and append a section helping users to migrate to built-in Firefox DevTools. I’ll point to the MDN page:

https://developer.mozilla.org/en-US/docs/Tools

… and as soon as there are other pages (like suggested below) I can refer them too.

Honza

That information would greatly benefit users by steering them to the relevant pages they need to immediately start using the new system. ...and would, among other things, eliminate users from continuing to post 'Firebug' issues, or following old issues, unwittingly hoping for resolution of them.

I totally agree with you, Christopher.
I think it is time to offer Firebug users some migration path to the DevTools on getfirebug.com. A prominent hint on the landing pages directing web developers to the DevTools would be a good start.

Suggested links to post on multiple Firebug pages:

 - Devtools Home:
"(URL unknown by me)"

That's https://developer.mozilla.org/en-US/docs/Tools.
 

- Starting point for Devtools functionality specifically comparable to Firebug
"(URL unknown by me)"

- Demonstration video on using Devtools functionality specifically comparable to Firebug
"(URL unknown by me)"

There is no such reference yet, as far as I know. Honza, Brian, Will, what about creating a page on MDN for this?

Sorry for the late response, Sebastian. This does sound like a good idea. I'm not very familiar with Firebug, but it would be simple enough to do a high-level comparison (i.e. JS command line -> Web Console command line).

 

Sebastian

[Jan Honza Odvarko]

On Tuesday, November 8, 2016 at 3:44:09 PM UTC+1, Christopher James Francis Rodgers wrote:

It would be very helpful if the fact that Firebug is being migrated to Firefox DevTools, and is no longer being actively developed, were prominently displayed on all of the most popular Firebug landing pages (including being posted, and 'sticky' at the top of-- if possible, the Firebug section 'Recent news'), so that users are aware of that.

I am working on this.

Thanks for pointing this out.

Honza

[Christopher James Francis Rodgers]

Thank you for seriously considering my recommendation, and for your quick application of it. Your open-mindedness and the speed with which you incorporated the change are extremely refreshing. I wish you all the very best.

- Chris
 

[Sebastian Zartner]

On 17 November 2016 at 05:33, William Bamberg <wbam...@mozilla.com> wrote:

On Thu, Nov 10, 2016 at 4:33 AM, Sebastian Zartner <sebastia...@gmail.com> wrote:

Sorry for the late response, Sebastian. This does sound like a good idea. I'm not very familiar with Firebug, but it would be simple enough to do a high-level comparison (i.e. JS command line -> Web Console command line).

Don't worry, I'll help with that. I've started creating the page at https://developer.mozilla.org/en-US/docs/Tools/Migrating_from_Firebug. I expect that page to provide a general comparison between the panels, but also give some details about where to find specific features.

Honza, it would be great if you could also privide some entries.

On 17 November 2016 at 12:01, Jan Odvarko <odv...@gmail.com> wrote:

On 17 Nov 2016, at 05:33, William Bamberg <wbam...@mozilla.com> wrote:

On Thu, Nov 10, 2016 at 4:33 AM, Sebastian Zartner <sebastia...@gmail.com> wrote:

On Tuesday, November 8, 2016 at 3:44:09 PM UTC+1, Christopher James Francis Rodgers wrote:

It would be very helpful if the fact that Firebug is being migrated to Firefox DevTools, and is no longer being actively developed, were prominently displayed on all of the most popular Firebug landing pages (including being posted, and 'sticky' at the top of-- if possible, the Firebug section 'Recent news'), so that users are aware of that.

I’ll take care of this. I think I can modify the header used on all getfirebug.com pages and append a section helping users to migrate to built-in Firefox DevTools. I’ll point to the MDN page:

https://developer.mozilla.org/en-US/docs/Tools

Thank you for the changes!

Sebastian

[Lawrence San]

Sebastian wrote:

Don't worry, I'll help with that. I've started creating the page at https://developer.mozilla.org/en-US/docs/Tools/Migrating_from_Firebug.

​Thanks, that should be useful. Currently, near the top of the page it says:

The Web Console is the pendant to Firebug's Console panel. 

​

​Not sure what you mean by "pendant" -- in English that usually refers to a piece of jewelry, although there may be a technical meaning I'm not familiar with. Perhaps you meant "analog"? Something like "The Web Console is analogous to [or similar to, or works like] Firebug's Console panel"... ?​

[Keith Bartman]

I can understand the complexity of merging both tools... However there are basic things that I can't find how to do!  (i.e. How do you turn on persistent logging?... When you click on the console tab it's not there.... !??!?

Clearly Visible in Firebug

Clearly Absent in Dev-Tools..

I like some of the other features... especially the responsive design tool... But help I need this (I'm sure everybody who's writing any javascript does!)  Anybody?

[Jan Honza Odvarko]

Done, check out http://getfirebug.com/

The following message appended at the top:
The Firebug extension isn't being developed or maintained any longer. We invite you to use the Firefox built-in DevTools instead.

Honza

[Sebastian Zartner]

Great! Thanks Honza!

Sorry! I meant "equivalent". I'm a non-native English speaker and thought this word would also exist in English. Anyway, thank you, Will, for correcting it and the stupid "it's" vs. "its" mistakes.
I'll continue writing the points.

Sebastian

[realm]

unfortunately there is no equivalent of firebug in the dev tools nor for chrome, nothing works better for css inspection changes, uninstalled firefox and not going back, if the devs of firefox, not firebug cant fix simple things like this that have worked for years and cant break everything with code changes leaving us devs up the creek without a paddle theres no point in supporting their software, i just want my css code inspection and live changes working, thanks for all the years of firebug kudos, goodbye firefox!!! 

[Erik Krause]

Am 22.11.2016 um 19:46 schrieb realm:
> i just want my css code
> inspection and live changes working, thanks for all the years of firebug

CSS code inspection and live changes work in devtools. What is your problem?

--
Erik Krause
http://www.erik-krause.de

[Sebastian Zartner]

On Wednesday, November 23, 2016 at 12:19:57 AM UTC+1, Erik Krause wrote:

Am 22.11.2016 um 19:46 schrieb realm:
> i just want my css code
> inspection and live changes working, thanks for all the years of firebug

CSS code inspection and live changes work in devtools. What is your problem?

For clarity, the CSS related to the selected element can be viewed and manipulated via the Rules side panel and the style sheets can be edited within the Style Editor.
I assume he means HTML live preview, which is not implemented yet though mentioned in bug 991806.

Sebastian

[pd]

Mozilla management clearly are morose.

Discontinuing Firebug is the biggest knife in the back of those who have struggled through the poor management of Firefox throughout this whole decade to date. Those of us who have rejected Google and want to keep supporting the open web through loyalty to the only browser developer with a great engine and no ulterior motive to service.

Shame Mozilla, shame. One or two developers have done a great job supporting and maintaining Firebug and you just go and kill it.

[Henk van den Bor]

I have dreaded this moment for a lomng time... hoping it would not arrive. But alas, thank you guys for creating & maintaining Firebug for all these years.
Now it feels like somebody is sawing of my right hand..

I have DevFox next to FF to get familiar with the new way, but man it's nothing like Firebug :-( Every element I inspect (right click 'inspect with Firebug) first cursor jumps to body and I have to do additional clicks to get to the element I want, losing time on every action ... go tto love change grrr.

Thanks again for all the work you must have put in.


Op dinsdag 8 november 2016 15:44:09 UTC+1 schreef Christopher James Francis Rodgers:

[Erik Krause]

Am 12.12.2016 um 15:12 schrieb Henk van den Bor:
> Every element I inspect (right click 'inspect with
> Firebug) first cursor jumps to body and I have to do additional clicks to
> get to the element I want

For me it stays on body only for a split second, then jumps to the
selected element. Is this different for you?

--
Erik Krause

[Sebastian Zartner]

It depends on the computer you're using. On my cheap laptop it sometimes takes several seconds until the correct element is selected. I've filed this now as bug 1324254.

Sebastian