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
dart2js document.hidden returns null in firefox #13411
Comments
Added html-api label. |
This comment was originally written by everton.mar...@gmail.com This issue affects the Page Visibility API for Dart: |
Removed Area-HTML label. |
Removed this from the Later milestone. |
Removed Oldschool-Milestone-Later label. |
This comment was originally written by matthew1...@gmail.com The issue also impacts Safari. I am, however, able to check document.visibilityState and receive either: 'visible' or 'hidden' The Page Visibility API, in the current spec as of this writing (http://www.w3.org/TR/page-visibility/), also specifies the vendor optional: 'prerender' and 'unload' 'prerender' and 'unload' is implied to be correspond to hidden == true. As such I can work around this by wrapping the document.visibilityState for now. |
Still true in 1.8 with Safari and Firefox. Removed Priority-Unassigned label. |
This issue was originally filed by everton.marqu...@gmail.com
What steps will reproduce the problem?
What is the expected output?
document.hidden : true OR false (non-null)
What do you see instead?
document.hidden : null
What version of the product are you using?
Dart Editor version 0.7.3_r27487
Dart SDK version 0.7.3.1_r27487
Firefox 24
On what operating system?
64-bit Windows 7
Please provide any additional information below.
I see the following output from hidden.dart:
Dartium:
document.hidden : false
hidden : false
hidden == null : false
hidden is bool : true
dart2js + Chrome:
document.hidden : false
hidden : false
hidden == null : false
hidden is bool : true
dart2js + Firefox:
document.hidden : null
hidden : null
hidden == null : true
hidden is bool : false
Attachment:
hidden.dart (488 Bytes)
The text was updated successfully, but these errors were encountered: