page visibility api vs pause/resume

[Brian LeRoux <b...@brian.io>]

Our impl of pause/resume events predate the spec of the page visibility
api. I feel we should deprecate for the web thing.

Discuss!

Re: page visibility api vs pause/resume

[Brian LeRoux <b...@brian.io>]

Its true the behavior is different tho I *think* usage is the same.


On Tue, Dec 10, 2013 at 10:16 AM, Ian Clelland <ic...@chromium.org>wrote:

> +0 -- I'm generally in favour, and it looks like we could provide a pretty
> simple shim if people still wanted onpause/onresume events.
>
> The concepts aren't entirely synonyms, though, are they? -- the W3C rec is
> concerned with "is the app actually visible on the screen right now";
> pause/resume are more about "am I being suspended/pushed to the background"
>
> (Not certain how many platforms would allow another app to be shown
> on-screen *without* immediately suspending the previous foreground app, but
> it's a possibility)
>
>
>
> On Mon, Dec 9, 2013 at 6:42 PM, Brian LeRoux <b...@brian.io> wrote:
>
> > Our impl of pause/resume events predate the spec of the page visibility
> > api. I feel we should deprecate for the web thing.
> >
> > Discuss!
> >
>

Re: page visibility api vs pause/resume

[Ian Clelland <ic...@chromium.org>]

+0 -- I'm generally in favour, and it looks like we could provide a pretty
simple shim if people still wanted onpause/onresume events.

The concepts aren't entirely synonyms, though, are they? -- the W3C rec is
concerned with "is the app actually visible on the screen right now";
pause/resume are more about "am I being suspended/pushed to the background"

(Not certain how many platforms would allow another app to be shown
on-screen *without* immediately suspending the previous foreground app, but
it's a possibility)



On Mon, Dec 9, 2013 at 6:42 PM, Brian LeRoux <b...@brian.io> wrote:

> Our impl of pause/resume events predate the spec of the page visibility
> api. I feel we should deprecate for the web thing.
>
> Discuss!
>