11:49:52 hi, anyone else experiencing issues with discourse backed sites? 11:51:23 the couple ones I checked right now are as usual with noscript: they load, but Atwood's "IE6-level" CSS revert keyword means overflow is left at hidden 12:07:29 hm, for me it is unscrollable :/ 12:07:38 e.g. https://discussion.fedoraproject.org/t/amdgpu-fatal-error-during-gpu-init-on-5-19-8-works-on-5-19-6/75827 12:10:09 onnly way to move around there is with caret browsing 13:41:35 hrosik: javascript:(void(function(){s=document.createElement("style");st=document.createTextNode("html,*{overflow:unset!important;}");s.appendChild(st);document.head.appendChild(s);document.body.appendChild(s);}())) 13:42:00 quick and dirty, bookmarklet to add a style to override the overflow properties. 13:42:45 if unscrollable is the only thing you get, something like that might be enough, if the list of sites you browse that rely on discourse is small, you can add something to userContent.css too 13:43:00 the problem is their noscript style, supposedly to make it scrollable, relies on "revert" 13:43:27 which in turn IIRC is implemented using the rust styling code 15:55:09 njsg: thanks for the pointer! 15:55:41 njsg: re rust styling code - meaning this is something SM doesn't have (yet)? 16:00:58 anyway, would I really be asking too much to use plain old (X)HTML? Are really megabytes of javascript framework that generates what could easily be done once a comment is added (and the associated wasted energy) needed to display and navigate a comment thread? 17:31:53 Push! Things! Forward! 17:32:02 it's like the folks that encourage using COMPILERS to make websites! 17:32:47 like, author your site in some weird language, run Magic Web Compiler™, and get something that resembles HTML+CSS 17:33:06 at best that's all you get (like those static site generators like Hugo), and you're good to go 17:33:29 at worst you end turning something obscure into a JS framework hellstew that won't degrade grafecully 17:33:32 --gracefully 17:59:28 anyway, would I really be asking too much to use plain old (X)HTML? [...] Yes. Unless I am in charge.. Vote Tobin.. You could do a lot worse! :P 18:01:26 tomman: know how you do a static site generator? have php do it and just .. save the output and boom static site.. HELL many early perl and php systems merely wrote out to disk.. 18:02:12 that's so convoluted that might have a chance to stick... in 2030 :D 18:03:14 in the context of levels of survival one is prepared to accept.. is small dynamic control panel but system craps out static pages to a cdn backed server.. keeping active server code where it needs to be.. not just shoving everything to the webclient but respecting the world wide web 18:04:18 New theory: nobody does server-side rendering anymore and push everything to be rendered on the client with tons of icky JS toxins because we're in a Serverless™ world 18:04:28 can't really do server-side without a server, amirite? /s 18:05:21 besides that all isn't something people(tm) do they pay some fuckin domain hussler to fill out a limited wysiwyg webapp that writes their website for them.. like a front page via microsoft word if it actually worked worth a crap.. but of course still mediocre today 18:05:43 or just use discord youtube twitch bluesky and facebook 18:05:59 and not have a web zone 18:06:37 how the HELL are you supposed to be able to get pizza rolls via people emailing your web zone if you ain't got one 18:07:04 nuuummmbbberrr fffooouuurr 18:07:05 err 18:07:12 I don't have fond memories of MS Office generated HTML 18:07:31 Word 97 required a wizard for that and the results were... not great. But then the Internet back then was... not great either :D 18:07:49 i used hotdog professional originally 18:07:52 Word 2000 generated... that hodgepodge of custom XML namespace vomit that also included VML 18:08:02 then went frontpage 2000 then dreamweaver then notepad++ 18:08:10 suppose i used composer for a minute 18:08:11 too 18:08:19 but you know me.. All about that navigator 18:08:36 Eventually when I jumped ship to OpenOffice/LibreOffice, those generated more abominations, but at least it was standard HTML... that rendered poorly everywhere :D 18:09:07 i still run office 2003.. well i did until i went linux.. suppose i still do in a vm 18:09:08 for that you want an addon called Writer2XHTML, which generates 1) cleaner, proper XHTML, and 2) tons of redundant CSS rules that require 1-2 hours of work to simplify them 18:09:37 i still use LO Writer with that addon to pre-author reports for our webapps at work (that are eventually supposed to generate PDFs) 18:10:24 model the report in Writer, export it as XHTML, cleanup all that dodgy CSS, import it into your server-side framework, put the magic tags to output actual content, and pass the output HTML through a HTML to PDF filger 18:10:24 i wish seamonkey was a development/office/communications/web suite but those other things are not in the navigator.. in a PERFECT WORLD SeaMonkey would basically be an operating environment 18:10:27 boom, reports~! 18:10:49 like i could just have a window manager and seamonkey and that is your system.. that was the PROPER FUTURE 18:10:53 make no mistake 18:23:34 hrosik: in this case, I think the problem might be that whoever wrote the noscript code doesn't know the requirements for that code 18:24:03 hrosik: as in, discourse does try to work, at least for reading, with JS disabled, but does so in a way that requires that feature. 18:28:01 tomman: my experience is that MSO HTML output tended to try to replicate inner workings of their formats, which tended to be poor for webpages 18:28:27 not that e.g. word content couldn't use html-like markup, their users probably don't use styles as much as they should 18:28:38 njsg: that was a often quoted advantage because you could take said MSO HTML, load it back in Word (or whatever) and edit it back like if it was a native doc 18:28:45 without losing the original format 18:29:53 nsITobin: yes but SeaMonkey would then need (1) LaTeX support (2) a LISP 18:30:05 but I guess JS is quite lispy already 18:31:01 if i want to have seamonkey on my new slowly materalizing distro i will have to build rust and cargo my self.. which may be beneficial later on