New issue
Advanced search Search tips

Issue 793656 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Sep 13
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows
Pri: 1
Type: Bug-Regression


Show other hotlists

Hotlists containing this issue:
Hotlist-3


Sign in to add a comment

Fixed tabs are lost when Chrome is the default browser and an external app opens it to access a URL

Reported by gbae...@gmail.com, Dec 10 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.84 Safari/537.36

Steps to reproduce the problem:
1. Set Chrome as default browser in Windows 10;
2. Open Chrome and fix some tabs;
3. Fixed tabs are kept even after you close and open Chrome again;
4. Close Chrome;
5. Open a PDF file with an external link;
6. Click on the link;
5. Adobe reader opens chrome to access the URL, but the fixed tabs are gone.

What is the expected behavior?
Fixed tabs should be always kept (or backup up), doesn't matter how the browser is opened.

What went wrong?
When an external app opens chrome to access a URL, the fixed tabs are gone.

Did this work before? N/A 

Chrome version: 63.0.3239.84  Channel: stable
OS Version: 10.0
Flash Version: 

It also happens with other apps, when they try to download updates (not only with Adobe Reader).
 
Labels: Needs-Triage-M63 Needs-Bisect
Components: UI>Browser>TabStrip
Labels: -Type-Bug -Pri-2 -Needs-Bisect hasbisect-per-revision Triaged-ET M-65 OS-Linux Pri-1 Type-Bug-Regression
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on Windows 10 and ubuntu 14.04 using chrome reported version #63.0.3239.84 and latest canary #65.0.3292.0.
Issue is not seen in OS-Mac.

Bisect Information:
=====================
Good build: 58.0.2999.0    Revision(447413)
Bad Build : 58.0.3000.0    Revision(447669)

Note: Unable to provide per-revision bisect results, as opening a PDF file with an external link from the saved location as in step 5 of comment #0, invoked other chrome builds and did not open in the bisect tool invoked chrome builds. Hence, providing the change log from omahaproxy.

Change Log URL: (From Omahaproxy)
https://chromium.googlesource.com/chromium/src/+log/58.0.2999.0..58.0.3000.0?pretty=fuller&n=10000

Unable to find any possible suspect from the above CL. Hence, marking it as untriaged and requesting someone from dev team to please help us in assigning it to the right owner.

Thanks...!!
Status: Archived (was: Untriaged)
Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!

Sign in to add a comment