#dev | Logs for 2019-07-18

« return
[01:44:32] <chromas> Seems like the type of thing that should be default
[02:13:06] <Bytram> I suspect it might be somewhat intentional. I well-remember the "page-widening troll" that haunted /. for a few months. Wreaked havoc on their site. The solution was to introduce a space in any string of 40[*] or more alphanumeric characters. [*] I think that was the size; not certain, but am sure it's in the ballpark.
[02:13:45] <Bytram> HMTL would naturally do a line break on any space or punctuation char (IIRC), hence the preceding restriction.
[02:14:17] <Bytram> Or, it may be that it is late and hot and I am misuunderstanding the issue. Anyway, help it is of some help!
[02:14:55] <Bytram> Time to check out my inner eyelids for a while.
[02:15:03] <Bytram> Have a great night everybody!
[02:39:40] <chromas> Not sure how it works with wrapping but there's a max-width property that could be set
[10:47:26] <SemperOSS> Unless it creates a specific problem, I agree with fyngyrz that code blocks should retain whitespace, especially now that languages like python are actually dependent on correct indentation
[10:48:37] <SemperOSS> If width becomes a real problem, we could consider restricting the size of the bounding box for code and apply scrollbars right and bottom for excessive code chunks
[10:54:05] <fyngyrz> The CSS I suggested maintains whitespace and line breaks but ALSO will wrap at the edge of a window. This prevents the "page widening" problem, yet keeps code formatted as long as there is room in the block.
[10:55:44] <fyngyrz> Back in the day, when /. was built, there was no such CSS. You had either HTML <pre> or not, and that _would_ cause page widening.
[10:56:11] <fyngyrz> Now we have better choices. Ideally, they'd be used. And it really is an easy fix.
[11:08:49] <Bytram> kewel!
[11:08:59] * Bytram stands^W sits corrected.
[11:09:10] <Bytram> indentation++
[11:09:10] <Bender> karma - indentation: 1