If you have an email ending in @hotmail.com, @live.com or @outlook.com (or any other Microsoft-related domain), please consider changing it to another email provider; Microsoft decided to instantly block the server's IP, so emails can't be sent to these addresses.
If you use an @yahoo.com email or any related Yahoo services, they have blocked us also due to "user complaints"
-UE
I don't like it. The font it has when you type stuff is weird, and Firefox's auto-spellcheck doesn't work on it.
Comments
I was just about to make this thread.
Change bad.
Even though I can get to the html, I cannot manualy clean it up and fix annoyances with it. Stop turing a br tag into a wrapping p tag, they are not the same thing.
What the hell IJBM, what the hell?
Information?
What is even that?
I'm not seeing a way to shrink/strike text.
...Dislike. :<
Hahaha!
Awe, what the hell
By the way, in this new editor, pressing enter makes a new paragraph. Pressing shift+enter makes a new line.
That makes no sense to me.
Strikethrough doesn't work properly.
Very little seems to work right.
well, that's interesting: vanilla must be stripping the style attributes the editor is adding.
Vanilla is stripping IJBM?
Vanilla / IJBM OTP
It's stripping your text because it wants it's way with you.It made it impossible to comment on the activity page T_T
Yeah, I wanted to tell Juan Carlos that's Lilly
Yeah it does seem pretty terrible.
Instant dislike for not allowing the Chrome spellcheck addon to work.
let's try that again while not on my alt account.
Spellcheckers probably don't pick this up since this typing box is essentially an html document, however, the source editor does work with spellcheck since it's a normal textarea. Odd that the old cleditor was picked up since it's essentially done in a similar fasion.
As for activity, it should be disabled on there now.
Also at the bottom of the box it says:
Path:p
yeah, that's a feature of sorts. it shows what tags you have open and how deep into them you are: insert a strikethrough or something similar and it should add >span until you stop using strikethrough text at another point.
asdfsadfasdfkjsdlfjsdlj
On the plus side, now command+key works in Chrome. But no flipghifng spellcheck.
You do know a workaround for spellcheck is to hit the HTML button and it should work then, right? :P
That aside, I don't know how possible it is to do with this style editor, since most spellcheckers in browsers probably only look for textareas or text input elements. What's odd is that the old one should be similarly setup to how this one is.
The spellcheck only works if you type your message directly into the HTML window and not on already typed in text
it worked for me typing in here and then hitting html; I got tons of red lines due to keyboard mashing (using opera here). seems chrome and firefox (which had spellcheck disabled for me; I had to manually right click and hit check spelling for it to redline stuff) don't do so. I never really used spellcheck much in-browser, so I don't really know the normal behavior of the browser's feature anyway :P
Think I might've found something for spellcheck, gimme a few.
Eh, if a majority supported a revert to the older version I would too.
I'd support a revert, unless I'm missing some obvious benefit I was unaware of.
The main reason we went to a new editor is due to an unresolved issue in cleditor with handling what the enter key did across browsers, which for some browsers, broke toggleboxes.
Oh, right, that. Yeah, that is a benefit...
test
test
test
Wait, no, they don't work this way either...
Now they do :P Turns out it adds
tags around the toggle button too.
Spellcheck should exist now