Last modified: 2012-03-07 03:29:09 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T36964, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 34964 - ApiSandbox partially remembers input values when navigating to another page and then going back
ApiSandbox partially remembers input values when navigating to another page a...
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
ApiSandbox (Other open bugs)
unspecified
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-03-04 18:48 UTC by MZMcBride
Modified: 2012-03-07 03:29 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments
Screenshot of ApiSandbox UI after navigating away and then hitting back button in browser (76.41 KB, image/png)
2012-03-04 18:48 UTC, MZMcBride
Details

Description MZMcBride 2012-03-04 18:48:33 UTC
Created attachment 10173 [details]
Screenshot of ApiSandbox UI after navigating away and then hitting back button in browser

When using ApiSandbox, if you set some of your parameters such as json/edit and then you happen to click the "the API documentation" link in your browser and then click back to the ApiSandbox page, the behavior is a little odd.

ApiSandbox remembers which options you selected for Format and Action, but it requires toggling the Action parameter to re-view the form. This behavior exists on both Chrome/Mac and Safari/Mac. I'll try to attach a screenshot of the behavior as well.

Ideally, ApiSandbox would remember all of your parameters and show what you had before navigating away. If that isn't possible, it would at least re-initialize the form properly rather than requiring people to fiddle with the drop-down menus to view the form again.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links