chrome.tabs.onUpdated > changeInfo.title doesn't fire on history back/forward (button click)
Reported by
wolfw...@gmail.com,
Feb 4 2018
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36 Steps to reproduce the problem: 1. install extension from attached file in developer mode 2. open background page 3. observe console What is the expected behavior? when back button is pressed, tab title is changed... and that new title should be logged on console What went wrong? no event in tabs API (change in title) when back/forward button is pressed Did this work before? N/A Does this work in other browsers? N/A Chrome version: 64.0.3282.140 Channel: stable OS Version: 10.0 Flash Version: if event is fired on any title change, it should also fire when user clicks back/forward button
,
Feb 6 2018
Unable to reproduce the issue on Win-10 using chrome reported version #64.0.3282.140 and latest canary #66.0.3340.0. Attached a screen cast for reference. Following are the steps followed to reproduce the issue. ------------ 1. installed extension from attached file in developer mode 2. opened background page 3. observed console and found that a new tab event is fired. 4. Pressed back arrow at the top left corner and observed that a new tab event is again fired. reporter@ - Could you please check the screen cast and please let us know if anything missed from our side. Also please check the issue on latest canary #66.0.3340.0 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not. Thanks...!!
,
Feb 6 2018
@krajshree Problem is not in new tab (or returning to it from arbitrary page) When you open some page, and follow link or two (or more), when you click back button, "changeInfo.title" is not fired (same for forward button). So you need to open some eg. portal, click on any link AND THEN click back button. In that case, new title won't be logged on console
,
Feb 6 2018
Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 8 2018
Able to reproduce this issue on Mac 10.13.3, Win-10 and Ubuntu 14.04 using chrome latest stable #65.0.3325.146 and latest canary #67.0.3365.0. This is a non-regression issue as it is observed from M60 old builds. Hence, marking it as untriaged to get more inputs from dev team. Thanks...!! |
||||
►
Sign in to add a comment |
||||
Comment 1 by krajshree@chromium.org
, Feb 4 2018