Google Chrome 2.0

Google Chrome 2.0.177.1

PS. Cum aflăm Versiunea?
Click sub "X", dreapta-sus (*cheia franceză*) > "About Google Chrome"... .

rsumy

Edited by rsumy, 04 May 2009 - 17:17.

Da, a facut si la mine update

Bai, mai usor cu updateurile Schimbari majore?

Uite schimbarile:

Google Chrome 2.0.177.1 has been released to the Dev channel.  

It includes a number of fixes and a couple UI tweaks.  For example, if you have searched from wikipedia.org in the past, start typing wikipedia.org in the omnibox, press the Tab key then a search term and suggestions and past searches will appear for Wikipedia.  Other fixes include:

    * [r14196] Scrollbars, Home/End work again in Gmail (Issue: 10009)
    * [r14377] Flash (and other plugins) can be installed without restarting the browser. (Issue: 10574)
    * [r14137] Fix hang seen in plugin process, including the new O3D plugin. (Issue: 10711)
    * [r13934] On some sites text disappears or is never drawn. For example, on Google Calendar, the titles for all day events do not display. (Issue: 9904)

Detailed release notes are available.  You can find out about getting on the Dev channel here: http://dev.chromium....ved/dev-channel.

If you find new issues, please let us know by filing a bug at http://code.google.c...um/issues/entry.

--Jonathan Conradt
Google Chrome Program Manager

2.0.180.0 s-a lansat cu intarziere din cauza lansarilor de beta si stable updates de saptamana trecuta.

1.Google Chrome has been updated to 2.0.180.0 on the dev channel.

Version Changes:

WebKit 530.9
V8 1.2.2.1

Visible changes:

    * [r14827] Support PgUp/PgDn in Omnibox for "first entry/last entry." (Issue: 6857)
    * [r15115] Tell the user if Chrome is not the default browser. (Issue: 9049)
    * [r15702] You can choose to allow pop-ups from a site. (Issue: 11440)

Other changes of note:

    * [r14891] Fix for crashing when zoomed into street level on maps.yahoo.com (Issue: 2044)
    * [r14731] Patch from Mohamed Mansour for systems without an installed printer. (Issue: 6835)
    * [r15020] Stop the location bar from flashing white when navigating from one HTTPS site to another. (Issue: 11157)
    * [r15214] Fix for common issues around opening a new window. (Issues: 6377, 6192, 835)
    * Lots of work around Extensions.  (See r15417, r15271, r15310)

The release notes are available as well as a detailed list of all revisions.

You can find out about getting on the Dev channel here: http://dev.chromium....ved/dev-channel.

If you find new issues, please let us know by filing a bug at http://code.google.c...um/issues/entry.

--Jonathan Conradt
Google Chrome Program Manager




2.[Edit, 11 May 2009: Change 'bandwidth' to 'test capacity'. Sometimes the colloquial jargon we use at work translates imprecisely for a public audience.]

We were not able to issue a Dev channel release this week. Our test team did a great job in qualifying two Stable udpates and a Beta update this week, and we just didn't have the test capacity to push a Dev channel release.


We'll get an update out early next week. Stay tuned for some exciting new features we hope to land in the Dev channel.


Mark Larson
Google Chrome Program Manager


PS: S-a modificat designul cand e pe tot ecranul , nu fullscreen (culoarea partii de sus)

Edited by hotwhells, 13 May 2009 - 14:21.

Google Chrome 2.0.180.0

PS1. Title Bar mi s-a făcut *negru*. La voi e la fel?
PS2. Cred că e vorba de asta... :

hotwhells, on May 13 2009, 15:08, said:

 111.jpg   105.99K   62 downloads

rsumy

Edited by rsumy, 13 May 2009 - 20:27.

Eu am actualizat la ultima versiune, nu sunt cine stie ce schimbari.

2.0.181.1 Title Bar este iarasi albastru .

Google Chrome has been updated to 2.0.181.1 on the dev channel.  This release contains many localization, crash, and ui behavior fixes.

Version Changes:

    * WebKit - 530.11
    * V8 - 1.2.4.1
    * Gears - 0.5.21.0

Changes:

    * Fixed a common crash when using a French spell-check dictionary. (Issue: 8551)
    * Fixed a regression where maximizing Chrome turned the tab-background black. (Issue: 11695)
    * Improved remote desktop (RDP) performance by using the standard dotted rectangle when moving a tab out. (Issue: 805)
    * The command line debugger has been replaced by a graphical debugger using the WebKit inspector scripts tab to debug Javascript running in V8.
    * It is now possible to set proxy setting from the command-line.  See the issue for more information. (Issue: 266)

The release notes are available as well as a detailed list of all revisions.

You can find out about getting on the Dev channel here: http://dev.chromium....ved/dev-channel.

If you find new issues, please let us know by filing a bug at http://code.google.c...um/issues/entry.
Jonathan Conradt
Engineering Program Manager

Edited by hotwhells, 21 May 2009 - 07:44.

Quote

Cand au introdus zoom-ul full image (sa nu mareasca doar textul) a fost un mare pas inainte, dar de ce nu poti sa pui tu nivelul default nu inteleg.
Imi place ca porneste repede, incarca site-urile rapid si ocupa putina memorie, dar sa dau "ctrl +" mereu pe ecranul de 22inch devine obositor.

Lipsa unor maruntisuri ca cea de sus + lipsa extensiilor arata ca mai are pana la maturitate. Totusi inceputul este f. promitor

p.s. dev channel user

Stable Update: Google Chrome 2.0.172.28
Thursday, May 21, 2009 | 11:00
Labels: Stable updates

We're promoting 2.0.172 from Beta to the Stable channel today.

