With --enable-fast-unload, some events are lost for some extensions to correctly acquire the currently available tabs
Reported by
innatere...@gmail.com,
Aug 16 2017
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3178.0 Safari/537.36 Steps to reproduce the problem: 1. Install Vimium and enable chrome://flags/#enable-fast-unload, restart Chrome. 2. Open three tabs, A, B, and C. (must all be web pages so extensions can work on) 3. From tab A, switch to tab B, then switch to tab C. 4. Close tab B. 5. Hit ^ key. (the number 6 key with Shift) What is the expected behavior? Switch to tab A. As ^ is the Vimium hotkey to switch between most recently used tabs, and with tab B closed, tab A is now the most recently used tab. What went wrong? Nothing happens. Vimium is not informed that tab B has been closed. WebStore page: https://chrome.google.com/webstore/detail/vimium/dbepggeogbaibhgnhhndojpepiihcmeb Did this work before? N/A Chrome version: 62.0.3178.0 Channel: dev OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: This only repros when running Chrome with --enable-fast-unload. Please see below for technical details explained by the Vimium developer. https://github.com/philc/vimium/issues/2567
,
Aug 17 2017
Correction: the direct link to the technical details is https://github.com/philc/vimium/issues/2567#issuecomment-321522700
,
Aug 18 2017
Tested on Chrome Stable #60.0.3112.101, Canary #62.0.3188.0, reported Dev #62.0.3178.0 on Windows 7, Mac 10.12.6, Ubuntu 14.04 and able to reproduce the issue. This is a non-regression issue and able to reproduce from M-45 #45.0.2454.85. Marking it as untriaged so that issue gets addressed. Note: As mentioned S#3 (3. From tab A, switch to tab B, then switch to tab C.) It should be done after loading pages and by giving some time to load pages. Thanks. |
||
►
Sign in to add a comment |
||
Comment 1 by innatere...@gmail.com
, Aug 16 2017