Last modified: 2013-12-15 01:55:50 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 T18306, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 16306 - Allow user to specify block settings from CU form
Allow user to specify block settings from CU form
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
CheckUser (Other open bugs)
unspecified
All All
: Normal enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: SWMT
  Show dependency treegraph
 
Reported: 2008-11-11 04:29 UTC by Mike.lifeguard
Modified: 2013-12-15 01:55 UTC (History)
7 users (show)

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


Attachments
Crappy mockup (106.63 KB, image/png)
2008-11-24 03:16 UTC, Mike.lifeguard
Details

Description Mike.lifeguard 2008-11-11 04:29:27 UTC
Currently the settings are hardcoded - please add a block form to set this manually (one for users and one for IPs). Probably the current settings should be defaults such that if one is happy with those settings, a click on the button is all that's required.
Comment 1 Mike.lifeguard 2008-11-24 03:16:33 UTC
Created attachment 5538 [details]
Crappy mockup

I was concerned this would waste lots of screen real estate, but after doing this mockup, I think it can work.

The block form is smaller in this case, since you don't need the fields for:
*username (that input comes from the checkboxes)
*block reason dropdown or text field (one common field provided at the bottom)
*nuke the expiry dropdown too (text box is enough)
*the block buttons (replaced by the one at the botton)

I just crossed out those inputs for illustration.

So out of 22 lines of inputs for 2 block forms, only 11 are kept.

You can also save some space by putting the user & user talk replacement fields on one line.
Comment 2 Mike.lifeguard 2008-11-24 05:59:50 UTC
(In reply to comment #1)
> Created an attachment (id=5538) [details]
> Crappy mockup
> 
> I was concerned this would waste lots of screen real estate, but after doing
> this mockup, I think it can work.
> 
> The block form is smaller in this case, since you don't need the fields for:
> *username (that input comes from the checkboxes)
> *block reason dropdown or text field (one common field provided at the bottom)
> *nuke the expiry dropdown too (text box is enough)
> *the block buttons (replaced by the one at the botton)
> 
> I just crossed out those inputs for illustration.
> 
> So out of 22 lines of inputs for 2 block forms, only 11 are kept.
> 
> You can also save some space by putting the user & user talk replacement fields
> on one line.
> 

Additionally, you can hide the block forms until a user or IP is checked off. So, nothing shows unless you start ticking off boxes.
Comment 3 Bugmeister Bot 2011-08-19 19:12:18 UTC
Unassigning default assignments. http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/54734
Comment 4 MA 2012-08-10 10:05:33 UTC
Related: bug 39213

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


Navigation
Links