Last modified: 2014-09-12 23:23:55 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 T69491, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 67491 - Error handling for not writing anything in the Close / Reopen field
Error handling for not writing anything in the Close / Reopen field
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
Flow (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-07-03 20:33 UTC by Danny Horn
Modified: 2014-09-12 23:23 UTC (History)
5 users (show)

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


Attachments
Closing failz screenshot (181.12 KB, image/png)
2014-07-03 20:33 UTC, Danny Horn
Details

Description Danny Horn 2014-07-03 20:33:54 UTC
Created attachment 15835 [details]
Closing failz screenshot

On Mediawiki.org -- 

When you close or reopen a topic and you don't write anything in the field, you get a pop-up modal that says failz

This is amusing but probably not great error handling. :) 


To reproduce:

- Select Close topic
- Type "closing test" in the field, click Close topic
- Select Reopen topic
- Remove all the text from the field, click Reopen topic

It's the same error whether you're doing opening or closing.
Comment 1 Danny Horn 2014-07-03 20:34:46 UTC
On Trello: https://trello.com/c/VDqYLQ40
Comment 2 Erik Bernhardson 2014-09-12 23:23:55 UTC
This field is now handled by the standard "gray out" behavior.  The textarea is marked as "required" via HTML5 and the javascript doesn't allow you to clikc "Reopen" unless there is content.  There is no more "failz" dialog.

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


Navigation
Links