Jump to content



Photo

Meet Chrome Next

chrome

670 replies to this topic

#181 +Zlip792

Zlip792

    Neowinian Senior

  • Tech Issues Solved: 16
  • Joined: 31-October 10
  • Location: Pakistan
  • OS: Windows 8.1 Pro 64-bit
  • Phone: Nokia C3-00 (8.70 firmware)

Posted 08 January 2013 - 12:31

New menu look (might be some about:flags stuff (since I turned on many yesterday and feeling tired to find which one enabled it or might be work in progress):
Posted Image
Posted Image


#182 torrentthief

torrentthief

    Neowinian Senior

  • Joined: 18-November 06

Posted 08 January 2013 - 12:36

new dev build and beta build were released yesterday.

#183 +Frank B.

Frank B.

    Member N° 1,302

  • Tech Issues Solved: 12
  • Joined: 18-September 01
  • Location: Frankfurt, DE
  • OS: OS X 10.10
  • Phone: iPhone 6

Posted 10 January 2013 - 18:23

Stable Channel Update

The Chrome team is excited to announce the promotion of Chrome 24 to the stable channel. Chrome 24.0.1312.52 has been updated for Windows, Mac, Linux, and Chrome Frame.

This is the first Stable release with support for MathML, thanks to WebKit volunteer Dave Barton. This release also contains an update to Flash (11.5.31.137) as well as improvements in speed and stability. You can find out more about Chrome 24 on the Official Chrome Blog and the Official Chromium Blog.

Security fixes and rewards:

Please see the Chromium security page for more detail. Note that the referenced bugs may be kept private until a majority of our users are up to date with the fix.
  • [$1000] [162494] High CVE-2012-5145: Use-after-free in SVG layout. Credit to Atte Kettunen of OUSPG.
  • [$4000] [165622] High CVE-2012-5146: Same origin policy bypass with malformed URL. Credit to Erling A Ellingsen and Subodh Iyenger, both of Facebook.
  • [$1000] [165864] High CVE-2012-5147: Use-after-free in DOM handling. Credit to José A. Vázquez.
  • [167122] Medium CVE-2012-5148: Missing filename sanitization in hyphenation support. Credit to Google Chrome Security Team (Justin Schuh).
  • [166795] High CVE-2012-5149: Integer overflow in audio IPC handling. Credit to Google Chrome Security Team (Chris Evans).
  • [165601] High CVE-2012-5150: Use-after-free when seeking video. Credit to Google Chrome Security Team (Inferno).
  • [165538] High CVE-2012-5151: Integer overflow in PDF JavaScript. Credit to Mateusz Jurczyk, with contribution from Gynvael Coldwind, both of Google Security Team.
  • [165430] Medium CVE-2012-5152: Out-of-bounds read when seeking video. Credit to Google Chrome Security Team (Inferno).
  • [164565] High CVE-2012-5153: Out-of-bounds stack access in v8. Credit to Andreas Rossberg of the Chromium development community.
  • [Windows only] [164490] Low CVE-2012-5154: Integer overflow in shared memory allocation. Credit to Google Chrome Security Team (Chris Evans).
  • [Mac only] [163208] Medium CVE-2012-5155: Missing Mac sandbox for worker processes. Credit to Google Chrome Security Team (Julien Tinnes).
  • [162778] High CVE-2012-5156: Use-after-free in PDF fields. Credit to Mateusz Jurczyk, with contribution from Gynvael Coldwind, both of Google Security Team.
  • [162776] [162156] Medium CVE-2012-5157: Out-of-bounds reads in PDF image handling. Credit to Mateusz Jurczyk, with contribution from Gynvael Coldwind, both of Google Security Team.
  • [162153] High CVE-2013-0828: Bad cast in PDF root handling. Credit to Mateusz Jurczyk, with contribution from Gynvael Coldwind, both of Google Security Team.
  • [162114] High CVE-2013-0829: Corruption of database metadata leading to incorrect file access. Credit to Google Chrome Security Team (Jüri Aedla).
  • [Windows only] [162066] Low CVE-2013-0830: Missing NUL termination in IPC. Credit to Google Chrome Security Team (Justin Schuh).
  • [161836] Low CVE-2013-0831: Possible path traversal from extension process. Credit to Google Chrome Security Team (Tom Sepez).
  • [160380] Medium CVE-2013-0832: Use-after-free with printing. Credit to Google Chrome Security Team (Cris Neckar).
  • [154485] Medium CVE-2013-0833: Out-of-bounds read with printing. Credit to Google Chrome Security Team (Cris Neckar).
  • [154283] Medium CVE-2013-0834: Out-of-bounds read with glyph handling. Credit to Google Chrome Security Team (Cris Neckar).
  • [152921] Low CVE-2013-0835: Browser crash with geolocation. Credit to Arthur Gerkis.
  • [150545] High CVE-2013-0836: Crash in v8 garbage collection. Credit to Google Chrome Security Team (Cris Neckar).
  • [145363] Medium CVE-2013-0837: Crash in extension tab handling. Credit to Tom Nielsen.
  • [Linux only] [143859] Low CVE-2013-0838: Tighten permissions on shared memory segments. Credit to Google Chrome Security Team (Chris Palmer).
Many of the above bugs were detected using AddressSanitizer.

The security issues in V8 have been fixed in v8-3.14.5.3.

We’d also like to thank Atte Kettunen and Sławomir Błażek for working with us during the development cycle and preventing security regressions from ever reaching the stable channel. Rewards were issued.

Full details about what changes are in this build are available in the SVN revision log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug.

Dharani Govindan
Google Chrome


Source: Google Chrome Releases blog

#184 +Frank B.

Frank B.

    Member N° 1,302

  • Tech Issues Solved: 12
  • Joined: 18-September 01
  • Location: Frankfurt, DE
  • OS: OS X 10.10
  • Phone: iPhone 6

Posted 11 January 2013 - 08:27

Dev Channel Update

The Dev channel has been updated to 25.0.1364.29 for Windows, Mac, Linux, and Chrome Frame. This update contains additional stability fixes. A full list of changes in this build is available in the SVN revision log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug.

Jason Kersey
Google Chrome


Source: Google Chrome Releases blog

#185 +Frank B.

Frank B.

    Member N° 1,302

  • Tech Issues Solved: 12
  • Joined: 18-September 01
  • Location: Frankfurt, DE
  • OS: OS X 10.10
  • Phone: iPhone 6

Posted 14 January 2013 - 18:22

Chrome 25 promoted to Beta Channel:

Beta Channel Update

The Chrome team is happy to announce the promotion of Chrome 25 to the beta channel for Windows, Mac, Linux and Chrome Frame. Chrome 25.0.1364.29 contains a number of new improvements, including:
A full list of changes in this build is available in the SVN revision log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug.

Jason Kersey
Google Chrome


Source: Google Chrome Releases blog

#186 +Frank B.

Frank B.

    Member N° 1,302

  • Tech Issues Solved: 12
  • Joined: 18-September 01
  • Location: Frankfurt, DE
  • OS: OS X 10.10
  • Phone: iPhone 6

Posted 16 January 2013 - 05:35

Dev Channel Update

The Dev channel has been updated to 26.0.1384.2 for Windows, Mac, Linux, and Chrome Frame. This build contains improvements in stability and fixes for few other issues. Full details about what changes are in this build are available in the SVN revision log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug.

Dharani Govindan
Google Chrome


Source: Google Chrome Releases blog

The new menu look from Zlip792's post above is in this build. Not sure if like.

#187 ViperAFK

ViperAFK

    Neowinian Senior

  • Tech Issues Solved: 3
  • Joined: 07-March 06
  • Location: Vermont

Posted 17 January 2013 - 16:37

New menu look (might be some about:flags stuff (since I turned on many yesterday and feeling tired to find which one enabled it or might be work in progress):
Posted Image
Posted Image


wth? stick with native menus google!

#188 +Zlip792

Zlip792

    Neowinian Senior

  • Tech Issues Solved: 16
  • Joined: 31-October 10
  • Location: Pakistan
  • OS: Windows 8.1 Pro 64-bit
  • Phone: Nokia C3-00 (8.70 firmware)

Posted 17 January 2013 - 16:55

wth? stick with native menus google!


It been several chromium snapshots and it is still showing and sticking with this menu style, so I think they ditched that old menus and I disabled many about:flags as well.

#189 articuno1au

articuno1au

    Neowinian Senior

  • Tech Issues Solved: 3
  • Joined: 20-March 11
  • Location: Brisbane, Australia

Posted 17 January 2013 - 17:01

You can enable it. It's to do with touch sensitive interfaces flags.

If you override it it disables the funky menus.

Worry not ViperAFK.

#190 +Zlip792

Zlip792

    Neowinian Senior

  • Tech Issues Solved: 16
  • Joined: 31-October 10
  • Location: Pakistan
  • OS: Windows 8.1 Pro 64-bit
  • Phone: Nokia C3-00 (8.70 firmware)

Posted 17 January 2013 - 17:36

You can enable it. It's to do with touch sensitive interfaces flags.

If you override it it disables the funky menus.

Worry not ViperAFK.


Which flags enabled it, it is making my head fuzzy. Do tell me.

#191 +Frank B.

Frank B.

    Member N° 1,302

  • Tech Issues Solved: 12
  • Joined: 18-September 01
  • Location: Frankfurt, DE
  • OS: OS X 10.10
  • Phone: iPhone 6

Posted 18 January 2013 - 08:19

Dev Channel Update

The Dev channel has been updated to 26.0.1386.0 for Windows, Mac, Linux, and Chrome Frame. This build contains following updates:
  • Fixed marking notifications when opened and closed (Issue: 169388)
  • Fixed web popup menus (Issue: 166832)
  • Fixed renderer form_autofill_util changes to support Checkboxes and Radiobuttons (Issue: 157636)
  • Fixed decoding of URL in bookmark editor (Issue: 165648)
  • Added the preferences and UI to make the launcher opt-inable (Issue: 151676)
  • Added incognito visualization to items in the new app menu (Issue: 169842)
  • Renamed the magnifier names: "Full" -> "Entire screen", "Partial" -> "Lens" (Issue: 166832)
  • Enable webkit preference for Chromium to disallow unsafe plugin pasting (Issue: 112325)
  • Fixed thumbnail view on Drive (Issue 170022)
  • Fixed crash bug in BookmarkEditorView (Issue 167385)
Full details about what changes are in this build are available in the SVN revision log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug.

Tanya Radeva
Google Chrome


Source: Google Chrome Releases blog

You can enable it. It's to do with touch sensitive interfaces flags.

If you override it it disables the funky menus.

Worry not ViperAFK.

There is no way to disable the new-style menus as far as I can see.

#192 Jeroen S.

Jeroen S.

    Neowinian Vigilante

  • Tech Issues Solved: 1
  • Joined: 22-October 05
  • Location: The Netherlands
  • OS: Windows 8.1
  • Phone: iPhone 5

Posted 04 February 2013 - 14:42

For some reason my account was corrupted after a PC reboot yesterday. And now I can't seem to be able to log into my Google Chrome account. It shows me the account page and I login though it doesn't load the next page that's supposed to come up :s

Alright, fix it through the most obvious way: My account was still "signed in" but it asked for my password. I selected the option to sign in with a complete new account and re-entered my email and the corresponding password. Now it's logged in and all synced up again.

Edit: A question though. Has anyone had the Omnibox being part of a Google search page? Whenever I was searching on Google yesterday the Omnibox was part of the search page and the black bar of Google was gone (I hope I'm explaining this right). The Omnibox dropdown also looked a bit different and the "New Tab" page had a search field in it as well.

#193 ViperAFK

ViperAFK

    Neowinian Senior

  • Tech Issues Solved: 3
  • Joined: 07-March 06
  • Location: Vermont

Posted 04 February 2013 - 16:47

For some reason my account was corrupted after a PC reboot yesterday. And now I can't seem to be able to log into my Google Chrome account. It shows me the account page and I login though it doesn't load the next page that's supposed to come up :s

Alright, fix it through the most obvious way: My account was still "signed in" but it asked for my password. I selected the option to sign in with a complete new account and re-entered my email and the corresponding password. Now it's logged in and all synced up again.

Edit: A question though. Has anyone had the Omnibox being part of a Google search page? Whenever I was searching on Google yesterday the Omnibox was part of the search page and the black bar of Google was gone (I hope I'm explaining this right). The Omnibox dropdown also looked a bit different and the "New Tab" page had a search field in it as well.


Its a known bug in chrome 24+, happens to everyone afiak. It happened to me on a totally fresh install yesterday.

#194 Jeroen S.

Jeroen S.

    Neowinian Vigilante

  • Tech Issues Solved: 1
  • Joined: 22-October 05
  • Location: The Netherlands
  • OS: Windows 8.1
  • Phone: iPhone 5

Posted 05 February 2013 - 16:59

I liked it to be honest though I'd like it even more if it didn't screw around with Speed Dial 2 :p

#195 Steven P.

Steven P.

    aka Neobond

  • Tech Issues Solved: 88
  • Joined: 09-July 01
  • Location: Neowin HQ

Posted 27 February 2013 - 11:15

New menu look (might be some about:flags stuff (since I turned on many yesterday and feeling tired to find which one enabled it or might be work in progress):
Posted Image
Posted Image


This just landed in beta when I updated this morning. Still getting memory leaks and malformed pages after Chrome has been open all day. Seems there isn't a browser that can be open 24/7 and handle memory properly :/

Edit: by malformed pages, I mean just below the fold (visible area of the browser window) if I start scrolling before the web page has fully loaded, bits of the page will be "missing" showing only background. Text selecting the affected area makes that bit readable again. Fix is to close Chrome and then open it again, restoring tab sessions.

Maybe it's a known bug? I've had it for ages anyway. Bloody annoying!