Live data from Hacker News

Future of Firefox DevTools

paulrouget.com

121–130 of 170 posts

Re: Future of Firefox DevTools

#121
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.

You can have a pretty close approximation on chrome with this plugin (fauxbar): https://chrome.google.com/webstore/detail/fauxbar/hibkhcnpka...

It searches your history and bookmarks too, which is what the awesome bar does.

Re: Future of Firefox DevTools

#123

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.

You can deactive this in chrome://settings/. I did it after your post. I find it also annoying.

I am surprised not a lot of people at HN do this. Disabling predictive service is one of the first things I do after installing chrome on a new machine. Something about sending every keystroke made on the omnibar to Google makes me feel uneasy, it could also be the paranoid in me talking.

Re: Future of Firefox DevTools

#124
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.

Your comparison would be stronger if you searched for the same string in both.

Re: Future of Firefox DevTools

#125

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…

(this is on a Mac)

In Firefox, the hotkey "cmd-K" will put focus into the search bar at the top.

In Chrome they don't have a keybind set to this by default (though on Windows they seem to). But if you open mac System Preferences, go to Keyboard, then Keyboard Shortcuts, and add an Application Shortcut for Chrome, you set the menu item name to "Search the Web..." and the keybind to whatever you want (I used "cmd-K").

So that way regardless if I'm in Firefox or chrome, pressing cmd-K will put me in a place I can search.

Re: Future of Firefox DevTools

#126
I was one of those that requested a way to profile repaints. Thank you for adding the aggregate repaint view. The video showing the margin-left vs. transform repaints is exactly the kind of thing developers can take advantage of.

Question: does the aggregate repaint view indicate what caused the repaint? Determining that isn't always as easy or obvious as the margin-left vs. transform example in the video, so it'd be a huge benefit if that was included.

Thank you for listening!

Re: Future of Firefox DevTools

#127
post #97

Earlier quoted context omitted.

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.

I always visit by going to hackerne.ws, so I hit H in Chrome.

Re: Future of Firefox DevTools

#129

Earlier quoted context omitted.

Because the OP was pointing to Sublime as an example of a tool that is available, and popular, cross-platform.

If that were the case, then the OP would have no argument because that's the only external tool being shown right now.

On re-reading, I've now realized polskibus was referring to sublime as a tool which IS available cross platform.

Like the downvoted comment I too initially read it as that he thought it WAS NOT cross platform based on thee here he postitioned his example near his Apple comment and hence why the 'sublime is available cross platform' comment made good sense to me.

Post reply on HN