merge from upstream #3
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
FIX: Fix an issue where an inner node's mark information could reset the same mark provided by an outer node in the DOM parser.
Co-authored-by: lastnigtic <[email protected]> FIX: Fix issue where 1.11.1 uses an array method not available on Internet Explorer.
FEATURE: The output of `toDOM` functions can now be a `{dom, contentDOM}`
object specifying the precise parent and content DOM elements.
See https://discuss.prosemirror.net/t/contentdom-when-returning-a-dom-node-from-todom/3209
See https://discuss.prosemirror.net/t/underline-parserule-that-excludes-links/3302/9 See https://github.com/ProseMirror/rfcs/blob/master/text/0011-nonconsuming-parse-rules.md FEATURE: Parse rules can now have a `consuming: false` property which allows other rules to match their tag or style even when they apply.
FIX: Fix a bug where nested marks of the same type would be applied to the wrong node when parsing from DOM.
FIX: `MarkType.removeFromSet` now removes all instances of the mark, not just the first one. Issue ProseMirror/prosemirror-transform#17
FIX: Fix an issue where nested tags that match mark parser rules could cause the parser to apply marks in invalid places. Closes ProseMirror/prosemirror#1130
FEATURE: `Fragment.textBetween` is now public.
FIX: `Node.check` will now error if a node has an invalid combination of marks. Closes ProseMirror/prosemirror#1116
Even when preserveWhitespace is "full". FIX: Don't leave carriage return characters in parsed DOM content, since they confuse Chrome's cursor motion. Issue ProseMirror/prosemirror#1138
…pace is full FIX: DOM parsing with `preserveWhitespace: "full"` will no longer ignore whitespace-only nodes. Issue ProseMirror/prosemirror#1159
FEATURE: The `ParseRule` type is now a union of `TagParseRule` and `StyleParseRule`, with more specific types being used when appropriate.
FEATURE: The new `linebreakReplacement` property on node specs makes it possible to configure a node type that `setBlockType` will convert to and from line breaks when appropriate. Issue ProseMirror/prosemirror#1460
FIX: Improve performance and accuracy of `DOMParser` style matching by using the DOM's own `style` object. Issue ProseMirror/prosemirror#1470
FIX: Make sure resolved positions (and thus the document and schema hanging off them) don't get kept in the cache when their document can be garbage-collected. Closes #81
... rather than iterating style items, which may show only normalized versions of the properties. FIX: Fix an issue where parse rules for CSS properties that were shorthands for a number of more detailed properties weren't matching properly. Closes ProseMirror/prosemirror#1473
FEATURE: Attribute specs now support a `validate` property that can be used to provide a validation function for the attribute, to guard against corrupt JSON input.
FIX: Add code to `DOMSerializer` that rejects DOM output specs when they originate from attribute values, to protect against XSS attacks that use corrupt attribute input.
FIX: Make attribute validation messages more informative.
FIX: Fix some corner cases in the way the DOM parser tracks active marks. See https://discuss.prosemirror.net/t/how-to-parse-nested-mark-attributes/6596
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.