Make the entire Remember Me settings entry active, and have it trigger a
click on the checkbox, to have the existing change handling code do its
job.

I have a question regarding this change.

I'm adding an event.preventDefault() to both the new
rememberMeSetting_tapHandler() and the already existing
rememberMe_changeHandler().  I believe, however, that the latter will never
be necessary, because the active encompassing anchor, together with the
.preventDefault() in the .rememberMeSetting_tapHandler(), will only get the
click via the .trigger('click') from the method associated with the anchor,
never directly from the UI.  Should I leave out the second
.preventDefault()?
To give a sense of the problem, this elaborate interlock works *sometimes*.
This leads me to believe that implementation of the switch, itself, is
getting in the way.  There may be an easy way to work around it, but that
probably requires factoring in the switch operation, and maybe changing it.
Merge branch 'master' into issue-229-active-settings-toggle-body
Remove the interlock stuff - much too cumbersome, and not a good approach.

Try setting z-index.  Not currently sufficent, and we will probably be
switching to a different switch mechanism anyway, but worth recording.
Provide a wrapper DialogView.showNotifyErrorResponse() for .showNotify()
which takes an XHR response object and incorporates the error status text
and status code in the error notice.
Provide missing parameters on PublicShareRoomsCollection.addHandler(), so
that salient info is not lost when calling the surrounding success and
error handlers.
Include the status code in the "temporary server failure" catchall error
notice, in case it might sometimes be useful.  (It occurs to me that
"temporary" may purely be for dubious "spin", rather than useful info.
But, hey.)
Deploy the new DialogView.showNotifyErrorResponse() everywhere we can.

Now, hopefully, we'll have more chance of getting salient info about what
went wrong when users encounter errors.
Slightly better offline error message...
Merge pull request #273 from SpiderOak/issue-272-better-connection-error-messages

Issue 272 better connection error messages