-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: ueberdosis/tiptap
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: @tiptap/extension-bullet-list@2.6.3
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: ueberdosis/tiptap
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: @tiptap/extension-bullet-list@2.6.4
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 3 commits
- 112 files changed
- 2 contributors
Commits on Aug 15, 2024
-
fix(react): attempt to cleanup editor instances, on creation #5492 (#…
…5496) The core of the change ended up being quite simple, because we can create the editor within the first render, we need to already schedule it's destruction. Scheduling a destruction, ensures that an instance that was created in that first render pass can be cleaned up. Waiting one more tick than before ensures that we don't accidentally destroy an editor instance that could actually be valid in the next render pass. In StrictMode, there will be two editor instances created, the first will be created & quickly destroyed in 2 ticks. In Normal React, there will only ever be 1 instance created and destroyed only on unmount.
Configuration menu - View commit details
-
Copy full SHA for 6a0f4f3 - Browse repository at this point
Copy the full SHA 6a0f4f3View commit details -
fix(link): respect custom protocols #5468 (#5470)
When [we fixed a XSS vuln](#5160), we inadvertently broke the ability to use custom protocols, this resolves that by allowing additional custom protocols to be considered valid and not stripped out
Configuration menu - View commit details
-
Copy full SHA for 593f107 - Browse repository at this point
Copy the full SHA 593f107View commit details -
Configuration menu - View commit details
-
Copy full SHA for ae6cb9d - Browse repository at this point
Copy the full SHA ae6cb9dView commit details
There are no files selected for viewing