开云体育

I wrote:

As readers of beta@ may know, there's a test of a new message editor afoot, which users can volunteer to join. So if you're the sort of person who likes to puzzle out a new feature, acid test it, and report your findings, you might want to give it a spin.

I did, and am using it now.

Ok, that was unexpectedly awkward. I used the speech bubble button on the left of the formatting bar to insert a quote my prior message, then tried to break it into sections as I normally do to make inline comments like this one. Inserting and removing newlines did not break it. Nor did attempting to Decrease Indent. Then I noticed that the?“ (Blockquote) button was pushed. So I selected my inline text and un-pushed it. Rather than removing the Blockquote attribute from just my inline text, it removed it from the entire quoted message. Fine. So I re-applied Blockquote on the prior section and moved on.

It currently suffers one of the problems that (I think) got fixed in the old one: if your group "normalizes" HTML it nevertheless allows you to use and see in WYSIWYG formatting features that get stripped by normalization.

I reported this one and Mark reports it to be fixed. I haven't retested it.

One of the fun things is an insert tool for special characters - Ω is the button icon for it. → It is a limited set ← but has many of the more useful glyphs.

I noticed in a view source of my message that the special characters are inserted as named . This probably explains how those particular glyphs were chosen. I tried to insert other Unicode glyphs using the < > (Source code) mode to insert them as numeric references, but that failed. They got converted to asterisks by the editor. Some kind of exploit defense perhaps?

Shal

?