Timeline for Multiple spaces in code in comments get merged into one
Current License: CC BY-SA 2.5
22 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
May 23, 2017 at 12:35 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
Mar 3, 2014 at 12:40 | vote | accept | Abel | ||
Feb 21, 2014 at 12:05 | history | edited | balphaStaffMod |
edited tags
|
|
Feb 21, 2014 at 12:05 | answer | added | balphaStaffMod | timeline score: 11 | |
Feb 22, 2013 at 23:12 | comment | added | Lorem Ipsum | @Oded I don't mind the flooding; in fact, I'm happy the devs are closing/fixing bugs. However, without a comment/answer, I don't know if you mean "This is so old that changes since then have rendered it invalid" or "This is so lame that I don't care to respond" or "This is how it will be and I'm not going to fix it" | |
Feb 22, 2013 at 14:50 | comment | added | Oded StaffMod | @LoremIpsum - Sorry, trying to close old old old bugs. Didn't mean to flood the front page. | |
Feb 22, 2013 at 14:49 | comment | added | Lorem Ipsum | @Oded Can you at least post an explanation as to why it is status by design or declined instead of simply flooding the front page with your retagging? | |
Feb 22, 2013 at 14:36 | history | edited | OdedStaffMod |
edited tags
|
|
Mar 22, 2012 at 6:52 | comment | added | Arjan | No, @Lri, they are not. (See the HTML page source for this comment.) | |
Mar 22, 2012 at 6:21 | comment | added | Lri | @Arjan But aren't newlines removed before the CSS anyway? | |
Mar 21, 2012 at 17:15 | comment | added | Arjan | I guess not, @Lri, as pre-wrap also enables newlines? Those don't get any love in comments. | |
Mar 21, 2012 at 0:27 | answer | added | Stéphane Gimenez | timeline score: 1 | |
Dec 14, 2011 at 16:09 | comment | added | Chris Down | This is still an issue, and now unicode nbsp doesn't work either (at least as far as I can test). | |
Jul 7, 2011 at 2:49 | comment | added | Lri |
Couldn't code {white-space:pre-wrap} be added to the SE default stylesheets?
|
|
Nov 30, 2009 at 0:05 | vote | accept | Abel | ||
Dec 19, 2011 at 15:26 | |||||
Nov 30, 2009 at 0:05 | comment | added | Abel | Firefox is correct in copying, but not in selecting. Unfortunately, the W3 and other standards bodies say little if anything about how selections are supposed to look (or what Ctrl-C should copy consecutively), that's totally up to the UI. | |
Nov 21, 2009 at 23:21 | comment | added | perbert | @Abel: you are right, Chrome doesn't like it either. It must be because generally in HTML 1+ space becomes 1 space. I think that firefox's (pronounce it out loud, I dare you) is the correct behavior in this case. | |
Nov 18, 2009 at 13:37 | comment | added | Abel |
I used Opera (doesn't work). Now tested with IE (doesn't work) and FF (works). Looking at the code (<code>with </code><code> multiple </code><code> </code><code> spaces</code> ) there are spaces (but most space is created by CSS), but when selecting they aren't "blue" in any browser, and only FF copies them. Interesting little browser quirks.
|
|
Nov 17, 2009 at 23:37 | comment | added | perbert | @Abel: What is the problem? On FF, If I select the text and paste it I get the spaces on the pasted text. | |
Nov 17, 2009 at 22:05 | comment | added | Abel | @voyλger nice alternative workaround (but try to select and copy it). | |
Nov 17, 2009 at 20:29 | answer | added | perbert | timeline score: 1 | |
Nov 17, 2009 at 2:28 | history | asked | Abel | CC BY-SA 2.5 |