Jump to content

Edit History

Llyarden

Llyarden

Not sure if these should be feature requests or bug reports.

1) Creating an inline dice through the WYSIWYG editor deletes everything between it and the last line break or inline roll. (For instance, if I put an inline die roll at the end of this line, everything going back to the 1) would be deleted)

2) When adding new dice, the source-editor-to-WYSIWYG parser strips out the mwinlinedice-showresults and mwinlinedice-showdetails part of the class, meaning that if you're doing stuff in the source editor, you have to manually reset every single die to show its details/results through the editor UI popup. This can be...tedious, if you have a lot of rolls. Not sure if this also happens if you edit a post that already has dice in it. I guess I can try that now.

...or not, I guess you can't do dice in this forum. Will try it in one of my games. EDIT: No, it's only new dice, extant ones seem to tolerate the parser fine (presumably because they instead have data-showdetails="true" and data-showresults="true" instead of additions to the class.

Llyarden

Llyarden

Not sure if these should be feature requests or bug reports.

1) Creating an inline dice through the WYSIWYG editor deletes everything between it and the last line break or inline roll. (For instance, if I put an inline die roll at the end of this line, everything going back to the 1) would be deleted)

2) When writing a new post, the source-editor-to-WYSIWYG parser strips out the mwinlinedice-showresults and mwinlinedice-showdetails part of the class, meaning that if you're doing stuff in the source editor, you have to manually reset every single die to show its details/results through the editor UI popup. This can be...tedious, if you have a lot of rolls. Not sure if this also happens if you edit a post that already has dice in it. I guess I can try that now.

...or not, I guess you can't do dice in this forum. Will try it in one of my games. EDIT: No, it's only new dice, extant ones seem to tolerate the parser fine (presumably because they instead have data-showdetails="true" and data-showresults="true" instead of additions to the class.

Llyarden

Llyarden

Not sure if these should be feature requests or bug reports.

1) Creating an inline dice through the WYSIWYG editor deletes everything between it and the last line break or inline roll. (For instance, if I put an inline die roll at the end of this line, everything going back to the 1) would be deleted)

2) When writing a new post, the source-editor-to-WYSIWYG parser strips out the mwinlinedice-showresults and mwinlinedice-showdetails part of the class, meaning that if you're doing stuff in the source editor, you have to manually reset every single die to show its details/results through the editor UI popup. This can be...tedious, if you have a lot of rolls. Not sure if this also happens if you edit a post that already has dice in it. I guess I can try that now.

...or not, I guess you can't do dice in this forum. Will try it in one of my games.

Llyarden

Llyarden

Not sure if these should be feature requests or bug reports.

1) Creating an inline dice through the WYSIWYG editor deletes everything between it and the last line break or inline roll. (For instance, if I put an inline die roll at the end of this line, everything going back to the 1) would be deleted)

2) When writing a new post, the source-editor-to-WYSIWYG parser strips out the mwinlinedice-showresults and mwinlinedice-showdetails part of the class, meaning that if you're doing stuff in the source editor, you have to manually reset every single die to show its details/results through the editor UI popup. This can be...tedious, if you have a lot of rolls. Not sure if this also happens if you edit a post that already has dice in it. I guess I can try that now.

Here is a test:1d20

×
×
  • Create New...