91–100 of 102 posts
If it were a WYSIWYG editor, there'd be previews for images. But it seems like it's just syntax highlighting for textareas. Nice project either way, but false advertising.
I can type text, mark it, click "B" for bold and it works. This is WYSIWYG minus images.
This isn't really WYSIWYG because it keeps the formatting symbols like * or # etc.
My life-long gripe is that Microsoft Word forms the basis for what people think text editing is and should be. This could be incredibly useful for developers though.
Two issues I saw:
- on my phone, the framerate noticeably drops as I scroll over the widget
- caret positioning within the textarea seems to desync against the letter positions in the highlighted div
And the whole concept severely constrains the styling choices that could be applied to the highlighted output, but I suppose that was a given.
At least it works in my Sciter like this:
textarea::mark(myHighlight) {
background-color: yellow;
color: red;
}
Lorem ipsum dolor sit amet
// Select a range of text to highlight
const range = document.createRange();
const textNode = document.querySelector('textarea').firstChild;
range.setStart(textNode, 6); // Start at the 6th character
range.setEnd(textNode, 11); // End at the 11th character
// Highlight the range
range.highlight("myHighlight")
Earlier quoted context omitted.
I can type text, mark it, click "B" for bold and it works. This is WYSIWYG minus images.
WYSIWYG does not refer to the icons in the toolbar, but rather the text itself. This is not WYSIWYG because when I make something bold, I see a bunch of asterisks around it. Still a cool project, but someone who does not understand markdown would wonder why pressing the heading button makes my text into a hashtag instead of making it bigger.