Timeline for Opt-in alpha test for a new Stacks editor
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 15, 2021 at 21:05 | history | edited | Ben KellyStaffMod | CC BY-SA 4.0 | added 87 characters in body |
| Feb 3, 2021 at 4:45 | comment | added | Sebastian Simon | Apparently empty elements like <sup></sup> are removed when switching from rich-text to Markdown. Does this also explain why no <code></code> is present when performing the steps to reproduce from It is impossible to place your cursor immediately after an inline code block in rich text mode? | |
| Feb 3, 2021 at 4:25 | comment | added | Sebastian Simon | Please tell me, this editor isn’t using regexes to parse HTML… | |
| Jan 29, 2021 at 21:18 | history | edited | Ben KellyStaffMod | CC BY-SA 4.0 | added 20 characters in body |
| Jan 29, 2021 at 21:18 | comment | added | Ben Kelly StaffMod | Thanks for the report. HTML is... tough and there's still a number of edge cases we're running into. I'll see if I can't get to the bottom of this one, as I'm sure it affects other nested html structures, not just <sub> | |
| Jan 28, 2021 at 9:23 | comment | added | Makyen | In the current editor, any HTML-valid combination of <sub></sub> and <sup></sup> is supported (or at least functional), including nesting one element within another. It might result in text which was too small to read, but it produces the correct HTML output. | |
| Jan 28, 2021 at 9:11 | history | answered | Luuklag | CC BY-SA 4.0 |