Page MenuHomePhabricator

Site JS editing experience when timeout happens mid-edit is poor
Open, HighPublicBUG REPORT

Description

Steps to replicate the issue (include links if applicable):

  • Start editing site JS
  • Wait long enough for your session to expire
  • Try to save

What happens?:

"You must log in again to verify that you are Pppery."

No way to do so other than opening the edit form again

What should have happened instead?:

Some way to verify your security status inline. Maybe a popup asking for a 2FA code ...

Software version (on Special:Version page; skip for WMF-hosted wikis like Wikipedia):

Other information (browser name/version, screenshots, etc.):

Event Timeline

Catrope triaged this task as High priority.Apr 13 2026, 9:19 PM
Catrope subscribed.

We will look into this as part of the work we're doing this quarter on improving the reauthentication system. We could mitigate this several different ways, for example:

  1. Show the same error as now, but also use JS to pop up a login form
  2. When the user hits the save button, stash the content they were trying to save, redirect to the login form for reauth, then redirect back to the edit form with the stashed content pre-populated

In the meantime, a workaround you can use when you see this error is:

  • resubmit the edit

But there are no .editOptions buttons at all when this happens?

  • resubmit the edit

But there are no .editOptions buttons at all when this happens?

You can use the refresh button in your browser, and confirm that you really want to resubmit the form when it displays a prompt. (I tested this on Firefox and Chromium.)

Close this tab, go back to the tab with your edit session, and resubmit the edit

Note: in many browsers simply press F5 on "You must log in again to verify that you are XXX" error screen will try to resubmit the edit.