Last modified: 2013-08-30 05:43:49 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 T33347, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 31347 - Data lost when creating threads in separate browser tabs/windows
Data lost when creating threads in separate browser tabs/windows
Status: RESOLVED WORKSFORME
Product: MediaWiki extensions
Classification: Unclassified
LiquidThreads (Other open bugs)
unspecified
All All
: Normal major with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
http://translatewiki.net/w/i.php?titl...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-10-04 14:11 UTC by Purodha Blissenbach
Modified: 2013-08-30 05:43 UTC (History)
4 users (show)

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


Attachments

Description Purodha Blissenbach 2011-10-04 14:11:51 UTC
When several threads are creaded from parallel browser windows or threads, only the first one survives when saved, all other data is lost.

You may wish to follw the link "Start a new discussion" several times, opening the respective pages in new browser windows/tabs each time. While you can edit the new threads in prallel, you can save only one. Saving the threads begun in all other parallel tabs or windows yields nothing. They are not saved, and all typed data is lost. You can however, retrieve the data when your browsers "back" button supports restoring the pre-save state of input fields. Starting a new thread after the unsuccessul "save", and copying the data to it, does start another thread.

Put in other words, you can be creating only one thread at a time. Software seems to silently set a semaphore from "start new thread" to "save the thread from this window/tab" which inhibts starting another thread and invalidates all corresponding "save" operations of ones started in between.

I did not try with different browsers on the same client computer, and I did not try with different client computers but same user.
Comment 1 Nemo 2013-08-30 05:43:49 UTC
Works for me now, have you encountered this problem recently?

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


Navigation
Links