-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Focus detection not fully functional #29
Comments
As far as I remember the focus never worked when place another window (like On Tue, Jul 8, 2014 at 6:45 PM, dbb613 [email protected] wrote:
|
I am quite certain that focus detection used to work more completely -- specifically when another window overlaps the browser window. I can send you a demo link, but in short, the focus detection code was: |
Is there a reason why this logic was removed? It seems essential to proper detection of focus. |
The old focus detection didn't detect correctly on FF and IE browsers. I'll On Wed, Jul 9, 2014 at 10:16 AM, dbb613 [email protected] wrote:
|
From my tests, it looks like the old focus detect does work in recent FireFox (v 30 works). I think using hasFocus is tricky because it doesn't work as expected when inside an IFRAME, but in all other cases, we should be using that to take into account a broader range of "out of focus" situations not covered by using the various hidden properties or visibilityState properties. |
Can you share the test page? On Wed, Jul 9, 2014 at 12:52 PM, dbb613 [email protected] wrote:
|
Hey guys, I just added a test page/harness into the test_page branch that may be of help here. |
The summary of the expected behavior is here:https://docs.google.com/spreadsheets/d/1SriqfUS17Riij6C8xsb71pxNlD8L1wGXIUhoICSQ1Vc/edit#gid=1680772678 |
The OpenVV focus detection seems to be only partially functional. It properly detects when you have switched to a different tab or have minified the browser, but does not properly detect when you place another window such that it overlaps the browser window containing the asset.
This used to work properly in an older version of OpenVV, so I'd consider it a regression bug.
This behavior can be observed with both IFRAMEd and non-IFRAMEd cases. See these example links:
Note that these are both based off of my fork which has the latest code as of commit id 812622c.
My code is here for reference: https://github.com/dbb613/openvv/tree/test-pages_and_build-improvement
Configurations Tested:
The text was updated successfully, but these errors were encountered: