require manual unpause when app is refocused

[hunter-pbs]

Instead of toggling pause state on application focus, just set pause to true when focus is lost, requiring a manual unpause via pause buttons.

[fuentism]

@hunter-pbs this behavior makes sense to me, but I didn't see this functionality listed on that ticket - is this something that Kelly is aware of, that we're changing what happens when you re-focus the play page?

[hunter-pbs]

@hunter-pbs this behavior makes sense to me, but I didn't see this functionality listed on that ticket - is this something that Kelly is aware of, that we're changing what happens when you re-focus the play page?

Sorry, I referenced the wrong Pause ticket in the changelog. Has been updated. This behavior is detailed here:
https://www.pivotaltracker.com/story/show/188461849

[fuentism]

Looks good to me, but let's let @renzoolguin weigh in on this one too since this will be our first commit to the container code. Woo!

[renzoolguin]

This looks good. I was a little confused at first because it looked we were PR'ing into the original repo and not the fork due to the similar repo names. Maybe we could at least update the README to reflect that this is for the redesign site?

[hunter-pbs]

This looks good. I was a little confused at first because it looked we were PR'ing into the original repo and not the fork due to the similar repo names. Maybe we could at least update the README to reflect that this is for the redesign site?

@renzoolguin @fuentism
I added a Redesign tag to that Changelog entry. Is that sufficient? Should we add a line noting when we forked and took over? Should our version numbers more clearly represent our fork? Like, is this Website Redesign Springroll Container v1.0.0? I can imagine conflicting version numbers getting confusing down the road.

[renzoolguin]

This looks good. I was a little confused at first because it looked we were PR'ing into the original repo and not the fork due to the similar repo names. Maybe we could at least update the README to reflect that this is for the redesign site?

@renzoolguin @fuentism I added a Redesign tag to that Changelog entry. Is that sufficient? Should we add a line noting when we forked and took over? Should our version numbers more clearly represent our fork? Like, is this Website Redesign Springroll Container v1.0.0? I can imagine conflicting version numbers getting confusing down the road.

Let's start tracking the Redesign work as 3.0.0+ Note in that version that is the start of redesign work. That way any updates in 2.x.y can be merged in if any changes in the original repo need to be pulled in.