[firebug] Re: firebug html tab is empty after new firefox upadated

not working properly. the > HTML tab is empty but other tab is working good. maybe you can refere to > the attachment. *"Inspect Elemnt With FireBug"* > > > Thanks > Vikram > > On Friday, 20 October 2017 17:53:04 UTC+5:30, Sebastian Zartner wrote: >> >

[firebug] Re: Firebug not comfortable Ubuntu Firefox 56.0 (64-bit)

Firebug's development is officially discontinued. Firebug users are encouraged to use the Firefox built-in developer tools instead. See https://hacks.mozilla.org/2016/12/firebug-lives-on-in-firefox-devtools/ for more info. Sebastian On Monday, October 16, 2017 at 1:42:28 PM UTC+2, vithul nk

[firebug] Re: firebug html tab is empty after new firefox upadated

Just to be clear, staying with an outdated version of a software is normally not recommendable, because you miss security and other bug fixes and also new features. Firebug users are advised to try out the Firefox DevTools. And if you don't like them or miss a feature Firebug had, you should

Re: [firebug] firebug....is a bug?

Just to be clear, the development and maintainence of Firebug stopped several years ago. Mozilla introduced a new architecture for extensions called WebExtensions, which will be the only supported extension system once Firefox 57 is released. That means, Firebug as well as all other extensions

[firebug] Re: Firebug stopped recognizing the "! important"?

Note that Firebug is discontinued and unmaintained for several years now. Firebug users are advised to use the Firefox built-in DevTools. Those support the !important keyword (note: *without* space) within their Rules panel. Sebastian On Wednesday, October 4, 2017 at 2:19:06 PM UTC+2, Carlos

[firebug] Re: Firebug is not working in firefox 55.0.2 and below all versions.

Hi! You may have missed it, though Firebug is officially discontinued for several years now. Users are encouraged to use the Firefox built-in DevTools instead. Sebastian On Wednesday, October 4, 2017 at 2:17:04 PM UTC+2, ke...@cactusstudio.com

[firebug] Re: firbug is not install on my laptop

Firebug is officially discontinued . You should use the Firefox DevTools instead. Sebastian On Friday, September 1, 2017 at 2:22:20 PM UTC+2, naseemab...@gmail.com

Re: [firebug] Re: Firebug not found when I install Firefox 55.0.2

On Monday, August 21, 2017 at 7:05:04 PM UTC+2, Michael_google gmail_Gersten wrote: > > > On 2017-08-20, at 4:19 AM, Erik Krause > wrote: > > > Am 20.08.2017 um 03:32 schrieb Michael: > NB: Firefox developer tools is not an acceptable substitute. Far > too often,

Re: [firebug] Firebug not found when I install Firefox 55.0.2

On Saturday, August 19, 2017 at 10:17:06 PM UTC+2, Michael_google gmail_Gersten wrote: > > Firebug is no longer compatible with Firefox. > > More specifically, Firebug is not compatible with multiprocess firefox. If > you need it, you can use Firefox ESR, which has multiprocess disabled by >

Re: [firebug] "ADD TO CHROME" button not working

On Monday, August 14, 2017 at 6:45:55 PM UTC+2, dmccunney wrote: > > On Mon, Aug 14, 2017 at 1:09 AM, Oyee BSnu > wrote: > > > > I am trying to install this extension but not able to! > > How do I get to install this firebug? > > Any help Please! > > I don't believe you

[firebug] Re: Grid display toggle

Hi Melisa, the grid overlay is a feature of the Firefox built-in DevTools and is not part of Firebug, which is discontinued . What you describe sounds like a bug to me, though unfortunately I cannot reproduce it. I

[firebug] Re: Firefox Developer Tools with JAWS and NVDA screen readers since Firebug is no longer developed?

On Saturday, July 29, 2017 at 5:45:43 PM UTC+2, Walker, Michael E wrote: > > Hi, I have been searching for days for information on how to use the > Firefox Developer Tools with the latest JAWS for Windows by Freedom > Scientific screen reader, and NVDA by NV Access. I also posted this >

