Live data from Hacker News

Future of Firefox DevTools

paulrouget.com

91–100 of 170 posts

Re: Future of Firefox DevTools

#91
post #26

I still don't get it way mozilla made it's own devtools, instead of integrating and extending on firebug. Had the devs of mozilla and the one of firebug diffs, which couldn't be solved?

At the time, yes.

In particular, there were somewhat irreconcilable differences in goals and priorities...

Re: Future of Firefox DevTools

#92

Earlier quoted context omitted.

What setting do you change?

[] Use a prediction service to help complete searches and URLs typed in the address bar Maybe that one.

So that's why every time I start typing a reddit url, Chrome suggests I visit http://www.reddit.com/r/gone wild (sic, with the space in there).

There are a number of reasons why they really need to rethink this, default it off, or do some better filtering. Didn't impact me personally beyond the confusion but I could imagine that URL and maybe some others coming up in what appears to be someone's unique search or browsing history raising some interesting questions at work and/or at home for some users.

Re: Future of Firefox DevTools

#93

Earlier quoted context omitted.

Haha, I just switched from Chrome to Firefox because I hate how Chrome prioritizes Google Search over my previous history. It's idiotic. Here, let me show you a clear example. http://i.imgur.com/uNsh7Yv.png Firefox clearly has the superior bar.

I've personally internalized the downdown for going to things I've gone to before. However, I do brand new searches constantly . Often 20+ a day, that often look similar to older searches, but aren't quite. Now, whether I've developed that behavior because of Chrome, or because it works well for me, is a question for itself. Also, since I'm here- anyone get frequent fuckups lately in the Chrome omnibar, not searching…

Is it associated with Google Instant failing?

I've noticed frequently Google Instant will fail half way through searching, and it will ignore everything I typed and just go with what Instant guessed before it crapped out.

If Instant is prioritizing your previous search, it may be linked.

Re: Future of Firefox DevTools

#94
post #9

At the moment, I really like Chrome because I just find the behavior of the Omnibar superior to Firefox's Awesomebar. But hot damn, you're making me question loyalties on my dev machine.

I like how Firefox completes the site I want with only typing 1 or 2 characters in the address bar. Also Firefox has a separate search bar that supports plugins (dictionaries, CPAN and stuff like that)

Re: Future of Firefox DevTools

#95
I'm loving all of this. With these improvements, I have only one complaint. The tab bar is beautiful on Windows and OS X, but it's awful on Linux. Tabs should be the same on each OS.

Re: Future of Firefox DevTools

#97
post #9

At the moment, I really like Chrome because I just find the behavior of the Omnibar superior to Firefox's Awesomebar. But hot damn, you're making me question loyalties on my dev machine.

Like sergiotapia, I'm very close to switching back to FireFox /because/ of the Awesomebar. However, for me, it's because it matches my search history better. Let's say I'm working on a page call /editor/?id=1234, in FireFox, typing 1234 will show that page as the first match, whereas Chrome doesn't even match it unless I start typing /editor/, and sometimes even the root domain. It's very frustrating.

HackerNews is the best example for me. In firefox, I can type in y, and it will know that I want news.ycombinator.com. In Chrome, the only way to have it autocomplete (at least the last time I tried it) was to start with n.

Re: Future of Firefox DevTools

#98

Earlier quoted context omitted.

I kind of disagree, I would rather see Firefox DevTools not be Firebug. Firebug is not that great (compared to Chrome's debug tools) due to its UI. It looks like Firefox DevTools is at least going for a much better UI, so being constrained by Firebug would be a loss.

I still prefer Firebug, instead of Chrome dev tools. What are the reasons which make you think, it is not great?

Firebug:

-is slower

-has more glitches (things doing plain weird or not working sometimes)

-requires "activation" of each panel and reloading of the page

-sometimes suddenly opens for no reason when you visit a webpage without the intention to debug it

-is impossible to use if you want to debug a project with hundreds of js files (e.g. uncompiled JS of a large project) because it has a bad type of dropdown for selecting the JS file

-generally just requires more clicks and more frustration to get things done

The one in Chrome:

-is faster

-has a better console (easier to type commands, inspect variables, etc...)

-works immediately as soon as you open it (no "this panel was inactive during page load")

-has more features

Note that I was talking about Firebug here. Firefox also has its own dev tools, at least an "Inspect Element", with even a 3D view of a page allowing to see divs outside of it and so on, and that one is awesome!

I'm curious from your side (maybe also to learn a thing or two about Firebug): How would you compare it to Chrome? What features make Firebug stand out?

Thanks.

EDIT: Why do I need to add multiple newlines between the "-" to make Hacker News post them as newlines?

Re: Future of Firefox DevTools

#100
post #9

At the moment, I really like Chrome because I just find the behavior of the Omnibar superior to Firefox's Awesomebar. But hot damn, you're making me question loyalties on my dev machine.

Haha, I just switched from Chrome to Firefox because I hate how Chrome prioritizes Google Search over my previous history. It's idiotic. Here, let me show you a clear example. http://i.imgur.com/uNsh7Yv.png Firefox clearly has the superior bar.

Also, putting "* " in the awesomebar before typing searches your search string limits the results to bookmarks. Here is a list of these prefixes: Add ^ to search for matches in your browsing history. Add * to search for matches in your bookmarks. Add + to search for matches in pages you've tagged. Add % to search for matches in your currently open tabs. Add ~ to search for matches in pages you've typed. Add # to search for matches in page titles. Add @ to search for matches in web addresses (URLs).
Post reply on HN