You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I have defined a custom link inline spec with a defined input rule, and create editor schema without defaultInlineContentSpecs. But when I type a http link content, such as https://www.bing.com, then type a whitespace or enter, it insert default link inline content.
Describe the solution you'd like
Before I type in whitespace or enter, the input rule of my custom link inline content is triggered, but once whitespace or enter type in, the default link triggered and my custom link is invalid. It is bad, in this scene, my custom link should always be triggered.
Describe alternatives you've considered
Provide a configuration to remove or disabled default link spec, include input rules.
Additional context
Bonus
[ ] I'm a sponsor and would appreciate if you could look into this sooner than later 💖
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I have defined a custom link inline spec with a defined input rule, and create editor schema without defaultInlineContentSpecs. But when I type a http link content, such as
https://www.bing.com
, then type a whitespace or enter, it insert default link inline content.Describe the solution you'd like
Before I type in whitespace or enter, the input rule of my custom link inline content is triggered, but once whitespace or enter type in, the default link triggered and my custom link is invalid. It is bad, in this scene, my custom link should always be triggered.
Describe alternatives you've considered
Provide a configuration to remove or disabled default link spec, include input rules.
Additional context
Bonus
[ ] I'm a sponsor and would appreciate if you could look into this sooner than later 💖
The text was updated successfully, but these errors were encountered: