Last modified: 2014-02-19 22:30:56 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 T42692, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 40692 - New edit warning above the editing window should be dismissible
New edit warning above the editing window should be dismissible
Status: NEW
Product: MediaWiki
Classification: Unclassified
Interface (Other open bugs)
1.21.x
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-02 01:57 UTC by Erik Moeller
Modified: 2014-02-19 22:30 UTC (History)
3 users (show)

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


Attachments

Description Erik Moeller 2012-10-02 01:57:02 UTC
MediaWiki:Editpage-head-copy-warn was created to allow moving the warning that was previously shown below the edit window above it, per https://www.mediawiki.org/wiki/Micro_Design_Improvements

This actually makes the warning significantly more prominent than before, which is a good thing in that it'll actually be noticed, but it's pretty in-your-face for something that every Wikimedian understands after a while.

As a further iterative improvement, I would suggest making the warning dismissible (perhaps with a link with a friendly label like "Thanks, got it"). Ideally this should be persistent via the preferences API so it doesn't keep coming back if a cookie expires.

This change requires legal sign-off.
Comment 1 MZMcBride 2012-10-02 02:11:57 UTC
I agree that it'd be nice to be able to dismiss this warning. I'm not sure why the dismissibility has to be conditional on the use of JavaScript, though.
Comment 2 Erik Moeller 2012-10-02 03:55:38 UTC
You're right, this was more intended in the "at a minimum" sense - but if we use a persistent pref rather than Yet Another Cookie, we get non-JS dismissibility for free, at the cost of some additional pref clutter. Amending summary.
Comment 3 Oliver Keyes 2012-10-06 13:42:54 UTC
Yeah, the additional pref clutter is what I'm worried about; we're expected to dramatically slim down the prefs section for Echo. Perhaps we could just tie it to some sort of user status? Like, if we're talking "after a while, they know how to do it" - when an account has made N edits, or gets any userright other than autoconfirmed (or gets autoconfirmed itself) we assume they're far enough down the rabbit-hole to know that {{cn}} should be avoided. This is just me spitballing, note.

I don't think legal actually needs to sign off: this isn't their text (they own the "You agree..." section). The only bit that has legal implications is "please don't violate teh copyrights" and that's duplicated, for all intents and purposes, in the TOS, which says (Section 4) "Certain activities, whether legal or illegal, may be harmful to other users and violate our rules, and some activities may also subject you to liability. Therefore, for your own protection and for that of other users, you may not engage in such activities on our sites. These activities include...Infringing copyrights, trademarks, patents, or other proprietary rights under applicable law."

Users are, of course, required to accept this before hitting "save" (and hitting save is taken to be an acceptance of it).
Comment 4 Erik Moeller 2012-11-11 17:38:27 UTC
The perfect is the enemy of the good. Let's make it dismissible with pref for now.

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


Navigation
Links