The code under the return statement is unreachable and hence rendered useless.
https://github.com/charlyllo/writty/blob/b0db2bebd5cd0bcadf50e16981510496b35e01c0/writty.js#L24-L32

Current behaviour

Anchor tags are no clickable inside the editor.

Expected behaviour

Anchor tags should be clickable inside the editor.

Hi, found your editor via prototypr.io and looks good! Just wondering why you went with removing the outline on everything using css? Tried to use it while navigating via the keyboard and can't tell which object I'm focused on.

Cheers!

Would be nice to have a Sync mode attached to a file in the Google Drive or at least being able to import the exported texts.

Thanks.

Saw this on Product Hunt. Congrats on the launch!

Would you consider building this into a generic editor that could be embedded, similar to Quill JS? Perhaps as a native React component?

I really like the functionality and the default styling, but I would be much more interested in embedding this into a product I am currently building called NoteBrook than I would just directly using this as a browser.

Some CSS updates are required to fix some minor bugs and improve visuals.

That would be great to paste images in clipboard with CTRL+V.

Thanks!

Hello!

I've found a bug that occurs when you have multiple lists of elements in the text, and you change the text type to "body" while multiple lists are selected. All lists get merged into a single list, placed one after another starting at the position of the first list.

Example:

When all text is selected and changed into "Body", the output is:

(another bug: numbers in a numbered list always get converted into 1s when a list is converted to "Body")

Now, this doesn't always happen. If you just write random paragraphs and lists, things might work as expected. I suspect the bug is due to some markup present in the above example, but haven't figured out the exact cause yet. Also, it doesn't seem to happen when you change to other types than Body.

Below is an example of markup (saved by Writty) on which the bug does occur. Change the file back to .html and open it in Writty.

bug.txt

Hi! This extension doesn't work on my chromebook. It uses Chrome Version 58.0.3029.140. Yes, I know that machine is quite old, but I use it just for typing text, so it would be nice to be able to use this extension. Is there any way to make it possible?

Hi. Would be nice if the extension has an option for capturing new tabs. Thanks.