In Progress
Status Update
No update yet.
Comments
yu...@google.com
bl...@google.com
Assigning to dpenning to consolidate Chromium bugs under one account.
Automated by Blunderbuss job top-chrome-blunderbuss-autoassigner for 7th config for component 1363614.
Automated by Blunderbuss job top-chrome-blunderbuss-autoassigner for 7th config for component 1363614.
ch...@google.com
The Found In field may only contain numeric values. Some values were corrected. You can see the changes by toggling full history on the issue.
dp...@google.com
This is working as intended, the group should wait for the backend to make the change before destroying. we are introducing a new UI in the next week that will have a spinner for this.
dp...@google.com
assigning to yuheng since he's already working on the delay, but this should be able to be closed out once the sharekit collab service integration is done.
Description
Revision:a75548d15f8282e45b31303619cfd1ad5cb4d0fe-refs/branch-heads/7081@{#1}
OS: Windows, Mac
Pre-Requisite:
Chrome://flags
1. Data sharing->enable
2.Tab Group Sync Service Desktop Migration->enable
Steps:
1. Launch Chrome and SignIn
2. open NTP and create group
3. right click on tab group icon and click on "Share tab group" in tab strip
4. Share tab group bubble open and click on "Copy link" button
5. close "share tab group" bubble and right click on tab group icon
6. click on delete group
7. Observe that the delay in deleting shared tab group when you click on the delete group
Actual Result:
1.The shared tab group was not deleted immediately(time delay) when you click on the delete group
Expected Result:
1.The shared tab group should be deleted immediately when you click on the delete group
Please find bisect info below:
This is a regression issue broken in M135, and please find per revision-bisect info below:
Good Build : 135.0.7022.0
Bad Build : 136.0.7081.0
Please find bisect info below:
You are probably looking for a change made after 1421481 (known good), but no later than 1421482 (first known bad).
CHANGELOG URL:
Suspect:
@dp...@chromium.org, Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.
Please refer to the Screencast links below:
Bad build:
Good build:
Note:1.This issue is not able to reproduce on Stable #134.0.6998.89
2. This issue is able to reproduce in Dev #136.0.7064.0 and Beta RC#135.0.7049.28
Thanks..!!