Re: [firebug] Re: Firebug is back in Firefox 53.0.3!?

On another PC I can reproduce this issue. Reading through https://wiki.mozilla.org/Electrolysis I saw that some add-ons (like Firebug) may deactivate the multiprocess feature automatically. That page says that you can force-enable multiprocess Firefox by adding the preference

[firebug] Re: Firebug is back in Firefox 53.0.3!?

t; Thank you again and for providing the useful links. > > L > > On Wednesday, June 7, 2017 at 10:00:36 PM UTC+1, Sebastian Zartner wrote: >> >> That you see *Inspect Element with Firebug* again means that the >> preference browser.tabs.remote.autostart.2 is

[firebug] Re: Firebug is back in Firefox 53.0.3!?

That you see *Inspect Element with Firebug* again means that the preference browser.tabs.remote.autostart.2 is set to false for you. See my related answer on Stack Overflow . As far as I know, this doesn't happen by itself, so it might be that it

[firebug] Re: Firebug 2.0.18 deactivated

I want to note again that Firebug doesn't work anymore once multi-process Firefox is enabled . When it's enabled, the Firebug button will open the Firefox DevTools (with Firebug theme) instead of Firebug. Furthermore,

[firebug] Re: Firefox ESR, Firebug support

ormation. > I just installed FF ESR 52.1.4 and befor with FF ESR 45.x it was working > very nice. > > Does anybody has any information what's the reason or maybe if the FB team > is already working on it? > > Thanks, Michael > > Am Freitag, 10. März 2017 21:32:32

[firebug] Re: Removing Firebug

Are you sure that what you're seeing is Firebug and not the Firefox DevTools (with Firebug theme)? Can you post a screenshot? Anyway, to make sure Firebug is removed: 1. Go to your profile folder via the Firefox menu > *?* > *Troubleshooting

[firebug] Re: Firebug 2+ Add-on Doesn't Show Error Info

On Sunday, May 14, 2017 at 7:28:40 PM UTC+2, Erik Krause wrote: > > > The > > built-in Firefox web developer tools sucks. I hope somebody builds > another > > web developer tool similar to the classic Firebug. > > That won't likely happen, since there wasn't even enough manpower to > migrate

[firebug] Re: Firebug 2+ Add-on Doesn't Show Error Info

12:23:51 PM UTC+2, Sebastian Zartner wrote: > > I have already answered on your Stack Overflow question yesterday. Please > see my answer: > > http://stackoverflow.com/a/43903504/432681 > > Sebastian > > On Thursday, May 11, 2017 at 8:45:13 AM UTC+2, Meengla Yip wrote: &

[firebug] Re: Firebug 2+ Add-on Doesn't Show Error Info

I have already answered on your Stack Overflow question yesterday. Please see my answer: http://stackoverflow.com/a/43903504/432681 Sebastian On Thursday, May 11, 2017 at 8:45:13 AM UTC+2, Meengla Yip wrote: > > Hi, > Please see this cross post at Stack Overflow--no one is responding there: >

[firebug] Re: Firebug console incredibly slow

You have just excavated a five years old thread. Note that Firebug is officially discontinued. Read more about that in the Mozilla Hacks blog . People are recommended to use the Firefox DevTools instead. Sebastian On

[firebug] Re: When the Firefox e10 is enabled, the HTML menu in Firebug disappears.

uld definitely improve. Meanwhile, I >> will stay with Firebug and Devtools will try out some other version. >> >> Dne čtvrtek 4. května 2017 13:24:45 UTC+2 Sebastian Zartner napsal(a): >>> >>> Within the Firefox DevTools you have similar options to edit the HT

[firebug] Re: When the Firefox e10 is enabled, the HTML menu in Firebug disappears.

