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 17, 2021 at 19:43 | history | edited | Ben KellyStaffMod | CC BY-SA 4.0 |
added 88 characters in body
|
| Jan 29, 2021 at 22:43 | comment | added | Ben Kelly StaffMod |
There's still some edge cases here I can think of, even using _. This is going to require a bit of thought and a few unit tests. Thanks for the report!
|
|
| Jan 29, 2021 at 22:40 | history | edited | Ben KellyStaffMod | CC BY-SA 4.0 |
added 156 characters in body
|
| Jan 29, 2021 at 22:34 | comment | added | Ben Kelly StaffMod |
Ah, this is clever. In a way, you've created illegal content in the rich-text editor that isn't actually supportable in the backing markdown. The editor is "smart" enough to generate what would be sane markdown, but isn't actually valid due to the introduced ambiguity. I guess the solution here is to default weak emphasis back to _ in the case of an overlap since that is valid
|
|
| Jan 27, 2021 at 16:12 | comment | added | Konrad Rudolph |
@animuson It could potentially be handled by using _ for italics but personally I’d be more comfortable with forbidding overlapping formatting, but that’s admittedly fairly opinionated since it (arguably) prevents “valid” markup.
|
|
| Jan 27, 2021 at 16:11 | comment | added | animuson StaffMod |
The editor seems to have functioned correctly here. It split the italics. So you have a **this is bold, *now italic*** using three asterisks to close the bold and italics and then a *, and now?!* to re-enter the remainder of the italics for the part that was outside of the bold. The problem is that the parsers we have do not handle the scenario of four consecutive asterisks because of the ambiguity. I'm not sure how that's supposed to be handled.
|
|
| Jan 27, 2021 at 16:04 | history | answered | Konrad Rudolph | CC BY-SA 4.0 |