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
This issue can be appended to include various bugs that are found in the new editor. When fast fixes are complete, any remaining issues here can be converted to standalone issues.
Inline node processing issues
Inline nodes need to be processed alongside surrounding text, and be subject to surrounding marks, while still having their children processed as required.
inline images become text in the visual editor
markdown images within links used to display as images, now they display as text
marks around links cause the links to become text in the visual editor
marks applied to inline code, e.g. **`test`**, break in the visual editor
Escaping issues
when converting markdown to Remark, don't parse markdown entities within raw html
when converting Slate to Remark, escape all markdown entities except those in raw html
markdown images broken by unintelligent escaping because ![ becomes !\[
visual editor doesn't distinguish between newline sequence (literal \n) and line break
html entities are decoded by the visual editor (not just visually, but in the source)
line break entities (trailing backslash) are visible in visual editor
markdown entities within code blocks should not be escaped
markdown entities within raw html should not be escaped
(trailing double space or backslash)
inactive markdown entities (like a literal asterisk or backslash) are unnecessarily escaped
UX issues
clicking below a trailing shortcode block in the visual editor should set focus in a paragraph
trim trailing empty paragraphs during remark -> markdown
Parsing issues
standalone URLs in markdown are converted to links in the visual editor
After commit c25a7c4, whenever a change is made in a markdown editor in a list control, the other fields of the list control get reset to their original value (when the file was read).
This issue can be appended to include various bugs that are found in the new editor. When fast fixes are complete, any remaining issues here can be converted to standalone issues.
Inline node processing issues
Inline nodes need to be processed alongside surrounding text, and be subject to surrounding marks, while still having their children processed as required.
Escaping issues
![
becomes!\[
\n
) and line break(trailing double space or backslash)
UX issues
Parsing issues
(addressed here: fix backward delete of nested inline void node ianstormtaylor/slate#1202)
Related issues
The text was updated successfully, but these errors were encountered: