Because that I know of there is no current way to determine if an edit conflict is in different sections, and can be auto-merged. I would like to see an automerge feature sometime in the future, where a proposed merge is displayed. It would solve a lot of problems, even for a very conservative algorithm that only suggests a merge when the edits are done to different sections. It still would only have to load the specific section again to make the changes. I don't know how hard this would be though, but it doesn't sound too hard to me.
On Mon, Mar 17, 2008 at 6:00 PM, Nathan nawrich@gmail.com wrote:
Couple stupid questions: When you get an edit conflict, why does the entire page load instead of the relevant section? Also, do .js scripts effect the speed of an edit conflict load?
Nathan
On 2/25/08, Thomas Dalton thomas.dalton@gmail.com wrote:
On 25/02/2008, Nathan nawrich@gmail.com wrote:
Why is the edit conflict process so painful? When I get EC'd, it usually takes 20-30 seconds to work itself out and I typically get a JavaScript error to boot. Isn't there an easier way of handling edit conflicts
that
doesn't shut down a browser for up to 30 seconds on a brand new
machine?
What's it doing for this 20-30 seconds, and what's the error? I've never had any problems like that with edit conflicts (they're very annoying and it's takes me a while to resolve them, but my browser copes fine).
WikiEN-l mailing list WikiEN-l@lists.wikimedia.org To unsubscribe from this mailing list, visit: https://lists.wikimedia.org/mailman/listinfo/wikien-l
WikiEN-l mailing list WikiEN-l@lists.wikimedia.org To unsubscribe from this mailing list, visit: https://lists.wikimedia.org/mailman/listinfo/wikien-l