-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
[Bug]: InputRules seem not to fire in 2.5.5 #5384
Comments
@Nantris I don't see anything that would be different here for input rules between these versions: @tiptap/vue-3@2.5.4...v2.5.5 2.5.5 was mostly around vue 3 performance updates, are you using vue-3? The only other code change could have been: #5321 I would need more information to help you out here |
Is it just the one input rule that is not applying? Could your parseHTML not be applying? Maybe you have the task list extension installed twice? I don't know what could be breaking you here |
Any update on this @Nantris? I've also addressed a couple more bugs since so may be worth upgrading |
@nperez0111 thanks for the ping on this. I tried I was able to identify the problem commit: 4cca3826950176b6d9981cdc6e1e9b654f696319 but heck if I know why. None of the affected rules seem to have anything to do with Via manually editing the file in
In both cases the caret was in the position immediately after the Thanks again for the great work you're doing @nperez0111! |
Should be resolved already with v2.5.9 |
Confirmed resolved; forgot to close. Thanks for your great work @nperez0111! |
Affected Packages
core
Version(s)
2.5.5
Bug Description
After upgrading from
2.5.4
to2.5.5
several tests broke here. I took a look and it seems breakpoints inside of input rules are no longer being hit. Presumably it's not all input rules since only a few tests broke. Most of the broken tests seem to relate to lists.Example input rule which no longer applies:
Browser Used
Chrome
Code Example URL
No response
Expected Behavior
InputRule behavior is unchanged from
2.5.4
Additional Context (Optional)
We have a custom
parseHTML
so it seems unlikely to me that this PR broke it: b47df57At the same time, none of the others jump out to me as obvious causes either.
Dependency Updates
The text was updated successfully, but these errors were encountered: