Comment #5 on issue 15674 by jeff.allen: <pre> in CONTENTEDITABLE differs from Firefox behavior http://code.google.com/p/chromium/issues/detail?id=15674
I noticed this behavior because it also makes cut and paste of code into a blog posting do exactly NOT what you want: When you type "the code should look like this...", then choose "preformatted" off the menu, then paste in the code, you get an extra newline between each line, which is really annoying. Instead of complicating the bug report with all the cutting and pasting, I found that you can see Firefox's useful behavior and Chrome's irritating behavior with just "hit return", so I reported it that way. If Firefox is breaking the standard, they are doing it because of Do What I Mean, which is much nicer than Do What W3C Thinks I Mean. (It could be the right solution to this problem is make pasting behave differently than typing. I don't really have a complaint about "<return> starts new block, even in <pre>" as a policy.) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
