Live data from Hacker News

Google Chrome 4 now natively supports Greasemonkey user scripts

blog.chromium.org

21–30 of 51 posts

Re: Google Chrome 4 now natively supports Greasemonkey user scripts

#23

I only wish Chrome would add a second search box, like IE and FF do. I have never figured out how to get the keyword for another search engine (Wikipedia) to work satisfactorily in Chrome's combination url/search entry area.

Works for me. In preferences, manage search engines. All or most of the search engines you've used in the past should be there. Edit the keyword to the keyword of your choice (for Wikipedia I use "wp"). In the omni bar, type "wp", space, query, enter. Alternatively you can use a tab instead of a space and this makes it more obvious that you are searching.

Re: Google Chrome 4 now natively supports Greasemonkey user scripts

#24

I only wish Chrome would add a second search box, like IE and FF do. I have never figured out how to get the keyword for another search engine (Wikipedia) to work satisfactorily in Chrome's combination url/search entry area.

In Chrome, you can also use domain specific searches: start typing the domain name, and when autocomplete matches the domain, press tab, and the location bar becomes a site-specific search. e.g:

    ul  
expands to ultimate-guitar.com to search for guitar tabs

    en  
expands to en.wikipedia.org to search wikipedia

It's great that it automatically picks up search boxes in websites. So this works on any website that you have searched in the past - you don't have to manually set it up.

Re: Google Chrome 4 now natively supports Greasemonkey user scripts

#25
Does not anyone else get really let down every time they read a Chrome submission that doesn't announce that Firebug has been ported over?

I've started using Chrome for my day to day browsing, but I'll never be able to wholeheartedly switch until Firebug arrives.

Re: Google Chrome 4 now natively supports Greasemonkey user scripts

#26

Does not anyone else get really let down every time they read a Chrome submission that doesn't announce that Firebug has been ported over? I've started using Chrome for my day to day browsing, but I'll never be able to wholeheartedly switch until Firebug arrives.

Chrome comes with the element inspector built in which replicates a lot of the functionality of Firebug.

Re: Google Chrome 4 now natively supports Greasemonkey user scripts

#27
post #26

Does not anyone else get really let down every time they read a Chrome submission that doesn't announce that Firebug has been ported over? I've started using Chrome for my day to day browsing, but I'll never be able to wholeheartedly switch until Firebug arrives.

Chrome comes with the element inspector built in which replicates a lot of the functionality of Firebug.

The element inspector is handy, but personally I would also need JavaScript step through debugging like Firebug provides.

Re: Google Chrome 4 now natively supports Greasemonkey user scripts

#28

I only wish Chrome would add a second search box, like IE and FF do. I have never figured out how to get the keyword for another search engine (Wikipedia) to work satisfactorily in Chrome's combination url/search entry area.

I wish all other browsers would drop the unnecessary secondary box when they could be doing the searching in the address bar like Chrome.

Re: Google Chrome 4 now natively supports Greasemonkey user scripts

#29

I've been a big firefox fan since phoenix, but already moved to chrome for only one reason: Fastest...browser...evar

Chrome is the first browser that got me excited since I switched from IE to Firefox back in the day (or rather, phoenix and then Firebird...).

Back in my Slackware days, I loved the rendering of Konqueror/KHTML, so when I got a Mac I started using Safari. I was good, but didn't really excite me. Just competent stuff..

But Chrome. Now that's pushing things forward! Firefox is so slow and bloated on the Mac, I only use it for Stumbleupon.

Re: Google Chrome 4 now natively supports Greasemonkey user scripts

#30
post #26

Does not anyone else get really let down every time they read a Chrome submission that doesn't announce that Firebug has been ported over? I've started using Chrome for my day to day browsing, but I'll never be able to wholeheartedly switch until Firebug arrives.

Chrome comes with the element inspector built in which replicates a lot of the functionality of Firebug.

The element inspector comes somewhat close, but you can't add css attributes to selectors, only modify existing ones, which really makes the thing useless when doing front end dev
Post reply on HN