8
0
فهرست منبع

Docs: Reworded an inline comment to make it more clear.

Szymon Cofalik 6 سال پیش
والد
کامیت
f447d45099
1فایلهای تغییر یافته به همراه5 افزوده شده و 4 حذف شده
  1. 5 4
      packages/ckeditor5-engine/src/conversion/upcastdispatcher.js

+ 5 - 4
packages/ckeditor5-engine/src/conversion/upcastdispatcher.js

@@ -283,14 +283,15 @@ export default class UpcastDispatcher {
 		// Split element to allowed parent.
 		const splitResult = this.conversionApi.writer.split( modelCursor, allowedParent );
 
-		// Using the range returned by `model.Writer#split`, pair original elements with their split parts.
-		// The range returned from the writer spans "between" the split or precisely saying, from the end of the split element
-		// to the beginning of the other part of the split element:
+		// Using the range returned by `model.Writer#split`, we will pair original elements with their split parts.
+		//
+		// The range returned from the writer spans "over the split" or, precisely saying, from the end of the original (split) element
+		// to the beginning of the other (new) part of that element:
 		//
 		// <limit><a><b><c>X[]Y</c></b><a></limit> ->
 		// <limit><a><b><c>X[</c></b></a><a><b><c>]Y</c></b></a>
 		//
-		// After the split no meaningful content can be between the positions in `splitRange` - they have to be touching.
+		// After the split there cannot be any full node between the positions in `splitRange`. The positions are touching.
 		// Also, because of how splitting works, it is easy to notice, that "closing tags" are in the reverse order than "opening tags".
 		// Also, since we split all those elements, each of them has to have the other part.
 		//