[wp-trac] [WordPress Trac] #23295: Improved login expiration warning
WordPress Trac
noreply at wordpress.org
Thu Jul 11 20:02:19 UTC 2013
#23295: Improved login expiration warning
-------------------------------------------------+------------------
Reporter: mintindeed | Owner:
Type: task (blessed) | Status: new
Priority: normal | Milestone: 3.6
Component: Autosave | Version:
Severity: normal | Resolution:
Keywords: autosave-redo has-patch ui-feedback |
-------------------------------------------------+------------------
Comment (by wpdavis):
I agree that erring on the side of showing the modal is better. Anytime
there is a submit button, there is the potential to get kicked to the
login page and lose any edits you made, and that is _always_ frustrating.
The absolute worst case is that somebody will have to stop what they're
doing again and log back in. If I'd done that on the network page the
modal would have gone away and I could have accessed the code. I think
it's worth fixing in the few areas that there might be an action someone
would want to continue even after they've been logged out, but to be
honest, those are few and far between.
For that reason, I think a close box is a little extraneous — are there
any circumstances in which someone would _not_ want to log in to continue?
Would that person really not know how to delete the element out of the DOM
using dev tools?
Idea: What if we had the heartbeat on all form submits in the admin? Delay
the form submit until we're sure the person is logged in. If they're not,
show the modal and submit the form after a successful login (or prompt
them to resubmit).
--
Ticket URL: <http://core.trac.wordpress.org/ticket/23295#comment:75>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list