Settings->On Startup->Specific Page Selection not honored on multiple launches
Reported by
j...@prismnet.com,
Nov 11 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.89 Safari/537.36 Steps to reproduce the problem: 1. Create local disk blank.htm file and set it as start-up page in Settings->On Startup->Specific Page 2. Launch chrome. It is correctly displayed. 3. Shift->select to launch a second chrome. The selected file is not displayed. What is the expected behavior? Each new chrome launch should use the specified On Startup selection. What went wrong? Instead of the Startup selection, it displayed a google search page. Did this work before? Yes previous version Chrome version: 62.0.3202.89 Channel: stable OS Version: 10.0 Flash Version:
,
Nov 14 2017
Able to reproduce this issue on reported version 62.0.3202.89, latest stable 62.0.3202.94 and latest Canary 64.0.3267.0 using Windows 10, Ubuntu 14.04 and Mac 10.12.6. The issue is seen from M-50 (50.0.2641.0). Hence considering this issue as Non-Regression, removing Needs-bisect label and marking it as Untriaged.
,
Nov 14 2017
+tmartino
,
Nov 14 2017
Hi, thanks for the report. If Chrome is already running, we generally treat launching a new window similarly to opening a new tab. The startup pages are just that--used when Chrome is first starting up. I can see some arguments for treating it differently, but I don't think anything has really changed since this was originally designed a long time ago, and it would be a deceptively big undertaking. There are also lots of extensions already out there that do a capable job of changing New Tab/New Window behavior. |
||||
►
Sign in to add a comment |
||||
Comment 1 by manoranj...@chromium.org
, Nov 13 2017