chrome.tabs.move between windows makes pinned tabs unpinned
Reported by
andrey.k...@gmail.com,
Aug 21
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36 Steps to reproduce the problem: move a pinned tab to another window - it becomes unpinned. What is the expected behavior? It remains pinned. What went wrong? The pinned mode was not retained. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 68.0.3440.106 Channel: stable OS Version: 10.0 Flash Version:
,
Aug 28
Thanks for filling the issue... Unable to reproduce the issue on reported chrome version 67.0.3396.99 using Ubuntu 17.10. Attaching screenshot for reference. Steps: ------ 1. Launched reported chrome 2. opened some tabs and pinned all tabs 3. Moved left to right and right to left and also moved to new window As we are observed that pinned tabs are not being unpinned when drag to new window >It remains pinned @Reporter: Could you please check the attached screen cast and please let us know if anything missed from our end and also verify this issue with fresh profile that is not having any extensions and apps or reset all the flags. Let us know whether issue still persists. Thanks.!
,
Aug 28
Correcting the above comment #2, Tested and Unable to reproduce the issue on reported chrome version 68.0.3440.106 using Windows 10. Thanks..!
,
Aug 28
Hi, This issue is not about manual drag and drop, but when you move tabs via chrome.tabs API call - please see attached JavaScript code you can run from a Console where you have access to the Tab API.
,
Aug 28
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 5
andrey.kiyanovsky@ - Could you please provide a sample test file/url to test the issue from TE-end because as per comment #4 when running the code from the attached move-pinned.js file in console did not affect anything. This will help us in triaging the issue further. Thanks...!!
,
Sep 5
Hi, This is Extension API, so you need to run it from a console of an extension that has windows and tabs permissions. 1. Install my extension: https://chrome.google.com/webstore/detail/tabxpert-window-tab-manag/maomempcdmkfcjgeabecfpkebghcigac 2. Go to its background page 3. Run the code provided, you will get the following output: Source tab pinned: true Moved tab pinned: false Best regards, Andrey.
,
Sep 5
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 8
,
Nov 14
andrey.kiyanovsky@ Thanks for the update. Able to reproduce the issue on Windows 10, Mac OS 10.13.6 and Ubuntu 17.10 on the latest Stable 70.0.3538.102 and the latest Canary 72.0.3610.0 as per comment #7. This is a Non-Regression issue as this is observed from M-60 chrome builds. Attached is the screen shot for reference. Hence marking this as Untriaged for further updates from Dev. Thanks..
,
Nov 14
// Attaching screen shot for comment #10.
,
Nov 30
Drag moving a pinned tab between windows keeps that tab pinned, so I'd consider it as bug. /cc Kelvin if he wants to take a stab at it. TabsMoveFunction::Run() is probably the place to start looking at. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by susan.boorgula@chromium.org
, Aug 23