Last modified: 2013-10-09 21:36:37 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 T31917, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 29917 - LiquidThreads should obey Vector's "useeditwarning" user preference
LiquidThreads should obey Vector's "useeditwarning" user preference
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
LiquidThreads (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on: 46514
Blocks:
  Show dependency treegraph
 
Reported: 2011-07-15 22:46 UTC by Emufarmers
Modified: 2013-10-09 21:36 UTC (History)
4 users (show)

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


Attachments

Description Emufarmers 2011-07-15 22:46:28 UTC
By default, users are warned if they try to leave a page while they're editing it.  This doesn't appear to apply if you're replying to a LiquidThreads post.  This seems like inconsistent interface behavior.

Based on a report at http://www.mediawiki.org/wiki/Thread:Project:Support_desk/Suggestion_to_warn_user_when_leaving_page
Comment 1 Erwin Dokter 2011-07-15 22:57:20 UTC
That message is provided by the Vector extension on standard edit pages. When you reply on a LiquidThreads-enabled talk page, you are not on an edit page, and the message does not appear.
Comment 2 Emufarmers 2011-07-16 00:06:02 UTC
Yes, I see the technical reason for this behavior: I just think it should be changed. :)
Comment 3 Alex Monk 2013-02-19 02:42:11 UTC
+ Depends on bug 45051 - I don't think this should be done until the feature is in core.
Comment 4 Bartosz Dziewoński 2013-10-09 21:36:37 UTC
The edit warning feature (and preference) is in core for quite some time now.

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


Navigation
Links