#dev | Logs for 2019-07-22

« return
[17:59:15] <fyngyrz> TheMightyBuzzard: <code> tags appear to be doubling up on spaces now? They should be one em, no?
[17:59:26] <fyngyrz> here's what it looks like in preview: http://fyngyrz.com
[18:00:09] <fyngyrz> that's 4 spaces in the entry box, should land with the foo starting after the 2nd letter 't' in 'test'
[18:01:24] <fyngyrz> a tab is also 8 spaces - I guess someone might like that, but 4 is better. :)
[18:02:14] <fyngyrz> 8 spaces cuts the number of indents that will fit in half. But the doubling of spaces is the real problem here
[18:02:25] <fyngyrz> that's just odd
[18:14:58] <Bytram> fyngyrz: Support for "<code>" has been... problematic on SN. I use "<blockquote>", instead. That said, I would much prefer to use "<quote>" as (1) it *is* a valid element (2) it is less to type, and/but (3) beware we have gobs of each already in the DB, so any changes need to be non-impacting to previous stories/comments/etc.
[18:19:45] <fyngyrz> reaching for a space to actually equal a space in <code> tags is not, IMHO, something one should avoid. As for using <quote> etc., that's absurd. If I want to drop some code here, I would have to edit all the indents to <quote> tags? I mean, if you're writing something live, maybe it's not quite the devil's breakfast, but for actual code blocks... nuh-uh.
[18:20:47] <fyngyrz> there's no reason for fixing the <code> tags to impact <quote> tags, either
[18:20:54] <fyngyrz> they're entirely different CSS.
[18:21:29] <fyngyrz> unless... the pasted content between the tags is actually being modified, and if that's the case (tears at hair)
[18:35:24] <Bytram> fyngyrz: Oh, so sorry! I saw "<code>" but somehow read "<quote>"! IOW never mind!
[18:36:32] * Bytram notes he has very a restricted resource of remaining hair which can be removed.
[18:43:05] <fyngyrz> lol okay - thought that was odd. :)
[18:44:04] <fyngyrz> I'm still just trying to see if the <code> tags can work in a reasonable mamner:
[18:45:57] <fyngyrz> <code style="white-space: pre-wrap; font-family: monospace;">stuff</code> would work fine, for instance. If that could be made to be allowed.