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
I don't know what changed, but inline code marks were working before, and now they aren't:
Carnac_RJzpLl35iM.mp4
EDIT: Just noticed that this problem is not exclusive to inline code marks, but all other input rules as well. For instance, open the default editor, and try to type ** before a word, you'll quickly realize there's an issue (and you won't be able to type ** after the word, to turn the word bold).
Which browser was this experienced in? Are any special extensions installed?
All of them. No special extensions.
How can we reproduce the bug on our side?
Use the default text editor, and try to use backticks to applied inline code marks.
What did you expect to happen?
Inline code marks with backticks should work without issues, as they did in the past.
Did you update your dependencies?
Yes, I’ve updated my dependencies to use the latest version of all packages.
Are you sponsoring us?
Yes, I’m a sponsor. 💖 (on behalf of Doist)
The text was updated successfully, but these errors were encountered:
What’s the bug you are facing?
I don't know what changed, but inline code marks were working before, and now they aren't:
Carnac_RJzpLl35iM.mp4
EDIT: Just noticed that this problem is not exclusive to inline code marks, but all other input rules as well. For instance, open the default editor, and try to type
**
before a word, you'll quickly realize there's an issue (and you won't be able to type**
after the word, to turn the word bold).Which browser was this experienced in? Are any special extensions installed?
All of them. No special extensions.
How can we reproduce the bug on our side?
Use the default text editor, and try to use backticks to applied inline code marks.
What did you expect to happen?
Inline code marks with backticks should work without issues, as they did in the past.
Did you update your dependencies?
Are you sponsoring us?
The text was updated successfully, but these errors were encountered: