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

"Inspect Element with Firebug" has mysteriously reappeared (in the contextual menu) for me too. It brings up Firebug, not "the Firefox DevTools with a Firebug theme". However, the Firebug window that it brings up is still partially broken. The HTML tab works (I can edit something and see the

[firebug] Console grouping, Scratchpad, Network panel questions

1. Console grouping: Since I use a lot of console log items, I found it convenient in Firebug to group them with console.groupCollapsed() and console.groupEnd(). Worked fine. In the Moz devtools, all that does is indent the grouped items slightly, but they don't collapse. This page

Re: [firebug] Devtools cache settings labeled wrong?

I normally keep "Disable HTTP Cache" checked. As it happens I just yesterday unchecked it (that is, I enabled the cache) because I was working on a JS 'preload components' function and I needed to see whether the items were caching properly or not. (I'm running Mac FF 53.0.2). The devtools

[firebug] Partial fix for Console colors

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 it's because I'm on a Mac? Or something specific to my FF profile?

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

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 on my Mac. GetFirebug.com also seems to mention FF 47 as the cutoff --

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

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 > (good) one, even though it's discontinued, if i promise to not call > support?

Re: [firebug] Re: Firebug 2.0.19

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, and I seem to vaguely remember it could even show a "badge" on the icon (button) with a numeral warning of errors in the current web

Re: [firebug] Re: PHP server messages

I don't understand why people are ​now ​ saying you ​_​ have ​_​ to use Chrome Logger ​ to log PHP from Firefox.​ That's not true . In this discussion list, ​see the thread entitled "replacement for firephp (devtools)" ​ from late September to early December 2016 (sorry, I don't know how to link

Re: [firebug] Firebug 2.0.19

It's nice that you fixed this for those of us with e10s disabled... but I don't understand why you bothered to fix this but not something else equally important (more important to me) -- I mean that the Firebug Console no longer displays anything at all. Without the Console, Firebug is useless, so

Re: [firebug] Firebug 2.0.19

utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Lawrence San Business Writing: Santhology.com Cartoon Stories for Thoughtful People: Sanstudio.com -- You received this message because you are subscribed to the Google Groups

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

Thanks, Sebastian. Your link to variables.css opens what seems like a standard CSS file. However, I spent a lot of time searching for the local copy of that file

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

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 opposite of what it should be. All my experiments have failed to unearth the reason

Re: [firebug] Re: Inspect Element Broken

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). There doesn't seem to be any separate Inspect button in DevTools. If the DevTools console is attached to the

Re: [firebug] Re: future of this list (was: Tracking down CSS rules)

Sebastian Zartner wrote: Furthermore, I think a list like you outlined it already exists with > https://groups.google.com/forum/#!forum/mozilla.dev.web-development. > ​I just took a quick look at it. It seems to be filled with spam for sneakers, jackets, and

Re: [firebug] future of this list (was: Tracking down CSS rules)

I agree with you, Erik, but I think your use of the word "developer" might be a little confusing to some people. I know what you mean, but many of us "users" think of ourselves as "developers" too -- that is, web developers. I've liked this list/group for a long time, and I'd love to see it

[firebug] Tracking down CSS rules

I'm having some minor problems tracking down the source of CSS rules using the Mozilla DevTools. I click to inspect a section in the rendered page. The Inspector panel's Rules tab shows me the correct selector, but next to that it says "inline:13". This is a little confusing because there are no

Re: [firebug] Re: replacement for firephp (devtools)

Erik Krause wrote: > Yesterday I wondered why some calls caused an empty log. I soon discovered > that json_encode doesn't handle resources. So I added a special handling > for resources and output all other types with print_r, which should account > for most other special

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

David Smith 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

Re: [firebug] Re: replacement for firephp (devtools)

Erik, what you did is probably much better than what I'm using at the moment, and I'll take a look at your version soon. But for what it's worth, I'm using an extremely simple script to temporarily substitute for FirePHP (which I was using before). This isn't really my code; I just

Re: [firebug] Re: ALL console logging (flog, console.log) is utterly broken

Another thing to check: make sure you're looking at the Web Console and not the Browser Console . They're similar looking but have different purposes. (The links are to the

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

​Erik Krause said:​ > Since devtools support ChromeLogger natively I think about writing a > wrapper for ChromeLogger which provides FirePHP syntax. > Thanks, that sounds useful. In the meantime, here's an entire thread on StackOverflow

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

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... Am 22.11.2016 um 13:59

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

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 >

Re: [firebug] Re: Firebug starting Firefox Dev Tools?

Sebastian said: To get Firebug running again, you need to disable the multiple processes in > Firefox > > . I think the instructions on that page are outdated -- I can no longer find a checkbox

Re: [firebug] Re: Color of main Console text

Sebastian said: > You're right. The text of messages logged via the console API (i.e. > console.log(), console.info(), etc.) is indeed red. That is definitely a > bug in the theme. I've added this to bug 1269730 > , which I've filed > some

Re: [firebug] Re: Color of main Console text

Sebastian, I'm seeing something quite different from your screenshot. With the Firebug Theme on, my Console background is white, not yellow. The text from the Net tab is black, but I don't use that much. The text from the Logging tab (which I mostly use) is all red, both from JS and from PHP --

[firebug] Color of main Console text

I've been using the built-in Firefox tools for a while, and although I mostly like them, the color of Console text is annoying me. With the Firebug theme, the main Console text looks pinkish-red. With the Dark theme, it looks orange. I don't remember the Console text in the real Firebug being

[firebug] Which Firebug does GetFirebug.com refer to?

the new version? Thanks, Lawrence -- Lawrence San Business Writing: Santhology.com Cartoon Stories for Thoughtful People: Sanstudio.com -- You received this message because you are subscribed to the Google Groups "Firebug" group. To unsubscribe from this group and stop receiving e

Re: [firebug] Re: replacement for firephp (devtools)

In other words, you install the server library... but even though it's meant to accompany the Chrome extension, you don't need any extension for it in Firefox? Or, if I misunderstood... is there some way of installing a Chrome extension into Firefox now? On Fri, Sep 30, 2016 at 7:45 AM, Jan

Re: [firebug] Re: Firefox 49 and Firebug 3

Thanks, Sebastian. I was wondering where the DOM panel went. Now ​it's back! I still have a few questions about the new interface... In the Debugger panel, there's a column on the left with tabs for Sources or Call Stack. Is there some way to toggle (hide) the ​ whole​ Sources/Call Stack column

Re: [firebug] Re: FontSize control in Firebug3?

/group/firebug. > To view this discussion on the web visit > https://groups.google.com/d/msgid/firebug/1def8598-f132-4e1b-a0e6-cb5f4068475c%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- Lawrence San Business Writing: Santhology.com Cartoon Stories for T

Re: [firebug] Re: Customize debugger keyboard shortcuts?

Thanks for the link. Apparently lots of other people would also like to customize the debugger keys. There are some suggestions here for using about:config for that purpose, but when I enter them in the filter box, the page

[firebug] Customize debugger keyboard shortcuts?

Firebug's main keyboard shortcuts for JS debugging seem to be the same for Mac and Windows: f8 = Continue f10 = Step Over f11 = Step Into Shift-f11 = Step Out I'd like to change these to different fkeys, but Firebug's "Customize Shortcuts" dialog doesn't seem to include those items. The Key

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

> > 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,

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

ool to do this. On Wed, May 4, 2016 at 5:43 PM, Erik Krause <erik.kra...@gmx.de> wrote: > Am 04.05.2016 um 18:41 schrieb Lawrence San: > >> My workflow is based on browsing through the website I'm building, >> in Firefox, and when I see something that needs editing (

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

Sebastian, your suggestions sound excellent. I'd like to add just one of my own, which I've made before, but only here since I don't have an account on bugzilla... I'll make up a name for it: *Live code mapping*. Add some way to reverse-map from the current URL in Firefox, to the corresponding

Re: [firebug] Re: Now only see "Other" group under under HTML "Computed" tab

I'm running the same versions (Firefox 46.0 and Firebug 2.0.16) on the Mac, and having the same problems. Are these problems going to be fixed in Firebug 2.x, or has all maintenance on it ceased, pending the Firebug 3.x rollout? Michał Lepiarz wrote: > Downgrade Firefox to 2.0.15. It will fix

Re: [firebug] Re: Firebug 2.0.16

On Thu, Mar 31, 2016 at 6:08 AM, Erik Krause wrote: > But anyway, why would a web developer (I think the mayority of firebug > users) stick to a firefox version, that has almost no market share? I > wouldn't dare to deliver websites to my clients, that where not tested on >

Re: [firebug] Re: Firebug 2.0.15

> email to firebug+unsubscr...@googlegroups.com. > To post to this group, send email to firebug@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/c0abfd9d-17

Re: [firebug] Re: Firebug 3 Multi-line Concern

​I ​ never even noticed ScratchPad before! Seems to work, for a simple if/then alert anyway... I'll have to experiment with it. Thanks for pointing it out. What are the limitations of its not being integrated with Firebug?​ I guess that a command to copy code between the two would be helpful...

Re: [firebug] Re: Firebug 2.0.15

The most likely reason I might have to disable e10s has little to do with Firebug. I have a suspicion e10s is going to disable other development extensions I find critical. I hope I'm wrong; we'll see. Especially, if David Ficano's Dafizilla ViewSourceWith stops working -- which seems quite

Re: [firebug] Firebug 2.0.15

Regarding the linked discussions... I still don't like the revised message: "The next version of Firebug will be integrated directly into the Firefox Developer Tools..." etc. ​As a whole, I find the new description vague and unclear. Do I have some choice to make? Is Firebug just an optional skin

Re: [firebug] Firebug 3 Multi-line Concern

I also use the Command Editor (multi-line console) frequently to test code; if it disappeared that would be awful. Coincidentally, just yesterday I noticed a limitation (?) of the Command Editor. I've been experimenting with adding a custom property to a function as a way to maintain state on a

Re: [firebug] Re: v2.0.14 not reporting javascript case errors

I think the reason this is so confusing to people is that HTML and CSS are not case-sensitive, but JavaScript is -- even when the JS tag is quite similar to an HTML/CSS tag it's derived from. -- You received this message because you are subscribed to the Google Groups

Re: [firebug] Re: Firebug 2.0.13

On both Mac and Win7, Firebug 2.0.13 + Firefox 43.0.4 seem to be working mostly okay for me. I just checked about:config for the signatures flag that Sebastian referred to, which I don't remember changing. The xpinstall.signatures.required has _not_ been user-altered: it's still set to true.

Re: [firebug] Inspecting wrappers with Firebug

By "wrapper" I assume you mean tag? Anyway, if that's literally what you have in your document, then I'm not surprised that Firebug might not react the way you expected. You shouldn't use typographer's quotation marks ("curly quotes") in HTML markup. Try replacing them with straight quotes and see

Re: [firebug] Re: Bare ID name resolves to actual element -- why?

> Also you can set "use strict" and that will cause also an error (although > at runtime) on each undeclared variable. Thanks... I just read a little about "use strict", which I haven't used before, and tried to use it in this context. It didn't seem to work. Specifically: First I loaded an

Re: [firebug] Re: Bare ID name resolves to actual element -- why?

Ah, interesting. I never noticed that before. Let me make sure I understand this correctly... the reason we still have to "get" an element -- that is, do document.getElementById("foo") or $(foo) or whatever, when coding JS -- is that the DOM is a feature of the user agent (e.g. a browser engine),

Re: [firebug] Re: Bare ID name resolves to actual element -- why?

alfonsoml wrote: > You can try to use it that way if you like, but > ​...​ > ​No, I don't want to do that. I have a different concern, almost the opposite of what you said. I want to use the normal JS approach to "getting" an element. But if my JavaScript is complicated... how can I be sure

Re: [firebug] Re: Bare ID name resolves to actual element -- why?

OK, I'll try that, but there's something else going on. Forget about my function; let's take the simplest possible case. Here's what I just tried: I created the world's simplest HTML file -- NO JAVASCRIPT AT ALL. Here's the complete code: trashtest.html What is going on? I

[firebug] Bare ID name resolves to actual element -- why?

This is such a basic question that it will probably make me look like an idiot, but anyway... I have an element in my document: ... I'm writing a new JS function (in a linked JS file), and sending it a single argument, the ID of an element in the document. My real intention was to send it as a

Re: [firebug] 90 seconds?..

Just a thought... really just a wild guess... do you by any chance have Firefox set to load a custom home page when it launches, or when it creates a new window or tab? Say, a custom home page that contains or links to some JavaScript? -- You received this message because

[firebug] Function logging somewhat vague

ents passed in to the function? Thanks much! -- Lawrence San Business Writing: Santhology.com Cartoon Stories for Thoughtful People: Sanstudio.com -- You received this message because you are subscribed to the Google Groups "Firebug" group. To unsubscribe from this group and stop

Re: [firebug] Re: Am I the only one, or ...

Sebastian wrote: > Note that hanging is not the same as crashing. ​I think I understand the distinction you're making but I'm not sure... is "hang" synonymous with "freeze", and "crash" synonymous with "sudden unexpected quit"?​ Also, what if a program (Firefox or whatever) freezes and either

[firebug] Stopping runaway function

I have a very basic question... I'm working on defining a new function that's in a JS file, which is called from a very simple test web page. The new function contains a few console log items so I can see what it's doing. My Firebug console is open. When I reload the web page, the first of the

Re: [firebug] Re: Showing the name of the file that contains the source code

Sebastian wrote: > The reason why the HTML output seen in the browser cannot be directly > mapped to the server-side source code is that it is mostly dynamically > generated. ​For PHP-generated code, of course that's true. OTOH... in general, ​it *is* sometimes possible to map a

Re: [firebug] Firebug 2.0.12 breaks my custom login, apparently

Have you tried this with Firebug on for that website, but all its panels disabled? If it worked then, you could try enabling the panels one at a time until it broke, to narrow down the culprit. Also, have you checked the debugger to make sure you don't have any breakpoints? There's a separate

Re: [firebug] Re: Filtering M3U8

da61a-e7ac-457d-aa4a-cd10feab8f4b%40googlegroups.com > <https://groups.google.com/d/msgid/firebug/db4da61a-e7ac-457d-aa4a-cd10feab8f4b%40googlegroups.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Lawrence San Busi

Re: [firebug] Future if Firebug?

ension to get down >>>>>>> into >>>>>>> the guts of the browser and make major changes. For example, look at the >>>>>>> awkward interface that Chris Pederick was forced to use in Chrome for >>>>>>> his >>>>>&

[firebug] Tracking down missing image

I just spent many hours tracking down an error -- I finally solved it but I'm wondering if there was a more efficient approach. It started when Firebug's Net panel alerted a missing GiF on the dev server. The link in the Net panel pointed to the HTML file, but a quick search revealed there was no

Re: [firebug] Future if Firebug?

/optout. -- Lawrence San Business Writing: Santhology.com Cartoon Stories for Thoughtful People: Sanstudio.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

Re: [firebug] Filter in network tab

/msgid/firebug/27357a0b-e8ae-4458-a50a-46deb5d22add%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Lawrence San Business Writing: Santhology.com Cartoon Stories for Thoughtful People: Sanstudio.com -- You received

Re: [firebug] Console Clear button hides and clears command windows as well.

://groups.google.com/d/optout. -- Lawrence San Business Writing: Santhology.com Cartoon Stories for Thoughtful People: Sanstudio.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

Re: [firebug] Re: Persist element.style?

/0481cd3c-e5fd-4d95-883a-7a45bc84386e%40googlegroups.com https://groups.google.com/d/msgid/firebug/0481cd3c-e5fd-4d95-883a-7a45bc84386e%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Lawrence San Business Writing

[firebug] Persist element.style?

I ​n the HTML panel's Style side-panel, if I enter a temporary element.style rule, that rule gets wiped out as soon as I reload the page. I guess that's usually what you'd want to happen, but is there any way to make the element.style rule persist across page reloads? Thanks.​ -- You received

[firebug] Live bug looks dead

I ​'m experiencing a minor problem with the current versions of Firefox + Firebug on my Mac. Normally, I have a separate Firebug console window open on the second mo​nitor, and when it's active the little firebug icon at the bottom of the main Firefox window is lit-up orange. Recently, however, it

[firebug] Is there a 2.0.9.1 Firebug?

​I'm running Firebug 2.0.9 in both Mac and Windows, Firefox 37.0.2. ​ F ​or two or three days now, in my Extensions update window (on the Mac side), I've been seeing a listing for Firebug 2.0.9.1-signed Update. What's a signed update? Anyway, every time I click to accept it, there's a progress

Re: [firebug] Re: Firefox 36 crashes while debugging JS with FireBug 2.0.8

For me, Mac Firefox 36.0.1 has been crashing *a lot* even when I'm not using Firebug at all (i.e. FB is installed and enabled but not turned on for the current website). I uninstalled a different extension that I suspected and will see what happens. Maybe FF36 or 36.0.1 is just more fragile ​while

Re: [firebug] Re: Possible clue to breakpoints problem

Sebastian, you haven't addressed my core question, which doesn't require looking at *any* code: in general, what makes a line of code breakable (in any debugger, not just Firebug)? Why is some code executable from the browser's point of view but not from the debugger's? @Mahks Doma: No, there are

Re: [firebug] Re: Possible clue to breakpoints problem

The green lines are executable lines, that is lines with JavaScript that can be reached by the debugger when you set a breakpoint. ​That seems almost tautological. What is it that makes one line of JavaScript executable in the sense you mean, and another line not? My code lines that Firebug

Re: [firebug] Re: Has FB 2 bugfixing stopped?

Hmm... playing around more with either combination (FF 35.0.1 and Firebug 2.0.8 running inside my Win7 VM; or FF 34.0 and Firebug 2.0.8 directly on my Mac) ... I'm seeing behavior that I don't understand. I have an illustration page (in my Apache devel server, not online) where that HTML page

Re: [firebug] Re: Has FB 2 bugfixing stopped?

Now ​breakpoints have suddenly stopped working in the main JS file too; when I try to set one I'm just getting the throbber, as the other people here described. Overall the behavior is so erratic that I don't see how I could set up a repeatable test case even if I tried. -- You received this

Re: [firebug] Re: Has FB 2 bugfixing stopped?

/5313e06e-1a84-45f6-a836-c7ff164a09cb%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Lawrence San Business Writing: Santhology.com Cartoon Stories for Thoughtful People: Sanstudio.com -- You received this message because

Re: [firebug] Re: Has FB 2 bugfixing stopped?

. For more options, visit https://groups.google.com/d/optout. -- Lawrence San Business Writing: Santhology.com Cartoon Stories for Thoughtful People: Sanstudio.com -- You received this message because you are subscribed to the Google Groups Firebug group. To unsubscribe from this group

[firebug] Has FB 2 bugfixing stopped?

Does the focus on developing the new Firebug 3 mean that there won't be any more work on bugfixes for FB 2.0.8? For example, regarding breakpoints when FB 2.0.8 is used with Firefox 35? In other words, will there be a FB 2.0.9? Thanks. -- You received this message because you are subscribed to

Re: [firebug] Re: firebug 2.0.8 stops at no breakpoints in firefox 35.0.1 on Mac or PC

/652fa9fe-509f-4c00-b04c-5342370f1b1d%40googlegroups.com https://groups.google.com/d/msgid/firebug/652fa9fe-509f-4c00-b04c-5342370f1b1d%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Lawrence San Business Writing

Re: [firebug] change in inspect in v2.0.8

I just checked and it's not behaving that way for me; it's still going to the HTML. (MacFF 34, FB 2.0.8). On Fri, Feb 6, 2015 at 3:25 PM, Nicholas Shewmaker nshewma...@gmail.com wrote: In 2.0.7, clicking on the inspect button switches immediately to the HTML tab. In 2.0.8, clicking on a

Re: [firebug] Re: Firebug 3 - next generation of Firebug

I normally use the Firebug 2 debugger, but I've been comparing its behavior to that of Chrome and to the built-in Firefox debugger (all on a Mac, if that matters). One thing I've noticed is the difference in behavior when you mouse over a variable in a line of code that's already been run. In

Re: [firebug] Re: Comment out code in command line?

. -- Lawrence San Business Writing: Santhology.com Cartoon Stories for Thoughtful People: Sanstudio.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+unsubscr

[firebug] Comment out code in command line?

​I've got Firebug open in a separate split window, with the Console on the left and the large command-line area on the right. I'm experimenting with a function, but it's awkward compared to my text editor, because in Firebug the only way I know how to comment (or un-comment) lines ​of code is by

Re: [firebug] Re: Firebug 3 - next generation of Firebug

Oh... I already know about the filtering *buttons*; I didn't realize he was referring to one of them. I'm already filtering with the Images button. That works, but it's insufficient for my situation, because there's a humongous list of images on the page. I was referring to my attempts to filter

Re: [firebug] Re: FF34 FB2.07 search fail

-46ee-8927-97f4694c43d1%40googlegroups.com https://groups.google.com/d/msgid/firebug/7ee75bc7-3e0a-46ee-8927-97f4694c43d1%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Lawrence San Business Writing: Santhology.com Cartoon

Re: [firebug] Re: Firebug 3 - next generation of Firebug

On Thu, Jan 29, 2015 at 3:08 PM, Richard Muse frm...@gmail.com wrote: As I just figured out, I can filter to XHR to get just the requests, so that helps as well. ​Do you literally mean filter -- that is, you only see the Net panel items you're interested in? Can you please explain how you do

[firebug] Change speed of JavaScript and Network for testing?

I ​'m currently using Firebug 2.07 with Mac Firefox 34. I'm trying to determine whether or not some complex code I'm working on has a race condition -- or, more broadly, whether the various dependencies have any timing problems. In addition to JS timers I'm using dom-ready type scripts a lot to

Re: [firebug] Re: Regexp search in Net panel

Thank you for the suggestions, Florent. I looked at the NetExport and Selenium pages, and it seems like they're for *saving files* from the network results. But I'm involved in a rapid-fire tweak/reload/view cycle -- I don't want to export and then view files, that seems too complicated and slow.

Re: [firebug] Re: Regexp search in Net panel

Hmm... even after googling the phrase blocking issue I'm still not exactly sure what it means... if I were part of the Firebug development team, I guess it would mean not going forward with a new version/release until that bug were fixed (?). But since I'm not part of that team... does it mean is

[firebug] Regexp search in Net panel

​I'm in Firebug's *Net* panel, with the *Images* button highlighted, and when I refresh the page a long list of my images shows up as expected. I'm trying to find only a few specific images in the list, using the search box in the upper-right corner. As long as I type in a literal part of the

Re: [firebug] I don't know where to begin

I've found that in talking to non-developers, using words like *structure*, *markup*, *presentation*, *style*, and *behavior* are just confusing. We're so familiar with those terms that we forget that they require a context that most people don't have. I've done a lot of tech writing aimed at

Re: [firebug] Not sure what it's called but it no longer works

Ah, I guess I misread adding elements to mean adding attributes. I tab to add a new attribute/value pair within an existing element. I never noticed those right-click options before. The Add Rule... makes sense to me: it creates a new rule for 'body' with blank braces, where I can change 'body' to

Re: [firebug] Not sure what it's called but it no longer works

I just tried it (current version of Mac Firefox and Firebug). I can still add elements by tabbing from the last element, or by double-clicking on the final semicolon. This works in both HTML pane's Style side-panel, and in the CSS pane. I checked it both on a page served from my own local/devel

[firebug] Scripts popdown menu is borked

In Mac FF 28 / Firebug 1.12.8, in the Scripts panel while debugging, I can pull down a menu to show me the relevant documents (the current HTML file, plus JS files linked to it). It works fine. In MacFF 32.0.2 / Firebug 2.0.4, that pulldown menu is borked. The most prominent things in it are two

[firebug] Script panel won't stop splitting itself

In Firebug 1.12.8, sometimes when I'm debugging (stepping through code starting from a single breakpoint I've set), I want the Script panel to remain the full width of my second monitor the whole time. In other words, currently I do *not* want to see the Watch, Stack, or Breakpoints panels *at

Re: [firebug] Re: No conditional inside Firebug console call

insert as underlined blue links, even though they're not links at all. I have no idea why. It's a little annoying. Do other people see parts of my code that way? Any idea how I can stop it from doing that? Thanks. Lawrence San Business Writing: Santhology.com Cartoon Stories for Thoughtful People

Re: [firebug] Re: sort console.log order by time.

to automatically group them (something like console.groupCollapsed) as soon as the next bunch of items appeared. Lawrence San Business Writing: Santhology.com Cartoon Stories for Thoughtful People: Sanstudio.com On Tue, Jul 8, 2014 at 1:44 AM, Jan Honza Odvarko odva...@gmail.com wrote

Re: [firebug] Re: Firebug 2.0 !

. Lawrence San Business Writing: Santhology.com Cartoon Stories for Thoughtful People: Sanstudio.com On Sun, Jun 22, 2014 at 8:52 PM, Glenn murphy.gl...@gmail.com wrote: The random numbers show up instantly when I do this, so it sounds like the speed problem *is* related to syntax highlighting

Re: [firebug] Re: Configure Editors

refer to? Lawrence San Business Writing: Santhology.com Cartoon Stories for Thoughtful People: Sanstudio.com On Sat, Jun 14, 2014 at 1:50 PM, Sebastian Zartner sebastianzart...@gmail.com wrote: Firebug currently (up to 2.0) does not offer mappings between URLs and local files. This feature

Re: [firebug] Re: Configure Editors

? Lawrence San Business Writing: Santhology.com Cartoon Stories for Thoughtful People: Sanstudio.com On Thu, Jun 12, 2014 at 11:14 AM, Andrei jon...@gmail.com wrote: Is the same problem I am acing on local machine. On localhost it doesn't do anything, however, it works on a remote URL. You can

[firebug] Configure Editors

From reading an earlier post in this group, I just discovered the Open With Editor command in Firebug, which I never noticed before. Background: I run a local devel server (Apache) on the same Mac that I use for browsing and editing web pages, so the server file and the local dev file is actually

Re: [firebug] Re: Stop debugger on a breakpoint in code outside of function

it there too, without having to open the side-panel and hunt around for that breakpoint. Lawrence San Business Writing: Santhology.com Cartoon Stories for Thoughtful People: Sanstudio.com On Fri, Jun 6, 2014 at 10:15 PM, Sebastian Zartner sebastianzart...@gmail.com wrote: If your code

Re: [firebug] Re: Serious problem with firebug

I was using firebug when the text showed up at the top of my page so I'm sure it's the cause Just because two things happen at the same time doesn't mean one of them caused the other one. Or, as the saying goes, correlation does not equal causation. Firebug did not cause your problem. It is not

  1   2   >