Beta Update: Translate for the Mac

Thursday, March 25, 2010 | 16:33

Labels:

Google Chrome 5.0.342.7 has been released to the Beta channel for Mac users (we released Linux yesterday). The highlights for Mac are basically the same, with the addition of Full Screen view working.


We finally have automatic translation for all Beta users.


Highlights:

  • Automatic translations and greater control over content for privacy. The Google Chrome 4.1 Beta announcement for Windows explains these features in more detail.
  • Full screen mode
  • Really, really reload. A normal reload causes the browser to check with the server before reusing its cached content.  The server can decide whether or not the browser should use its cached content.  A force reload causes the browser to ignore its cached content and ask the server for a fresh copy of the page. Use Shift+Reload to force a reload (the reload keyboard shortcut varies by platform).
To get on the Beta channel, you can download Google Chrome from http://www.google.com/chrome?platform=mac.


If you find issues, please let us know by filing a bug.


--Mark Larson, Google Chrome Team 

24 comments:

Marcus said...

when's version 5 coming to the windows beta channel?

Yago said...

¿Bug?

http://dl.dropbox.com/u/60705/semaforoloco.mov

Kenny said...

I'm going to miss pinned tabs. They had some potential

Avinandan said...

Linux version needs more development?

joshuarudd said...

No more pinned tabs? :(

L. F. O. Martins said...

Please bring back Pinned Tabs ASAP! Pretty please

Matt Rogowski said...

Pinned tabs left the (Windows) dev channel for a while but came back, they're on dev now so they probably won't be gone long.

Gavin said...

I hate it when Chrome updates itself to a build without pinned tabs, I now have to go digging for the previous build and turn off autoupdate!

Grouchal said...

I also think that auto-update is a great feature within Chrome. I automatically get new features and security enhancements - well done Google!

Except when some idiot has removed functionality - such as pinned tabs.

Come guys pull your fingers out and QA a bit better - this is the beta channel not dev!

I know it hasn't been taken out on purpose because you make no mention of it above.

Ben said...

Are these weird bookmark menus on Mac Chrome here to stay? They look very out of place and are slower to appear, you should be trying to make it look more mac-like on the mac, not less! And my extensions seem to have strange dropshadows underneath them now that makes them harder to see.

Graeme said...

Pinned tabs are coming back and the auto-update mechanism is there to make sure all users are up to date with the latest security patches. Chill out.

Danny said...

Nice additions. But what happened to the mad padding of the bookmarks? Now a bookmark in the menu take up double the space for no reason besides lost overview.

I hope you revert back to the way it was beforehand. This just looks silly and makes the menus unnecessarily long.

Jug said...

Spaces WAY too great on Mac bookmark menus, as others have noted. Please reduce the spacing to be similar to the former builds. :(

The bookmark menus also have bugs when running out of vertical screen space. When I move to the very bottom, the auto-hiding dock appear instead, interfering... And when I move to the very top, bookmarks start scrolling and eventually mess up the entire menu.

I'm disappointed not more QA was done on this one before approving it for a beta release. This is dev channel quality IMHO.

Guido Rossi said...

This comment has been removed by the author.

Guido said...

I really like the new behavior of the bookmars that make bookmarks folders unfold when you click on one and move on the others. I was waiting for this, same as firefox. Much better than Safari!

Thanks!

Nick Chapin said...

Like those above, I HATE the new appearance of the bookmark folder menus. Feel flimsy, cheap, and out of keeping with the general mac interface. Really not sure I can live with this ... is there a way to change back??

andhra said...

I really love the translate feature

thanks Chrome team

Michael Nye said...

Love the full screen mode. But I can't stand the drag bar and the drop shadows you added to extensions on the toolbar. Can you add some way to disable these, or just get rid of them? They are ugly, and the shadows make it harder to see the icons.

The new pull down folder UI is ugly too; it should revert to standard Mac menus like in previous versions of chrome.

fede said...

I really hate the translation bar, please make it optional.. I'm getting irritated for this little thing, really annoying..

MDA said...

Bring back pin tabs and nix this ugly new UI. I Don't like the drop shadows on the extensions and the wonky spacing in the bookmark drop downs. Oh and did I mention pin tabs?!

Jay said...

Really, really, really dislike the new bookmark bar appearance/operation. I use my bookmark bar enough that the new design is pushing me to FF or Safari. Pls consider reverting this change! thanx

Tom said...

The new appearance of the bookmark dropdown menus is driving me insane. Why are they colored? I can't read my bookmarks anymore because all of a sudden they are colored to match my theme. What was wrong with the old menus?

Haze said...

Pinned tabs are back in the lastest chromium nightly but the terrible bookmark menus remain. They really really need fixing.

Gavin said...

This release really went way downhill in my opinion... many are complaining about this bookmark formatting issue, which I haven't notice because I rarely use bookmarks and never the bookmarks bar.

I mentioned further up that pinned tabs should not have been removed even for one release in my opinion. In addition, Chrome was running, so, so beautifully before this update, but now I'm constantly getting hanging pages when I try to interact with them before they're 100% loaded. Another serious issue that's come up with this release specifically is constant malfunctioning of the cursor state - a lot of the time, hovering over a linked element won't show the pointer associated with clickable elements, and hover-over JavaScript events often aren't triggered.

I really don't know how this made it past a nightly release, and THEN the dev releases.