Last modified: 2012-12-31 14:00: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 T45537, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 43537 - Review missingcommenttext and editingcomment messages
Review missingcommenttext and editingcomment messages
Status: NEW
Product: MediaWiki
Classification: Unclassified
Page editing (Other open bugs)
1.21.x
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
: i18n
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-12-31 13:51 UTC by Dereckson
Modified: 2012-12-31 14:00 UTC (History)
5 users (show)

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


Attachments

Description Dereckson 2012-12-31 13:51:29 UTC
[ Steps to reproduce ]

- Edit a page
- Add &section=new in the URL
- Don't add any body message
- Submit

You'll get a message (missingcommenttext) "Please enter a comment below.".

[ Issue ]

This doesn't seem really pertinent, as section=new is used for a wider spectrum than to comment something.

It's for example used to add a request on a requests page, to add a message on talk page, etc.

[ Solution offered ]

For missingcommenttext: "Please enter the text to add to the page below.".

For editingcomment: the new section wording is fine, maybe the message title is clumsy.
Comment 1 Nemo 2012-12-31 14:00:55 UTC
Message keys are not changed.

I'm not sure it makes sense not to consider that "Add a topic" (this the current name) to a discussion is the main use of section=new, and the only one offered by default by the UI. Maybe we could avoid the problem altogether (and get rid of the confusing "below") by just saying "Please enter a text for your contribution" or something like that.

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


Navigation
Links