Robert Sesek | 1 May 2012 01:17

Deprecating Mac OS X 10.5

Hi folks,


We're starting the process of deprecating Mac OS X 10.5 in M22, making 10.6 the minimum system version on which Chrome will run. Starting in M20 we will notify users, and M21 will be the last stable version to receive updates. In M22 the build SDK will be changed to 10.6. This should not affect developers, as the chrome target hasn't been able to build/link on 10.5 for over a year.

Let me know if you have any questions.

rsesek / <at> chromium.org

--
Chromium Developers mailing list: chromium-dev <at> chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
Marc-Antoine Ruel | 1 May 2012 01:49
Gravatar

Re: if you get the svnversion error while gclient sync'ing (windows)

As written in http://dev.chromium.org/developers/how-tos/install-depot-tools , it is preferable to not mix and match cygwin and non-cygwin executable.


Either use cygwin's version of python, svn and git or don't.

But as long as it works for you, I don't really mind.

M-A

2012/4/30 Michael Nordman <michaeln <at> google.com>
On my system, cygwin's svnversion was being invoked (which failed
since i don't use depot tools in cygwin from chrome, only webkit). I
fixed this by explicitly putting chrome_depot_tool/svn_bin in my path
in front of cygwin/bin so the unprefixed invocation from somewhere in
gyp found the right copy.

On Mon, Apr 30, 2012 at 1:11 PM, Carlos Pizano <cpu <at> chromium.org> wrote:
> Like so:
>
> Updating projects from gyp files...
> 'svnversion' is not recognized as an internal or external command,
> operable program or batch file.
> Traceback (most recent call last):
>  File "src/build/gyp_chromium", line 171, in <module>
> .....
> blah blah..
> .....
> Exception: Call to 'svnversion -n' returned exit status 1. while
> loading dependencies of src\third_party\ ... blah .. blah
>
>
> The solution is to delete depot_tools\svn.bat and run "gclient" again.
>
> --
> Chromium Developers mailing list: chromium-dev <at> chromium.org
> View archives, change email options, or unsubscribe:
>    http://groups.google.com/a/chromium.org/group/chromium-dev

--
Chromium Developers mailing list: chromium-dev <at> chromium.org
View archives, change email options, or unsubscribe:
   http://groups.google.com/a/chromium.org/group/chromium-dev

--
Chromium Developers mailing list: chromium-dev <at> chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
Yue Zhang | 1 May 2012 01:55
Picon
Favicon

Image Extraction Question

Hi,

   I'm new to chromium development. I want to extract all the images