ry easy to > translate. Then I copy the HTML code and return it back to the customer. With > Firefox Devtools, I have no option to edit the HTML code to make it look > the same as Firebug. The only solution for me is to turn off the E10s yet. > :( > Is support planned? > > Dne

[firebug] Re: When the Firefox e10 is enabled, the HTML menu in Firebug disappears.

When e10s is enabled, the Firefox DevTools are opened instead of Firebug, because Firebug does not work with e10s . Those tools have the HTML ancestor path is at the bottom of the panel. Sebastian On Wednesday, May 3,

[firebug] Re: Enable Javascript Debug

That the Script panel is broken is a known issue caused by a change in the Firefox internal APIs. Though, as you correctly noted, Firebug's development and maintenance is discontinued, so this won't be fixed anymore. If you have difficulties using

[firebug] Re: Partial fix for Console colors

On Monday, April 24, 2017 at 1:32:28 AM UTC+2, San wrote: > > I've written here a couple of times before about the colors in my DevTools > Console displaying weirdly -- ordinary log text in orange or red, and error > text in black. Apparently a lot of people are not seeing this problem; > maybe

[firebug] Re: Command Editor. Can't find the button

Note that what you're seeing actually isn't Firebug but the Firefox Developer Tools (with a Firebug theme to let them look like Firebug). You got switched to them automatically, because Firebug doesn't work in multi-process Firefox

[firebug] Re: new firebug is extremely awful

tly have regarding the Firefox DevTools <http://stackoverflow.com/a/41890636/432681>. Sebastian PS: Please refrain from hateful speech! Complaining about the DevTools doesn't bring back Firebug and the DevTools team doesn't follow this thread, anyway, so it's wasted time. On Thursd

Re: [firebug] browser question

On Monday, April 10, 2017 at 11:16:01 PM UTC+2, dmccunney wrote: > > On Mon, Apr 10, 2017 at 4:11 PM, 'Sydney Anderson' via Firebug > wrote: > > Is there a browser that works best with Firebug Lite? The website > mentioned > > Firefox, is that the best one to use

[firebug] Re: CSS?

If the CSS is not applied to the page, this means the style sheets could not be loaded, e.g. due to a network issue like a wrong URL. Though if the CSS is applied to the page, this is probably a bug in Firebug. Having said that, as Dennis already stated in the other thread

Re: [firebug] Re: new firebug is extremely awful

On Monday, April 3, 2017 at 3:58:09 PM UTC+2, fred.h...@gmail.com wrote: > > It is definitely a huge burden to extension developers, because in most >> cases they have to rework huge parts of their extensions. By the way, I'm >> also one of those developers, and I am also sad about that

Re: [firebug] Re: Firefox devtools sidebar UX issue

On 3 April 2017 at 21:54, Erik Krause wrote: > Am 01.04.2017 um 10:35 schrieb fred.heuv...@gmail.com: > >> I was afraid to click 'inspect element' for two weeks because I did >> not know how to remove it. >> > > You can remove it any time by pressing F12. However, I agree

[firebug] Re: How to reset firebug options in an external new firebug window in chrome?

Note that Firebug Lite is not maintained for several years now, so you should rather use the Chrome DevTools or remotely debug Chrome via the Firefox DevTools

Re: [firebug] Re: new firebug is extremely awful

On Thursday, March 30, 2017 at 8:06:05 AM UTC+2, San wrote: > > One of the linked pages says that Firefox 47 was the last version fully > compatible with Firebug. It links to a sourceforge page with "portable" > Firefox 47 -- but all the downloadables appear to be .exe files, so useless > to me

Re: [firebug] Re: new firebug is extremely awful

On Wednesday, March 29, 2017 at 6:14:19 PM UTC+2, San wrote: > > On Wed, Mar 29, 2017 at 6:56 AM, M Gol > wrote: > >> ... i don't get it, up until a few days ago firebug was awesome, now >> automatically it's crap because it's discontinued? Can I still use the old >>

Re: [firebug] Re: Firebug 2.0.19

See my answer on Stack Overflow . Sebastian On 29 March 2017 at 02:16, M Gol wrote: > Is there any way to go back to the old firebug? > > On Wednesday, March 1, 2017 at

Re: [firebug] Re: Firebug 2.0.19

On Thursday, March 16, 2017 at 3:27:38 PM UTC+1, Ole Laursen wrote: > > Hi! > > I just discovered today that my Firebug console is broken. > I've posted a related answer on Stack Overflow . > I tried the built-in one from a latest nightly build, but

[firebug] Re: Firebug deprecation: what to do next

On Thursday, March 16, 2017 at 2:06:23 PM UTC+1, Álvaro G. Vicario wrote: > > El martes, 14 de marzo de 2017, 21:30:01 (UTC+1), Erik Krause escribió: >> >> Firebug.next is integrated in the Devtools, which are shipped with >> Firefox. > > > Thank you. I already found the "Firebug" theme in the

Re: [firebug] Re: Firebug 2.0.19

On Thursday, March 9, 2017 at 8:12:41 AM UTC+1, San wrote: > > AFAIK, Firebug's minimize button was more than simply an alternative to > f12. Firebug was capable of running in the background even when it had no > windows showing > Pressing F12 while Firebug was open minimized it (letting

[firebug] Re: Firefox ESR, Firebug support

With ESR 52.0, which was released three days ago, Firebug's Console and Script panel stop working. Sebastian On Friday, March 10, 2017 at 3:35:42 PM UTC+1, alecwho wrote: > > Can you please tell me how long will firebug work with Firefox ESR (the > console and script tabs, in firebug as it

[firebug] Re: Does the development of Firebug.next is stopped ?

n On Monday, March 6, 2017 at 11:48:13 AM UTC+1, Pramod Y wrote: > > Yes Only Look and Feel [Theem]. But We need real tool features such as > Debugger Activate or inactivate. > > On Friday, 3 March 2017 02:21:55 UTC+5:30, Sebastian Zartner wrote: >> >> Yes, as th

[firebug] Re: Firebug 2.0.19

If you don't see the minimize button, it means you got switched to the Firefox DevTools automatically. See the Mozilla Hacks blog for more info why. A minimize button is requested for the DevTools in bug 1178218

Re: [firebug] Re: PHP server messages

Please forgive me my forgetfullness and ignorance, Lawrence and Erik! Indeed, you provide good alternatives for Chrome Logger. After all, server-side logging works through HTTP headers, so if somebody wants to, he or she can implement their own tool to create those headers, or use the simple

[firebug] Re: PHP server messages

Yes, Chrome Logger is what you need to use. If you have issues integrating it into your PHP code, you should open an issue for Chrome Logger . If you integrated it into your PHP code, but the output is not shown or incorrectly shown in the

[firebug] Re: Does the development of Firebug.next is stopped ?

Yes, as the homepage says , Firebug is officially discontinued. The Firebug.next extension got integrated into the DevTools as a theme for them. See also the related Mozilla Hacks blog post .

Re: [firebug] Firebug 2.0.19

On Thursday, March 2, 2017 at 3:18:07 PM UTC+1, Segei wrote: > > Want to absolutely second the console.log sentiment! Can't wrap my head > around how this absolutely indispensable feature not working has not > resonated at all (googling it brings up nothing). That and the fact that > the Script

[firebug] Re: "Firebug vs. DevTools" question

It's status is ASSIGNED, which means it is being worked on. Bugs are resolved when their status is FIXED. Sebastian On Thursday, March 2, 2017 at 1:28:16 PM UTC+1, Alexx Lebedinsky wrote: > > here that bug , but > I don't understand resolved

Re: [firebug] Re: "Firebug vs. DevTools" question

Live update doesn't work yet. See bug 815464 and bug 1067318 . Sebastian On 1 March 2017 at 20:55, Erik Krause wrote: > Am 01.03.2017 um 17:08 schrieb Alexx

Re: [firebug] Firebug 2.0.19

It's actually not about fixing Firebug but about making the transition to the DevTools easier. That the context menu inspection has been broken was the most mentioned issue and easy to fix. Fixing issues like the console or the debugger would require much more effort and therefore isn't worth

Re: [firebug] firebug problem in console tab

Hi there, Please see my answer to this on Stack Overflow: http://stackoverflow.com/a/42515910/432681 Sebastian Am 01.03.2017 12:58 schrieb "Morteza Fard Saffari" : hey guys. i have Firefox version 51.0.1 and my Firebug is latest version. i have a problem and i think

[firebug] Re: new firebug is extremely awful

As I wrote earlier, Firebug is officially discontinued. You got switched to the Firefox DevTools. Please read the comments above. Sebastian On Saturday, February 18, 2017 at 5:45:28 PM UTC+1, George wrote: > > Firebug was amazing but became so bad > that i cant use it anymore. > I hope that the

[firebug] Re: New firebug is not good

On Saturday, February 18, 2017 at 9:15:50 PM UTC+1, Erik Krause wrote: > > Am 17.02.2017 um 17:45 schrieb George: > > I was a very big fan of the old simple firebug till you > > released the new version that is totally different > Just to be clear, there is no "new version" of Firebug. You got

Re: [firebug] New firebug is too bad

On Saturday, February 18, 2017 at 6:26:48 PM UTC+1, dmccunney wrote: > > On Sat, Feb 18, 2017 at 11:44 AM, Himansu Patel > wrote: > > I want old version of firebug. > > Please remove restrictions for install old version in new Firefox. > > > > I hate new version and many

Re: [firebug] Re: Firebug console is blank; DevTools console text is orange

me what was the last version of Firefox that > completely supported Firebug without breaking anything? I assume I can dig > up that older FF either from some online archives or my own backup archives. > Thanks much as always! > > Lawrence > > > > On Mon, Feb 13, 2017 at 3:3

Re: [firebug] xPath 2.0 functions in FirePath

Hi Alvaro, I have several notes on this: - FirePath bases its functionality on the Firefox APIs. I.e. the XPath features need to be implemented in Firefox in order to work. And the min(), max(), avg() are obviously not (yet) implemented in Firefox. You can always try out whether a XPath

[firebug] Re: Firebug 2.0.18 'Inspect element with firebug' broken?

Please use the *Inspect Element* option instead. Sebastian On Thursday, February 9, 2017 at 11:01:39 PM UTC+1, Sebastian Zartner wrote: > > See http://stackoverflow.com/a/40910225/432681 and > http://stackoverflow.com/a/41890636/432681 for how to get Firebug back > (tem

Re: [firebug] Re: Inspect Element Broken

the *Inspect Element* option instead! Sebastian On Sunday, January 8, 2017 at 5:02:51 PM UTC+1, Sebastian Zartner wrote: > > On Friday, January 6, 2017 at 12:38:28 AM UTC+1, San wrote: >> >> A few other differences in how the Inspect feature works: >> >> In Fi

[firebug] Re: Firebug console is blank; DevTools console text is orange

Hi Lawrence, On Monday, February 13, 2017 at 8:39:43 PM UTC+1, San wrote: > > I've been trying to get used to the DevTools, and there are parts of it I > even like, but I can't get used to its console. As I've written before, > ordinary log text appears in orange, and error text in black, the

[firebug] Re: new firebug is extremely awful

Please note that this thread is *not* reaching the DevTools team. I am trying to forward specific requests about missing features and UX improvements, but if you want to reach the DevTools team directly, please do that via their official communication channels

Re: [firebug] Scroll CSS properties using Down keyboard key (like in firebug)

Hi Ludovic, somebody else asked me the same question yesterday. What a coincidence! :-) You're right that Firebug's UI was better in this point. For this purpose I have now filed bug 1338645 . Note that if you find such differences between

[firebug] Re: Firebug 2.0.18 'Inspect element with firebug' broken?

; On Tuesday, February 7, 2017 at 2:52:29 PM UTC-5, Sebastian Zartner wrote: >> >> See bug 1324254 <https://bugzilla.mozilla.org/show_bug.cgi?id=1324254>. >> >> Sebastian >> >> On Tuesday, February 7, 2017 at 2:49:08 PM UTC+1, Erik Krause wrote: >>> >

[firebug] Re: new firebug is extremely awful

The element picker does work, though due to a bug it first selects the element before selecting the actually inspected element. See bug 1324254 . If it really doesn't work for you at all, please file a new bug and post the link to it here

[firebug] Re: Don't like the new integration

The team behind Firebug has split up and with e10s implemented and WebExtensions enforcement on the horizon, Firebug basically would need to be recreated from scratch (if it's even possible to create it as WebExtension). So, I think the $100 are better invested in pushing the Firefox DevTools.

[firebug] Re: Firebug 2.0.18 'Inspect element with firebug' broken?

See bug 1324254 . Sebastian On Tuesday, February 7, 2017 at 2:49:08 PM UTC+1, Erik Krause wrote: > > Am 07.02.2017 um 11:43 schrieb Michael Chaplin: > > If I try to right click an element to use 'Inspect element with firebug' > it > >

[firebug] Re: Console.log not showing under console.

Please read my previous posts! Sebastian On Monday, February 6, 2017 at 8:57:11 AM UTC+1, Khantri Iswahyudi wrote: > > > > I have the same issue.. > > Console isn't

[firebug] Re: Suggestions for Firebug gaps to be closed by the DevTools

story >>menu. Yes, you can up-arrow through your history, but you don't see what >>that history actually is until you get there. >>4. Remembering the source file you had open the last time you opened >>the debug window on this page. >>5. Inspector Box Model ta

[firebug] Re: Where is "open in a new tab" tool?

ozilla.org/2016/12/firebug-lives-on-in-firefox-devtools/>. Sebastian On Friday, February 3, 2017 at 2:28:37 PM UTC+1, Sebastian Zartner wrote: > > Please see bug 1220758 > <https://bugzilla.mozilla.org/show_bug.cgi?id=1220758>. > > Sebastian > > On Friday, February 3,

[firebug] Re: Where is "open in a new tab" tool?

Please see bug 1220758 . Sebastian On Friday, February 3, 2017 at 12:34:22 PM UTC+1, Александр Анисимов wrote: > > After my firebug extension theme updated, there is no "open in a new tab" > that had been available on "console" tab. > This

Re: [firebug] Re: DOM Exploration - explore html element in DOM Panel - Show your own DOM additions

shooting process and for taking the time to help me in the disorientation of transition. FireBug will be sorely missed. Michael On Thursday, 2 February 2017 14:39:05 UTC, Sebastian Zartner wrote: > > Are there errors in the Browser Console (Ctrl+Shift+J) after you clicked > that opti

[firebug] Re: DOM Exploration - explore html element in DOM Panel - Show your own DOM additions

some reason > > > Michael > > > On Thursday, 2 February 2017 11:05:14 UTC, Sebastian Zartner wrote: >> >> On Wednesday, February 1, 2017 at 8:06:38 PM UTC+1, michael simpson wrote: >>> >>> When I'm inspecting an html element the right click contex

Re: [firebug] Re: Suggestions for Firebug gaps to be closed by the DevTools

Sorry my bad english. > It's actually quite good! :-) Sebastian > Em 2 de fev de 2017 9:15 AM, "Sebastian Zartner" <sebastia...@gmail.com > > escreveu: > > On Wednesday, February 1, 2017 at 1:45:20 PM UTC+1, Nick Odaemus wrote: >> >> Will there b

[firebug] Re: Suggestions for Firebug gaps to be closed by the DevTools

On Wednesday, February 1, 2017 at 1:45:20 PM UTC+1, Nick Odaemus wrote: > > Will there be any Xpath utilities, such as what FirePath covered? > Please see my answer in another thread . On Wednesday, February 1, 2017 at 8:06:37 PM

[firebug] Re: DOM Exploration - explore html element in DOM Panel - Show your own DOM additions

On Wednesday, February 1, 2017 at 8:06:38 PM UTC+1, michael simpson wrote: > > When I'm inspecting an html element the right click context menu gives me > an option to "Show in DOM Panel" but nothing happens when I click this and > the DOM panel hasn't changed to show the properties of the

[firebug] Re: Console.log not showing under console.

Firebug is unmaintained. If you're facing issues with the DevTools when working with complex SVGs, you should file a bug report about that . Sebastian On Wednesday, February 1, 2017 at 1:45:14 PM UTC+1, Dan M wrote: > > > Same here.

[firebug] Re: Where are useful features of firebug?

Again, what you are seeing are the Firefox DevTools. There is no new version of Firebug. Sure, the DevTools UI is not as good as Firebug's and they are missing several things Firebug had . But whining about the situation doesn't help anyone.

Re: [firebug] console not showing

Please see my answer on Stack Overflow . Sebastian On 31 January 2017 at 13:22, Pons Venkat wrote: > firebug - console text not showing. From program console.log query is not > executed in firebug . My firebug version is 2.0.18

[firebug] Re: I can't change block width and height in new "block model" block on Computed panel

This is filed as bug 1061823 . As a workaround until that bug is fixed, you can add width and height properties to the inspected element and press (Shift) Up/Down on your keyboard to get the same effect. Sebastian On Tuesday, January 31,

Re: [firebug] Re: Firebug 2.0.18 deactivated

alidate the Xpath with firebug 2.0.18 > deactivated > On Saturday, November 19, 2016 at 5:46:20 AM UTC+5:30, Sebastian Zartner > wrote: >> >> The reason for this is described in the Firebug blog: >> >> https://blog.getfirebug.com/2016/06/07/unifying-firebug-firefox-devt

[firebug] Re: Search CSS class in all CSS file not possible with Dev Tools ?

The CSS rules of the selected HTML element are shown within the Rules side panel . And by clicking on the source link besides a rule you switch to the Style Editor

[firebug] Re: Don't like the new integration

On Tuesday, January 31, 2017 at 9:06:52 AM UTC+1, Arun Kumar wrote: > > Is there any way to revert back to old firebug without reinstalling > firefox to old version? I simply dont like how firefox's developer tools > works and its lot buggy. That's the main reason I was using firebug. > Yes,

Re: [firebug] right click inspect, shows the html portion of that section

Also, please note that a related bug in Firefox 53 <https://bugzilla.mozilla.org/show_bug.cgi?id=1326753> got fixed recently. Sebastian On 30 January 2017 at 23:11, Sebastian Zartner <sebastianzart...@gmail.com> wrote: > As far as I can tell, the inspector is working bu

Re: [firebug] right click inspect, shows the html portion of that section

As far as I can tell, the inspector is working but has the issue that it is first selecting the element before selecting the one you inspected. See bug 1324254 . If that's not the case for you, please file a separate bug

[firebug] Re: Don't like the new integration

As the Firebug homepage states , Firebug development and maintainance is discontinued. You were obviously automatically switched to the Firefox DevTools (using a Firebug theme). There is more info about this at

[firebug] Re: Console.log not showing under console.

Hi Christian! Firebug development and maintainance is officially discontinued and Firebug will stop working once multi-process Firefox is enabled. See https://hacks.mozilla.org/2016/12/firebug-lives-on-in-firefox-devtools/ for more info. So, I suggest, you switch over

[firebug] Re: Firebug is deactivated

Hi Arthur, Firebug is discontinued. You got automatically switched over to the Firefox DevTools. See https://hacks.mozilla.org/2016/12/firebug-lives-on-in-firefox-devtools/ for more info. Regarding the issue related to picking elements, I've filed bug 1324254

[firebug] Re: Element id

Your issue seems to be related to the Selenium IDE and not Firebug. Therefore you should rather ask in the Selenium Users discussion group . I assume that the element with the id "QTY0" is added dynamically after you're trying to access

[firebug] Re: Firebug Console tab changed?

It's not totally clear to me what you mean but I assume you are talking about AJAX requests being logged to the *Console* panel. And I also assume that you were automatically switched to the Firefox DevTools , because Firebug does not have Net,

[firebug] Re: Finds HTML elements matching chosen CSS selector(s) or XPath expression is missing.

The Inspector panel allows to search by CSS selectors, just try it out. Searching within the Inspector panel by XPath was rejected (see bug 963933 ), because you can already do that via the $x() command

Re: [firebug] Re: 397 tets fails for firebug 2.0.18

: > Firebug is not supported on PowerPC that's why I was trying to build it > from the source. > Thanks For the help. > > YugandhaD > > On Thursday, January 19, 2017 at 4:22:11 AM UTC+5:30, Sebastian Zartner > wrote: > >> Firebug is not maintained anymore for several

[firebug] Re: 397 tets fails for firebug 2.0.18

Firebug is not maintained anymore for several months now, and therefore FBTest probably wasn't run for a while. So, it's likely that many of the test cases are failing now. According to https://wiki.mozilla.org/Electrolysis#Schedule Firefox 47 is the last version with e10s being off by

[firebug] Re: Thank you Firebug!

Great to hear that! I was happy to be part of the Firebug team. Unfortunately we have to say goodbye to Firebug, but I believe the Firefox DevTools are a good replacement for it and they will get even better the upcoming months. So, the loss of Firebug then won't be that sad anymore. Sebastian

[firebug] Re: Where are useful features of firebug?

Just for clarification, the "new Firebug" are actually the Firefox Developer Tools . FirePath does unfortunately not work with them. The CSS selector can still be copied via the context menu option *Copy* > *CSS Selector*. An option to copy the

[firebug] Re: Suggestions for Firebug gaps to be closed by the DevTools

On Friday, January 6, 2017 at 5:58:15 PM UTC+1, Arvis Pinkletter wrote: > > On Thursday, 5 January 2017 04:19:38 UTC-5, Sebastian Zartner wrote: >> >> Happy New Year everyone! >> >> I can see your problem, Arvis. The Gmail issue is related to what I wrote >

Re: [firebug] Re: Inspect Element Broken

On Friday, January 6, 2017 at 12:38:28 AM UTC+1, San wrote: > > A few other differences in how the Inspect feature works: > > In Firebug (on a Mac, anyway) I was able to put a separate "Inspect" > button in the Mac's Dock (similar to Windows Taskbar). > Outside of the browser? I didn't see that

[firebug] Re: Right click and copy Xpath has been removed in Firefox with firebug, is that intentional

What you are seeing are actually the Firefox DevTools using the Firebug theme. See the Mozilla Hacks blog post for more info about that. Unfortunately, this feature is not implemented yet in the Firefox DevTools, but

[firebug] Re: Suggestions for Firebug gaps to be closed by the DevTools

Happy New Year everyone! I can see your problem, Arvis. The Gmail issue is related to what I wrote in my previous comment, though it sounds to be a bug. Though I cannot reproduce it, unfortunately. For me the contents of the mail/u/0/ source look like this:

[firebug] Re: Inspect Element Broken

Happy New Year to everyone! For clarification, the inspect feature in the DevTools does work but is slow. What's confusing is that it's first selecting the element before selecting the inspected element. I've filed bug 1324254 for this. I

[firebug] Re: Firebug 2.0.18

On Monday, January 2, 2017 at 8:44:04 AM UTC+1, Sébastien Barré wrote: > > Would love for the "Open in new Tab" feature in the "Network" tab to > behave like the old Firebug. Right now "Open in new Tab" on a POST request > will result in a GET request in the new tab. That's unfortunate, that was

[firebug] Re: Firebug and Stylish : Same CSS rules showing 2 or 3 time in CSS Panel

See https://groups.google.com/d/msg/firebug/lkM-IFNRwlI/Aoj__cSTDQAJ. Sebastian On Thursday, December 29, 2016 at 3:32:03 AM UTC+1, decembre wrote: > > I use stylish and when i use the CSS panel of firebug, i can see some CSS > rules of my Userstyles twice or more for the same element >

  1   2   3   4   5   6   7   8   9   10   >