As Alfonso mentioned, the Firefox DevTools already have a feature that goes into that direction...
As Alfonso mentioned, the Firefox DevTools already have a feature that goes into that direction...
Sebastian, the link Alfonso supplied doesn't refer to the Firefox dev tools, it involves the Chrome dev tools.
And it seems a little closer to what I'm talking about than your link does, although I'm not sure... I think they expect you to do the editing in their dev environment, not in your own text editor as I prefer. I only looked briefly at the Moz page you linked to, but from the introduction, it seems to refer only to finding the original JavaScript sources of compiled JavaScripts.
I'm interested in mapping the current browser-rendered page to its main HTML server page, and then opening that HTML in my text editor, nothing more. Nothing fancy.
This is so important to me (the way I work) that if a newer version of Firefox breaks the extension I'm using, I'll stop upgrading Firefox and stick with the old version. If Firefox could be scripted with AppleScript, I might be able to figure out a way to do the mapping there... but AFAIK Mac Firefox isn't AppleScript-able.
I like the Firefox/Firebug devel interface better than Chrome's (I guess I'm just more used to it), but Chrome is much more successful at rendering a wide range of pages for ordinary browsing... so I could see a situation where I end up developing in an old version of Firefox, but doing routine browsing in a current version of Chrome. Which sounds a little awkward. That's what I'm hoping to avoid.
--
You received this message because you are subscribed to the Google Groups "Firebug" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebug+u...@googlegroups.com.
To post to this group, send email to fir...@googlegroups.com.
Visit this group at https://groups.google.com/group/firebug.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/7f8ce879-6d3d-4187-8592-5b919c72ff0f%40googlegroups.com.
The firebug method of having the list as a tab was much much better.This opens a horizontal panel across the bottom containing both the console & the DOM properties.In Firebug under HTML the was a DOM tabCurrently in dev tools under inspector, one must use the context menu to select "Show DOM properties".
Are there plans to have that (very useful) option in dev tools?
This is a real pain. The console is not needed when viewing the DOM properties and having the property list down there requires excessive scrolling or resizing of panels.
On 22 July 2016 at 19:36, Sebastian Zartner <sebastia...@gmail.com> wrote:
You're lucky. The suggestions already improved in Firefox 48. See https://developer.mozilla.org/en-US/docs/Tools/Page_Inspector/How_to/Examine_and_edit_CSS#Edit_rules and https://bugzil.la/1168246.So, to everyone wanting to post to this thread, please check the latest Firefox Nightly before suggesting something here.Sebastian
On 22 July 2016 at 11:12, Qlum Wyrfex <qlu...@gmail.com> wrote:
I find the auto completion in firebug much better then the one in the native debugger.
For example when creating a new property in css if you type "b" the native debugger will suggest "backface-visibility" which is something I personally never even knew existed where firebug would suggest "background" which is much more commonly used.
The native dev tools just seem to suggest them alphabetically.
--
You received this message because you are subscribed to the Google Groups "Firebug" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebug+unsubscribe@googlegroups.com.
To post to this group, send email to fir...@googlegroups.com.
Visit this group at https://groups.google.com/group/firebug.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/7f8ce879-6d3d-4187-8592-5b919c72ff0f%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Firebug" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebug+unsubscribe@googlegroups.com.
To post to this group, send email to fir...@googlegroups.com.
Visit this group at https://groups.google.com/group/firebug.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/CAERejNYw5%2BvPtXF09NNVs_oYPhc2je_4%3DBOoF3rBBa6_4PD2JA%40mail.gmail.com.
see bug 1306160 at bugzilla
On 13 September 2016 at 07:17, Mahks Doma <mah...@gmail.com> wrote:
The firebug method of having the list as a tab was much much better.This opens a horizontal panel across the bottom containing both the console & the DOM properties.In Firebug under HTML the was a DOM tabCurrently in dev tools under inspector, one must use the context menu to select "Show DOM properties".
Are there plans to have that (very useful) option in dev tools?
This is a real pain. The console is not needed when viewing the DOM properties and having the property list down there requires excessive scrolling or resizing of panels.
On 22 July 2016 at 19:36, Sebastian Zartner <sebastia...@gmail.com> wrote:
You're lucky. The suggestions already improved in Firefox 48. See https://developer.mozilla.org/en-US/docs/Tools/Page_Inspector/How_to/Examine_and_edit_CSS#Edit_rules and https://bugzil.la/1168246.So, to everyone wanting to post to this thread, please check the latest Firefox Nightly before suggesting something here.Sebastian
On 22 July 2016 at 11:12, Qlum Wyrfex <qlu...@gmail.com> wrote:
I find the auto completion in firebug much better then the one in the native debugger.
For example when creating a new property in css if you type "b" the native debugger will suggest "backface-visibility" which is something I personally never even knew existed where firebug would suggest "background" which is much more commonly used.
The native dev tools just seem to suggest them alphabetically.
--
You received this message because you are subscribed to the Google Groups "Firebug" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebug+u...@googlegroups.com.
To post to this group, send email to fir...@googlegroups.com.
Visit this group at https://groups.google.com/group/firebug.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/7f8ce879-6d3d-4187-8592-5b919c72ff0f%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Firebug" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebug+u...@googlegroups.com.
To post to this group, send email to fir...@googlegroups.com.
Visit this group at https://groups.google.com/group/firebug.
Since devtools support ChromeLogger natively I think about writing a wrapper for ChromeLogger which provides FirePHP syntax.
Am 22.11.2016 um 13:59 schrieb Sebastian Zartner:
> Please let us know the most pressing things you're missing!
Shall we add things even if there is already a bug on bugzilla?
For me this would be Add cookie function.
I suggest showing normal log text in black, and warnings in red, rather than the other way around.
Also the ability to configure the type styles (size, color, even font) would be nice.
Also if anything could be done to help the FirePHP developer get it working again...
I know that there is already bug 704094, but I have not seen any comment about the lack of the DOM tab inside the Inspect Element panel, along with the tabs: rules, computed, animations and so on.
So I decided to post this message to remind them of this feature.
PS: Sorry my english.
One thing that seems to be missing is the autocomplete when making CSS changes.
When I would begin typing a CSS rule - Firebug would auto complete it depending on the page I was on (E.G. On Wordpress, it was able to detect the fill in the page-id)
Now it doesn't complete at all - making it more cumbersome.
I have to say I HATE the Firefox dev tools, they are shite compared to Firebug. Please bring Firebug back, sir.
I am dearly missing the feature that displayed json in a cookie in a nice format.
But firebug was more of what I need, so fast compared with the problems I face right now.
- Now the inspector is a pain, sometimes doesn't work to choose an element, sometimes choose the element but only for 5 seconds and I have to search for it again.
- "Right click inspect with firebug" sometimes works, some times don't, sometimes show you the "body" and not the element you choosed.
- Adding tags, atributes, css, is more complicated and doesn't show live.
Now:
- Right click -> inspect (doesn't work)
- Right click -> inspect (Worked but does not show the element I choseed)
- Right click -> inspect (woked fine this time)
- I choose the elment to edit (cannot edit)
- Chose the atribute (cannot edit)
- Chose the element again and "right click -> edit element"
- Show the entire node, search for the element inside.
- I write to edit the element (nothing happens)
- Pressed enter (just create a new line)
- Deleted the line and re-write the atribute (because it created so many gaps and you have to clean manually)
- Enter doesn't work, so how you do: "ok make the changes"? I click there (doesn't work), click on the page (doesn't work), click on the screen or menu (doesn't work).
I would rather see some small improvements like:
- Jumping from one value to another in the BOX Model view (like in Firebug!)
- A real good syntax highlighting theme coz the new syntax highlighting is really bad (yes I know I now have my own chrome.css)
- Support copying the whole - absolute - CSS Selector path and not only the relative path (like in Firebug!)
- A simple shortcut for the eyedropper
and so on...
I think that these suggestions are not so hard to implement, aren't they? Please correct me if I'm wrong!
The Firefox DevTools team is working on closing the gaps between their tools and Firebug.
In the first quarter of the year the Firebug theme, HTTP log inspection in the Console panel and the DOM panel were ported to Firefox (see bug 1256749).
Now the team is asking what should be fixed in Q2 2016. See bug 1267303.
My suggestions:(These are all existing issues, but you can also suggest issues that are not already tracked in Bugzilla, of course.)
- 1004678: Break on DOM mutation
- 1267144: Allow to set breakpoints for XHRs
- 1165010: Set a breakpoint for errors in WebConsole (like Firebug)
- 1226640: Add Events side panel
- 1227054: [rule view] Show whether a CSS property, value or selector is valid
- 1267140: Allow auto-completing non-enumerable properties and member functions return types of known types
Sebastian
Inspector Box Model tab – you can not edit the height/width of the inspected item as you used to be able to do in FB. Everything else, but not height &width.
--
You received this message because you are subscribed to a topic in the Google Groups "Firebug" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/firebug/Q6eyvGt6hyI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to firebug+unsubscribe@googlegroups.com.
To post to this group, send email to fir...@googlegroups.com.
Visit this group at https://groups.google.com/group/firebug.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/1b1cf74b-3290-7eb9-867c-e3fc92baf06c%40gmx.de.
For more options, visit https://groups.google.com/d/optout.
Yes, I can stay at the version and continue to run Firebug (I am quite certain that I cannot have two versions on the same Mac)
--
You received this message because you are subscribed to a topic in the Google Groups "Firebug" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/firebug/Q6eyvGt6hyI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to firebug+unsubscribe@googlegroups.com.
To post to this group, send email to fir...@googlegroups.com.
Visit this group at https://groups.google.com/group/firebug.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/2ae4398b-4163-f849-2081-992339e12d62%40gmx.de.
So you, who are working in the fastest changing industry in the world,
be a bit more flexible and give a new tool a chance. And go to bugzilla
and vote for the bugs that annoy you most.
Console Tab:
How many of these items have been implemented Sebastian?
I cannot use this new tool at all. Where is the side by side console that allowed multiple line script and loading of scripts from history? I have been using this tool since it's inception and now we are forced to use a different browser.
The Firefox dev tools has ruined my development. Now I need to find a new browser to develop one. Sad day.
I do not know what prompted this move
It's not so much that they can do the same sort of things but differently, it's also a rote memory issue
Now I find myself trying to figure out what this prompt means "The Web Console logging API (console.log, console.info, console.warn, console.error) has been disabled by a script on this page" when I open the console.
David Smith <sm...@virtuluxe.com> wrote:Yes, I can stay at the version and continue to run Firebug (I am quite certain that I cannot have two versions on the same Mac)
Luckily -- despite your being "quite certain" -- that's not true, or at least it didn't used to be true. I have a free program called MultiFirefox installed on my Mac...
Am 09.12.2016 um 00:19 schrieb David Smith:
> I do not know what prompted this move,
> whether it is internal politics, a financial or corporate decision, but it
> is a monumental change for the people that develop with Firebug.
Firebug was an extension to Firefox, built by volunteers. There where
not enough of them to switch to multi process architecture. The devtools
are built-in, they come from mozilla. ...
The devtools are more or less usable now and in some aspects even better
than firebug. ...
So you, who are working in the fastest changing industry in the world,
be a bit more flexible and give a new tool a chance. And go to bugzilla
and vote for the bugs that annoy you most.
I try to keep an open mind and use all the browsers a little, rotate the usage, understand what are the improvements that each dev tools have, but so far I still haven't found anything that makes the native DevTools of Firefox anything special.
It includes options that I will never use, but it lacks features that were present in Firebug. So currently Firefox is my last option when I want to debug something complex.
Maybe the best is to put bug report on the best place : https://bugzilla.mozilla.org . See https://bugzilla.mozilla.org/show_bug.cgi?id=991806 for example ?
The Debugger tab - in "sources", when I am working on a site where you have to log in to see the page, I need the "source" of the page I'm working on to be the same as the one in the browser, that is, if I'm logged into the site, the source in the debugger tab for that page should also be the "logged in" version of the page. Our pages redirect you to a login page if you aren't logged in, so currently, in my "source" tab if I'm trying to work on something, I see the markup and scripting for the login page instead of the page I actually want. What's weird about this is that the "inspector" tab has the right content, but not the debugger tab.
Also, scrolling up and down in the debugger tab isn't as nice as in the inspector tab; I can't use my mouse pointer on the scroll bar - I have to use my wheel or my keyboard to page up and down.
On Friday, December 16, 2016 at 4:17:41 PM UTC+1, Arvis Pinkletter wrote:The Debugger tab - in "sources", when I am working on a site where you have to log in to see the page, I need the "source" of the page I'm working on to be the same as the one in the browser, that is, if I'm logged into the site, the source in the debugger tab for that page should also be the "logged in" version of the page. Our pages redirect you to a login page if you aren't logged in, so currently, in my "source" tab if I'm trying to work on something, I see the markup and scripting for the login page instead of the page I actually want. What's weird about this is that the "inspector" tab has the right content, but not the debugger tab.
Do you have a URL, so this can be reproduced? Did Firebug (before Firefox 50) show different results?
Also, scrolling up and down in the debugger tab isn't as nice as in the inspector tab; I can't use my mouse pointer on the scroll bar - I have to use my wheel or my keyboard to page up and down.
The Debugger panel is currently reworked for a better UI and to be independent of the DevTools. You may try it out in the latest Developer Editions and Nightlies of Firefox. Try it out and let them know if it's still not working for you.
On Friday, December 16, 2016 at 9:25:30 PM UTC+1, Arvis Pinkletter wrote:Console Tab:XHR requests have "Headers", "POST", "Response", "Call Stack".Need these that Firebug had: "JSON" (the nicely navigable JSON object that is the Response), and "Cookies"The JSON structure is available inside the Response tab. I'll add that to the migration guide.
On Monday, 19 December 2016 02:36:18 UTC-5, Sebastian Zartner wrote:On Friday, December 16, 2016 at 4:17:41 PM UTC+1, Arvis Pinkletter wrote:The Debugger tab - in "sources", when I am working on a site where you have to log in to see the page, I need the "source" of the page I'm working on to be the same as the one in the browser, that is, if I'm logged into the site, the source in the debugger tab for that page should also be the "logged in" version of the page. Our pages redirect you to a login page if you aren't logged in, so currently, in my "source" tab if I'm trying to work on something, I see the markup and scripting for the login page instead of the page I actually want. What's weird about this is that the "inspector" tab has the right content, but not the debugger tab.
Do you have a URL, so this can be reproduced? Did Firebug (before Firefox 50) show different results?Due to security reasons, I can't disclose a URL. But I can suggest this: log in to gmail. You ought to be on a page with a URL that looks like https://mail.google.com/mail/u/0/#inbox .... open up the Debugger, and find mail/u/0/ in the sources. The source there ought to have links for "sign in", "create an account", "get gmail", etc, while the browser's viewport shows your inbox and not have those links. One thing I find weird about this is that the "inspector" tab agrees with the viewport.And yes, in firebug, when the script tab still worked, it showed sources that matched the viewport.
//# sourceURL
comment at the end.Also, scrolling up and down in the debugger tab isn't as nice as in the inspector tab; I can't use my mouse pointer on the scroll bar - I have to use my wheel or my keyboard to page up and down.
The Debugger panel is currently reworked for a better UI and to be independent of the DevTools. You may try it out in the latest Developer Editions and Nightlies of Firefox. Try it out and let them know if it's still not working for you.OK, I grabbed the latest Developer Edition. Good news is that the sources match the viewport.
The vertical scrollbar on the source pane is sometimes clickable, if I point my mouse on the exact perfect pixel, occasionally, but I can't find a predictable way to make it always work. The vertical scrollbar in the inspector works nicely when clicked, and I can drag the scroll-cursor up and down at my leisure.
On Friday, December 16, 2016 at 9:25:30 PM UTC+1, Arvis Pinkletter wrote:Console Tab:XHR requests have "Headers", "POST", "Response", "Call Stack".Need these that Firebug had: "JSON" (the nicely navigable JSON object that is the Response), and "Cookies"The JSON structure is available inside the Response tab. I'll add that to the migration guide.Ah, I see. If I click the arrow next to my request, the response tab there will show the JSON object tree after I click on "Size limit has been reached. Click here to load more." I had thought it would just load the rest of the Raw Data.
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:
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:
You should do two things. First, create a fresh Firefox profile and try it there. If that doesn't help, try out the Developer Edition or Nightly of Firefox, which have a new debugger UI and see if it works for you there. If that still doesn't work for you, you should file a bug for the DevTools and, if possible, attach a simple test case, so people can reproduce it. If you file a bug, please post the link to it here for back reference.
Sebastian
On Tuesday, November 22, 2016 at 3:38:42 PM UTC+1, Erik Krause wrote:Am 22.11.2016 um 13:59 schrieb Sebastian Zartner:
> Please let us know the most pressing things you're missing!
Shall we add things even if there is already a bug on bugzilla?
Yes, of course! The point of this thread is to tell the DevTools people what the Firebug users are missing most, so they can do some prioritization. If you know the bug number, please share it here.
Will there be any Xpath utilities, such as what FirePath covered?
Hey there, when I opened Firebug today and discovered the changes, my heart sank. Gone is the html editor pane and the ability to edit html with one click of the edit button. Now it seems I need to right click and choose 'Edit as html' from the contextual menu.
Plus, changes need to be 'committed' by clicking outside the inline editor window before they are rendered.
--
You received this message because you are subscribed to a topic in the Google Groups "Firebug" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/firebug/Q6eyvGt6hyI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to firebug+unsubscribe@googlegroups.com.
To post to this group, send email to fir...@googlegroups.com.
Visit this group at https://groups.google.com/group/firebug.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/0189e797-9750-4ed1-bc3a-a6c54a98b343%40googlegroups.com.
Every time I hover a variable while debugging to see it value, the entire devtools "reload", only to show a popup.
Worst, if I have some object in variable panel "expadend" (?) Devtools close it when reloading.
The only way to close this "popup" are click somewhere else, not only hover out like firebug. I cant hover another variable while I dont close the first.So, I cant compare hover variable against value of property in an object. I need to put both in watch...
I think it will be necessary to break into several bugs to find a complete solution.
Sorry my bad english.
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 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 UTC+1, Andrew Carlisle wrote:Hey there, when I opened Firebug today and discovered the changes, my heart sank. Gone is the html editor pane and the ability to edit html with one click of the edit button. Now it seems I need to right click and choose 'Edit as html' from the contextual menu.
You can edit it by pressing F2.
Plus, changes need to be 'committed' by clicking outside the inline editor window before they are rendered.
--
You received this message because you are subscribed to a topic in the Google Groups "Firebug" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/firebug/Q6eyvGt6hyI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to firebug+u...@googlegroups.com.
To post to this group, send email to fir...@googlegroups.com.
Visit this group at https://groups.google.com/group/firebug.
To unsubscribe from this group and all its topics, send an email to firebug+unsubscribe@googlegroups.com.
To post to this group, send email to fir...@googlegroups.com.
Visit this group at https://groups.google.com/group/firebug.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/f937bd12-401e-43df-8073-693c268b9990%40googlegroups.com.
I posted a bunch of my gripes on one of Honza's blog posts from late 2015. He suggested I file tickets in Bugzilla which, sorry to say, I never got around to. Life interferes, you know? Some have been addressed, these are the remaining ones I still find ... annoying. I realize that some/all of these might be "nope, it's the way dev tools works now", and if that's the case then I can accept it, but I might as well get my 2 cents in. Apologies if some of these have already been brought up.thx
- debugger search. egads. #linenumber is engraved in my fingerprints. Finding something in the *current* file now needs a prefix (excuse me…”operator”)? What is that operator again? oh, wait, you can’t see those unless the search box is empty. I've managed to remember Ctrl-F most of the time, but I still find myself using "#" instead of ":" about 75% of the time to go to a line number.
- The multi-line command window on the Console tab. Yes, scratchpad is kind of like that, but not really. It was nice having it on Console.
- Back in high school you’d never hear me say this, but “I miss history”. Especially in the form of the Console Command Editor History menu. Yes, you can up-arrow through your history, but you don't see what that history actually is until you get there.
- Remembering the source file you had open the last time you opened the debug window on this page.
- Inspector Box Model tab – you can not edit the height/width of the inspected item as you used to be able to do in FB. Everything else, but not height &width.
jeff