(position, size, and raw data) from a webpage (from a renderer
process). A straight forward way I can think of is walking through the
WebElements in DOM document and do something like:

   If (element.HasTagName("img")
     // do something

   Now my question is:

   (1) Where to get the raw data of the image? I saw there is library
called ImageResourceFetcher but I thought a renderer process should
already download the image and I should not do it myself again?

   (2) Can this method get the css background image (and any other
style images)? If not, how to get the css images?

   Any suggestions/answers are greatly appreciated.

   Thanks,

Yue

--

-- 
Chromium Developers mailing list: chromium-dev <at> chromium.org
View archives, change email options, or unsubscribe: 
    http://groups.google.com/a/chromium.org/group/chromium-dev

Gabriel Charette | 1 May 2012 16:01

Re: Deprecating Mac OS X 10.5

Does that mean Chrome will no longer work on MAC OS X 10.5?!?! 10.5 is newer (some Macs shipped with it less than 3 years ago) than XP which we still support.

Or are we simply building with 10.6 SDK which is (?) backward compatible with 10.5 SDK?

Thanks for clarifying, seems to me like it's too early to deprecate Mac OS X 10.5,
Gab

On Mon, Apr 30, 2012 at 7:17 PM, Robert Sesek <rsesek <at> chromium.org> wrote:
Hi folks,

We're starting the process of deprecating Mac OS X 10.5 in M22, making 10.6 the minimum system version on which Chrome will run. Starting in M20 we will notify users, and M21 will be the last stable version to receive updates. In M22 the build SDK will be changed to 10.6. This should not affect developers, as the chrome target hasn't been able to build/link on 10.5 for over a year.

Let me know if you have any questions.

rsesek / <at> chromium.org

--
Chromium Developers mailing list: chromium-dev <at> chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

--
Chromium Developers mailing list: chromium-dev <at> chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
Mark Mentovai | 1 May 2012 16:06

Re: Deprecating Mac OS X 10.5

Gabriel Charette wrote:
Does that mean Chrome will no longer work on MAC OS X 10.5?!?!

Yes.

--
Chromium Developers mailing list: chromium-dev <at> chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
Gregg Tavares (勤 | 1 May 2012 18:58
Picon
Favicon

Re: Deprecating Mac OS X 10.5

So this is probably a stupid question but we just stop auto upgrading people on 10.5? right? Chrome doesn't suddenly update itself to a version that doesn't run anymore right?

Also, any plans to keep around an old version for 10.5 users? Maybe the installer can warn them they're getting an old version?



On Tue, May 1, 2012 at 7:06 AM, Mark Mentovai <mark <at> chromium.org> wrote:
Gabriel Charette wrote:

Does that mean Chrome will no longer work on MAC OS X 10.5?!?!

Yes.

--
Chromium Developers mailing list: chromium-dev <at> chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

--
Chromium Developers mailing list: chromium-dev <at> chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
Robert Sesek | 1 May 2012 19:00

Re: Deprecating Mac OS X 10.5

On Tue, May 1, 2012 at 12:58 PM, Gregg Tavares (勤) <gman <at> google.com> wrote:
So this is probably a stupid question but we just stop auto upgrading people on 10.5? right? Chrome doesn't suddenly update itself to a version that doesn't run anymore right?

Correct. M21 will continue to run without issue, and we just won't autoupdate users to M22 if they're on 10.5. 
 
Also, any plans to keep around an old version for 10.5 users? Maybe the installer can warn them they're getting an old version?

This I'm not sure about.

rsesek / <at> chromium.org 

--
Chromium Developers mailing list: chromium-dev <at> chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
Ryan Hamilton | 1 May 2012 19:13

Fwd: Delivery Status Notification (Failure)

[from the right address]

On Tue, May 1, 2012 at 10:00 AM, Robert Sesek <rsesek <at> chromium.org> wrote:
 > On Tue, May 1, 2012 at 12:58 PM, Gregg Tavares (勤) <gman <at> google.com>wrote:
>
>> So this is probably a stupid question but we just stop auto upgrading
>> people on 10.5? right? Chrome doesn't suddenly update itself to a version
>> that doesn't run anymore right?
>>
>
> Correct. M21 will continue to run without issue, and we just won't
> autoupdate users to M22 if they're on 10.5.

Do we know how many users we will be stranding on M21 as a result of this
deprecation?

Cheers,

Ryan

--
Chromium Developers mailing list: chromium-dev <at> chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
Ojan Vafai | 1 May 2012 20:48

Re: Deprecating Mac OS X 10.5

On Tue, May 1, 2012 at 10:00 AM, Robert Sesek <rsesek <at> chromium.org> wrote:
On Tue, May 1, 2012 at 12:58 PM, Gregg Tavares (勤) <gman <at> google.com> wrote:
So this is probably a stupid question but we just stop auto upgrading people on 10.5? right? Chrome doesn't suddenly update itself to a version that doesn't run anymore right?

Correct. M21 will continue to run without issue, and we just won't autoupdate users to M22 if they're on 10.5. 

FWIW, when we did this on Linux, we infobarred warning that the browser was no longer being updated. Given that having an out of date browser is having an insecure browser, we thought it was worth putting it in the user's face. So, if we were to do this on 10.5, M21 would infobar on 10.5.

Ojan

--
Chromium Developers mailing list: chromium-dev <at> chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
Mark Mentovai | 1 May 2012 20:51

Re: Deprecating Mac OS X 10.5

Ojan Vafai wrote:
On Tue, May 1, 2012 at 10:00 AM, Robert Sesek <rsesek <at> chromium.org> wrote:
On Tue, May 1, 2012 at 12:58 PM, Gregg Tavares (勤) <gman <at> google.com> wrote:
So this is probably a stupid question but we just stop auto upgrading people on 10.5? right? Chrome doesn't suddenly update itself to a version that doesn't run anymore right?

Correct. M21 will continue to run without issue, and we just won't autoupdate users to M22 if they're on 10.5. 

FWIW, when we did this on Linux, we infobarred warning that the browser was no longer being updated. Given that having an out of date browser is having an insecure browser, we thought it was worth putting it in the user's face. So, if we were to do this on 10.5, M21 would infobar on 10.5.

This is already part of the plan. We’ll notify via New Tab Page in Chrome 20, and infobar in Chrome 21. 10.5 users won’t get the update to Chrome 22. Chrome 22 won’t launch on 10.5 at all, but the OS will show a dialog saying that the system doesn’t meet the application’s minimum requirements.

--
Chromium Developers mailing list: chromium-dev <at> chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

Gmane