-
-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
Pressing enter with blank link input crashes editor #8195
Comments
If you look at the background with the "Preview" button appearing, it seems to be creating a card the second time rather than a link. |
I had a blank markdown card underneath the paragraph, it seems to break in a way that the "preview" hover text becomes part of the main content |
The issue isn't that applying the link twice causes chaos, it's that the focus isn't applied to the link input box but the editor has lost the windows selection after the first time that it is toggled. Issues with the Range are by far the most common that we have with mobiledoc, I'm going to have to go through the mobiledoc code base at some stage and make sure that when editing operations happen it checks to make sure the range is valid, or at least catches these range errors properly. 😡 |
When the toolbar is toggled into link mode the link input field should always focus, however this only happens on the first time which leads to issues with mobiledoc having focus but not the range. This fix means that the toolbar always focuses. Closes: TryGhost/Ghost#8195
closes TryGhost/Ghost#8195 When the toolbar is toggled into link mode the link input field should always focus, however this only happens on the first time which leads to issues with mobiledoc having focus but not the range. This fix means that the toolbar always focuses.
Issue Summary
I made some text a link and then wanted to remove it, I assumed I could do this by repeating the process and entering blank text for the link but that crashed the editor.
Steps to Reproduce
(note that the popups are partially hidden due to the proximity to the browser window edge rather than the screencap cutoff)
Technical details:
The text was updated successfully, but these errors were encountered: