Last modified: 2014-09-18 13:11:57 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 T26509, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 24509 - Editing too quickly causes EditWarning not to work
Editing too quickly causes EditWarning not to work
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
WikiEditor (Other open bugs)
unspecified
All All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-23 05:00 UTC by Liangent
Modified: 2014-09-18 13:11 UTC (History)
4 users (show)

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


Attachments

Description Liangent 2010-07-23 05:00:35 UTC
(Use a slow connection and / or computer, or open a very big page to test this) Open an edit page, and edit the content before the page is fully loaded. After the textbox is decorated by UsabilityInitiative, close the window. Though the content is changed, EditWarning does not warn me about this.
Comment 1 Bugmeister Bot 2011-08-19 19:12:53 UTC
Unassigning default assignments. http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/54734
Comment 2 Andre Klapper 2013-08-31 14:51:13 UTC
UsabilityInitiative not deployed anymore. Can this problem still be seen anywhere, or can this be closed as obsolete?
Comment 3 Andre Klapper 2014-07-18 12:29:06 UTC
Liangent: Can this problem still be seen anywhere, or can this be closed as obsolete?
Comment 4 Andre Klapper 2014-08-05 22:22:51 UTC
Liangent: Can this problem still be seen anywhere, or can this be closed as obsolete?
Comment 5 Liangent 2014-08-11 11:31:13 UTC
I'm unable to achieve "editing the content before the page is fully loaded" anymore probably thanks to ResourceLoader and the faster internet nowadays.

By checking code I can conclude that the issue still exists theoretically because it compares current text and origtext on window closing and origtext is fetched in document.ready, so an edit before document.ready pollutes it.

I'm putting this in lowest priority because people rarely see it while it's not a simple task to correctly fix it (maybe include a hash of original text on server side?).

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


Navigation
Links