We've made a lot of changes to stuff you never see, such as a newer version of WebKit for rendering web pages, a new network stack, and improvements to speed up the V8 Javascript engine.

There are some new features like removing Most Visited sites from the New Tab page, form autofill, and full screen mode.

We're also proud to announce that Google Chrome is now available in 50 languages. We added Bengali, Gujarati, Kannada, Malayalam, Marathi, Oriya (on Windows Vista only), Tamil, and Telugu in this release.

You can read more about it here.

--Mark Larson
Google Chrome Program Manager

-------------------------------------------------------------

Beta update: V8 experiment
Friday, May 22, 2009 | 12:19
Labels: Beta updates
Google Chrome 2.0.172.30 has been released to the Beta channel. The changes in this release since 172.27 are
complete translations in all languages
an experimental change in the V8 Javascript engine that might improve page load times for pages with a lot of Javascript.
a fix for a crash when using the French spell check dictionary (Issue 8551)
a fix for a crash when visiting a site with more than 50 feed links (Issue 12075)
You can join the Beta channel by downloading the Google Chrome Beta channer installer.

--Mark Larson
Google Chrome Program Manager

Edited by hotwhells, 24 May 2009 - 12:15.

E ok, e. E chiar ok de la ultima versiune pe care am încercat-o (adică 1). Doar un lucru-mi lipsește: *****. În rest numa' bine!

Stable update: 2 WebKit security fixes

Tuesday, June 9, 2009 | 12:47


Google Chrome's Stable channel has been updated to version 2.0.172.31 to fix two security issues in WebKit.

CVE-2009-1690 Memory corruption
A memory corruption issue exists in WebKit's handling of recursion in certain DOM event handlers. Visiting a maliciously crafted website may lead to a tab crash or arbitrary code execution in the Google Chrome sandbox. This update addresses the issue through improved memory management.

Severity: High. An attacker might be able to run arbitrary code within the Google Chrome sandbox.

Mitigations:

    * A victim would need to visit a page under an attacker's control.
    * Any code that an attacker might be able to run inside the renderer process would be inside the sandbox. Click here for more details about sandboxing.



CVE-2009-1718 Drag and drop information leak
An issue exists in WebKit's handling of drag events. This may lead to the disclosure of sensitive information when content is dragged over a maliciously crafted web page. This update addresses the issue through improved handling of drag events.

Severity: Medium. An attacker might be able to read data belonging to another web site, if a user can be convinced to select and drag data on an attacker-controlled site.

Mark Larson
Google Chrome Program Manager

Am si uitat de el

Merg numai pe v 3

Google Chrome 2.0.172.33 has been released to the Stable and Beta channels. This release fixes a critical security issue and two other networking bugs.

CVE-2009-2121: Buffer overflow processing HTTP responses
Google Chrome is vulnerable to a buffer overflow in handling certain responses from HTTP servers. A specially crafted response from a server could crash the browser and possibly allow an attacker to run arbitrary code.

More info:  http://code.google.c...detail?id=14508 (This issue will be made public once a majority of users are up to date with the fix.)

Severity: Critical. An attacker might be able to run code with the privileges of the logged on user.

Credit: This issue was found by the Google Chrome security team.

Other issues
This release also fixes two other network issues:
  - NTLM authentication to Squid proxies fails when trying to connect to HTTPS sites (Issue 8771)
  - Browser crash when loading some HTTPS sites (Issue 13226)
  
Mark Larson
Google Chrome Program Manager

Da , se misca mai bine ca Mozila !  

Stable, Beta update: Bug fixes
Thursday, July 16, 2009 | 11:42
Labels: Beta updates, Stable updates

Google Chrome 2.0.172.37 has been released to the Beta and Stable channels. This release fixes some minor bugs:
Fix: Solving captcha images broken at orkut.com. (Issue 15569)
Make forward/backward navigation work even when redirection is involved. (Issue 9663, issue 10531)
Fix: Daylight savings time not recognized for some CET locales. (Issue 12579)
Fix a browser crash on closing a URL request. (Issue 8942)
Update the V8 Javascript engine to version 1.1.10.14 to fix issues with regular expressions.
Update Gears to the latest release, 0.5.25.0.

In addition, this release fixes the following security issues:

Heap overflow with Javascript regular expressions

Evaluating a specially-crafted regular expression in Javascript on a web page can lead to memory corruption and possibly a heap overflow. Visiting a maliciously crafted website may lead to a renderer (tab) crash or arbitrary code execution in the Google Chrome sandbox.

More info: http://code.google.c...detail?id=14719 (This issue will be made public once a majority of users are up to date with the fix.)

Severity: High. An attacker might be able to run arbitrary code within the Google Chrome sandbox.

Credit: This issue was found by the Google Chrome security team.

Mitigations:
A victim would need to visit a page under an attacker's control.
Any code that an attacker might be able to run inside the renderer process would be inside the sandbox. Click here for more details about sandboxing.


Memory corruption in the browser process

A compromised renderer (tab) process could cause the browser process to allocate very large memory buffers. This error could cause the browser process (and all tabs) to crash or possibly allow arbitrary code execution with the privileges of the logged on user. To exploit this vulnerability, an attacker would need to be able to run arbitrary code inside the renderer process.

Severity: Critical. In conjunction with a vulnerability allowing arbitrary code to run in the renderer, an attacker might be able to run code with the privileges of the logged on user.

Credit: This issue was found by the Google Chrome security team.

Mitigations:
A victim would need to visit a page under an attacker's control.
The attacker must exploit a second vulnerability to control the renderer process.

 GC_3.jpg   43.72K   21 downloads


rsumy