Visibility API mis-firing on profile change from chrome Icon
Reported by
steven.f...@nielsen.com,
Sep 10
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36 Steps to reproduce the problem: 1. With chrome open, hover over chrome icon in bottom tray and right click 2. Select a different person than the current user under "people" 3. A new window will open for the new user, the visibility api will fire twice. One for hidden, and then another for in focus even though you are now on the other tab 4. The original tab never fires another "hidden" from the visibility API call even if you move screens from here altogether. What is the expected behavior? On step 3, the chrome browser should only fire one "hidden" fire from the view-ability API on a new profile selected, and only fire the in focus fire when the suer clicks back into focus. What went wrong? On step 3, the browser is firing both a hidden view-ability call and an in focus call. Did this work before? No Does this work in other browsers? Yes Chrome version: 68.0.3440.106 Channel: n/a OS Version: OS X 10.13.6 Flash Version:
,
Sep 10
Blink>JavaScript>API is the wrong component for this (it's for V8's C++ API). I don't know what the right component is, but it's something else under Blink.
,
Sep 11
,
Sep 12
|
||||
►
Sign in to add a comment |
||||
Comment 1 by lgrey@chromium.org
, Sep 10