The charms bar is a strange thing. I had problems getting to show when I wanted it, and problems getting it to not show when I didn't. Rather like some idiot cousin it seemed to do the opposite of what was needed. IMO the whole implementation was retarded. There was a hack (registry? I can't remember now) to stop it showing up when mousing to the middle right of the screen, but I still couldn't disable it properly, even what it was no longer needed (i.e. when the lightweight start menu introduced a more user-friendly way of shutting down.)
Oh yes, and not all of it's been good. But hopefully now that idiot Forstall been shown the gutter things will improve. I think MS looked at what Apple were doing and tried to beat them to the logical conclusion, thereby showing the world how unhelpful the logical conclusion is. What works on a mobile device doesn't necessarily work on a desktop (et v.v.). I can't imagine why anyone would've thought otherwise. hey ho.
Yeah, I realise that BH creates the visual representation of paragraphs by inserting line breaks. What I meant was that in order to create this effect on mobile I pressed return twice. But on desktop I have to do it three or four times (just tested...this is IE10 on W7). The first return gets a new line, then two or three may be needed for the next line.
No, I know. I didn't mean to imply that BH was converting double line breaks (either <br> tags or \n) to <p> tags, simply the visual appearance of paragraphs (blocks of text with whitespace between.)
And the problem with multiple returns seems to be odd. As I noted, I was posting on IE10/W7. Now I'm posting on Safari 7, Mac OS X 10.9 and returns behave as expected. But then the quote function is also working now (it wasn't this morning on IE10).
As Alice said, curiouser and curiouser...
Edit: (BTW, IE11 was one of the unwelcome additions that came with W8.1, I found that it broke a few websites, including WYSIWYG text editors. Strange that we seem to be having the opposite experience here.)