Visibility API #87

Open
justmarkup opened this Issue Jan 24, 2012 · 14 comments

Comments

Projects
None yet
7 participants

I think the Visibility API is worth a mention.

Currently there is native support for Chrome > 13, IE 10 and Firefox 10 although only with prefixes.

Pollyfills:

In my opinion the status should be "Use with pollyfills" .

What do you think?

Contributor

addyosmani commented Jan 24, 2012

I've used both of the above polyfills/shims in production. I think mine and evilmartians both need more/tests, but they do the trick. I would say 'use with polyfills'.

Member

Raynos commented Jan 24, 2012

Defiantly worth mentioning. Neiter appear to be polyfills they are just feature equivelant emulation using propietory APIs.

Writing a real polyfill shouldn't be too difficult though.

Member

nimbupani commented Jan 24, 2012

If this is proprietary API I think we should mention with 'avoid'. We shouldnt have to face the trauma of flexbox again.

Member

Raynos commented Jan 24, 2012

That's not what I meant. I meant the polyfills don't use the native API. (the polyfills use their own propietory API, except the term "propietory API" is poorly used to describe that).

Page Visibility is a proper w3c specification.

Member

nimbupani commented Jan 24, 2012

ohh i see. perhaps then we need a good polyfill that DOES use the native API?

Contributor

addyosmani commented Jan 24, 2012

So, to add some further clarity to the comment from @Raynos, both solutions do use the Page Visibility API in it's native form if it's present, but do so and provide fallbacks through an abstraction layer. This was necessary as we were experiencing (IE) issues related to just firing off simulated 'visibilityChanged' events that prevented us from just doing a 100% polyfill. If anyone feels they can improve on that, by all means please do :)

Member

Raynos commented Jan 24, 2012

Would firing visibilityChanged events through an emulated DOM2 events (addEventListener) API in oldIE count as a 100% polyfill? That should be possible. Also DOM 0 event listeners like document.onvisibilitychange should also be possible.

I'll add writing a page visibility polyfill to the list.

Contributor

addyosmani commented Jan 24, 2012

It would cover the most important part of the spec, but if you're going for completeness there's a little more to it such as exposing the actual state and not just that it's changed :)

On 24 Jan 2012, at 18:54, Raynosreply@reply.github.com wrote:

Would firing visibilityChanged events through an emulated DOM2 events (addEventListener) API in oldIE count as a 100% polyfill? That should be possible. Also DOM 0 event listeners like document.onvisibilitychange should also be possible.

I'll add writing a page visibility polyfill to the list.


Reply to this email directly or view it on GitHub:
#87 (comment)

Member

Raynos commented Jan 25, 2012

The following polyfill : https://gist.github.com/1677020 given some polish and testing should work correctly.

Note that legacy browser support in this case requires polyfilling addEventListener, [].forEach and Object.defineProperty which should all be shimmable back to oldIE.

Member

jonathantneal commented Jan 29, 2012

If it helps make things feel more native in old ie, you could use a combination onpropertychange and toString = function() to make your polyfill act and feel more native (i use it as a poor man's object.watch)

reconbot commented Feb 1, 2012

@Raynos that works for me, thank you thank you!

Member

nimbupani commented Feb 19, 2013

@Raynos what is your view on this? Would you be up to making a new post on Visibility API?

Member

Raynos commented Feb 19, 2013

Its worth mentioning yes, not sure what I would write about it, may get around to it.

Member

arthurvr commented Nov 12, 2014

Do you guys think there's still a need for 'use with polyfill'? Take a look at the caniuse page, but looks like it's overall quite green.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment