#dev | Logs for 2019-09-30

« return
[12:55:43] <TheMightyBuzzard> sure
[12:55:48] <Bytram> <ecode> and word wrap, continued.
[12:55:49] <Bytram> https://dev.soylentnews.org
[12:56:46] <TheMightyBuzzard> i see it. it shouldn't wrap like that.
[12:57:08] <TheMightyBuzzard> needs to have a horizontal scroll bar or truncate at the edge of the div.
[12:58:00] <TheMightyBuzzard> that's css changes though not site vars
[12:58:17] -!- janrinok [janrinok!~janrinok@Soylent/Staff/Editor/janrinok] has joined #dev
[12:58:25] * TheMightyBuzzard waves at janrinok
[12:58:34] * janrinok waves back
[12:59:10] <Bytram> I tried a horizontal scroll bar... and when I edit and preview the story, they are there, but when I just view it as a story, I do not see them any more.
[12:59:27] <Bytram> (given my druthers, I would prefer scroll bars over truncation)
[12:59:28] <Bytram> see:
[13:00:00] <Bytram> https://dev.soylentnews.org
[13:00:44] <TheMightyBuzzard> ain't no scroll bars for me on view, edit, or preview
[13:01:16] <Bytram> I just saw them earlier... hold on
[13:02:09] <Bytram> What I had before:
[13:02:11] <Bytram> <blockquote><div style="width: 30em;overflow-x: auto;white-space: nowrap;"><p><tt>
[13:02:17] <Bytram> scratch that
[13:02:25] <TheMightyBuzzard> grab a browser extension like stylish and get it working locally before monkeying with the templates on dev if you would. easier to keep up with what was done.
[13:02:28] <Bytram> <blockquote><div style="width: 100%;overflow-x: auto;white-space: nowrap;"><p><tt>
[13:02:48] <Bytram> not planning to change templates
[13:03:13] <Bytram> just want to update the site vars are: approvedtags_attr and approvedtags_attr_admin
[13:03:22] <TheMightyBuzzard> should be. ecode needs to be doing that in comments by default.
[13:03:34] <TheMightyBuzzard> and everywhere else for that matter
[13:04:05] <Bytram> no, that's the problem.... it does NOT do that. what Iposted above is my attempt to overcome that wrapping behavior.
[13:04:08] <TheMightyBuzzard> well css files not templates
[13:04:17] <TheMightyBuzzard> yes, i know, but it should.
[13:04:17] <Bytram> I ain't touching those!
[13:04:22] <Bytram> I agree!
[13:05:30] <TheMightyBuzzard> so grab stylish, monkey with local css overrides until you find one that covers the whole site, and then make a PR or let me know what to put in one of my own.
[13:05:37] <Bytram> better still, instead of inserting "&nbsp;" between every other space character, it should be using (I think) white-space: pre or similar
[13:06:00] <TheMightyBuzzard> prolly
[13:06:30] <TheMightyBuzzard> save db space anyway
[13:06:36] * Bytram hasn't used stylish in years
[13:07:09] <Bytram> Excellent point!
[13:07:32] <TheMightyBuzzard> it's way handy for working on css
[13:07:32] <Bytram> what the site does to ascii-fied tables output by mysql is... painful.
[13:10:20] <Bytram> do I have to wildcard the spec for documents to match or does it just see if the part provided is a proper subset of the URL to be compared against?
[13:10:22] <TheMightyBuzzard> okey doke, time to go rent some light earth moving equipment and put a bunch of dirt in more aesthetically and functionally pleasing locations than it currently is.
[13:10:40] <TheMightyBuzzard> ... i have no idea what you just said
[13:10:46] <Bytram> yeah, how's the house coming along?
[13:10:55] <TheMightyBuzzard> too slowly
[13:10:57] <Bytram> @namespace url(http://www.w3.org/1999/xhtml);
[13:10:57] <Bytram> @-moz-document url("https://dev.soylentnews.org/") {
[13:11:14] <Bytram> or do I need more in the moz-doc thingy
[13:11:18] <Bytram> @-moz-document url("https://dev.soylentnews.org/*") {
[13:11:40] <TheMightyBuzzard> oh, the former i think but you'll find out quick enough
[13:11:50] <Bytram> thanks.
[13:12:43] <janrinok> go move some mud, excavate some earth, shift some soil, displace some dirt or whatever
[13:12:55] * Bytram is starting to get a bit lost; have > 100 tabs open
[13:15:30] <janrinok> Bytram, everybody can see the report story being delayed in the stories coming up, do you want to hide it for the time being, or release and worry about solving this particular problem later. It doesn't change the outcome of the investigation and they have been waiting over a month already?
[13:18:58] <janrinok> Perhaps add a one-liner explaining some of the investigation details are not easily displayed on a cell phone?
[14:19:04] <Bytram> TheMightyBuzzard: I do not see a way to use css in the *generated* html to implement this.
[14:19:13] <Bytram> Basically I am trying to find out if I have:
[14:19:40] <Bytram> blockquote div p tt
[14:19:45] <Bytram> and, if I do,
[14:19:56] <Bytram> then apply the styles to the *DIV*
[14:20:51] <Bytram> as the "blockquote div p tt" is generated by the site, it seems to me to need to be the one to add the stying to the div.
[14:21:28] <Bytram> as far as I can tell, there is no selector that says "do this if I have a child that is $foo and a grandchild that is $bar
[14:23:13] <Bytram> for example, see: https://stackoverflow.com
[14:34:14] <janrinok> Bytram - in your report the link to "The circumstances surrounding the making of the Journal Entry are elaborated upon in this comment" no longer works for me. Para 1
[14:35:03] <Bytram> Huh? Ruh Roh!
[14:35:20] <Bytram> THANKS!
[14:36:09] <janrinok> I'm not sure which of the comments it refers to so I cannot edit it myself
[14:36:30] * janrinok thinks that there are two that it _could_ be referring to
[14:38:25] <Bytram> looks like rehash ate some "&" chars. :P
[14:39:04] <Bytram> got 1st one working; checking 2nd
[14:39:28] <Bytram> (elaborated upon)
[14:40:13] <Bytram> got a working link for that one, too