Status: Assigned Owner: [EMAIL PROTECTED] Labels: Type-Bug Pri-2 OS-All Area-Misc Regression
New issue 5109 by [EMAIL PROTECTED]: Regression: About Chromium no longer blocked on directory check http://code.google.com/p/chromium/issues/detail?id=5109 What steps will reproduce the problem? 1. Install Chromium alongside Google Chrome and run Chromium. 2. Go to About Chromium 3. Notice that it no longer displays error 1, but instead launches the COM component that tries to update Google Chrome. We have a function CanUpdateCurrentChrome() that used to check if we are installed in a location where Google Chrome would be installed. This function would return false if run from Chromium (or from a developer build built by VS). It uses GetChromeInstallPath() which used to just return the Chrome install path, but has been changed to return the Chrome or Chromium install path (depending on what you are running). As a result, we now no longer abort during the directory test and launch the COM component to try to update. This probably will result in Google Chrome being updated from within Chromium. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-bugs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
