Bartosz Dziewoński 2d038af705 CommentController: Remove remains of client-side edit conflict handling ... In commit 8829a1a412 we kept this code when adding the reply API, but on second thought it doesn't actually make sense. The reply API should never fail with an edit conflict normally, since it makes the edit on the latest version of the page. If it does fail, I think it's better to just show the error message. Current behavior is to retry, and if that doesn't actually solve the problem, this ends up in an infinite loop. Bug: T252558 Change-Id: I5e0dcb2c42e5de4f18e99b8a761ca048a430b31e		2020-08-10 20:27:57 +02:00
..
dt-ve	Username suggestion header	2020-08-10 17:34:04 +00:00
lib
.eslintrc.json
CommentController.js	CommentController: Remove remains of client-side edit conflict handling	2020-08-10 20:27:57 +02:00
CommentItem.js
controller.js	Re-apply new reply API patches	2020-08-07 21:31:38 +02:00
dt.debug.js	Refactor CommentParser	2020-07-20 23:38:10 +01:00
dt.init.js	Refactor CommentParser	2020-07-20 23:38:10 +01:00
dt.init.less	Do not include .dt-init-replylink-buttons in printouts	2020-08-10 17:55:08 +02:00
dt.ui.ReplyWidget.js	Re-apply new reply API patches	2020-08-07 21:31:38 +02:00
dt.ui.ReplyWidget.less	Swap toolbar and mode switcher	2020-07-31 20:12:05 +00:00
dt.ui.ReplyWidgetPlain.js	Re-apply new reply API patches	2020-08-07 21:31:38 +02:00
dt.ui.ReplyWidgetVisual.js	Re-apply new reply API patches	2020-08-07 21:31:38 +02:00
HeadingItem.js
highlighter.css
highlighter.js	Make getNativeRange a method of ThreadItem	2020-07-22 21:56:48 +01:00
logger.js	VisualEditorFeatureUse: trackdebug logging consistent with EditAttemptStep	2020-07-20 17:26:53 -05:00
modifier.js	Re-apply new reply API patches	2020-08-07 21:31:38 +02:00
Parser.js	Refactor CommentParser	2020-07-20 23:38:10 +01:00
ThreadItem.js	Make getNativeRange a method of ThreadItem	2020-07-22 21:56:48 +01:00
utils.js	Make getNativeRange a method of ThreadItem	2020-07-22 21:56:48 +01:00