Skip to content
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

Markdown editor fast fixes - 0.5.0 beta #575

Closed
20 tasks done
erquhart opened this issue Sep 1, 2017 · 2 comments · Fixed by #653
Closed
20 tasks done

Markdown editor fast fixes - 0.5.0 beta #575

erquhart opened this issue Sep 1, 2017 · 2 comments · Fixed by #653
Assignees
Milestone

Comments

@erquhart
Copy link
Contributor

erquhart commented Sep 1, 2017

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

Related issues

@erquhart erquhart added this to the 1.0.0 milestone Sep 8, 2017
@erquhart erquhart self-assigned this Sep 13, 2017
@tech4him1
Copy link
Contributor

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).

@erquhart
Copy link
Contributor Author

@tech4him1 thank you, added to the list.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants