Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

merge from upstream #4

Open
wants to merge 113 commits into
base: pr
Choose a base branch
from
Open

Conversation

shlroland
Copy link
Member

No description provided.

lastnigtic and others added 30 commits September 10, 2020 23:48
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
marijnh and others added 28 commits April 8, 2024 08:37
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 ProseMirror#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.
@shlroland shlroland changed the title Update Version Update version Aug 13, 2024
@shlroland shlroland changed the title Update version merge from upstream Aug 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.