112 karma · joined August 21, 2024
https://lists.freebsd.org/pipermail/freebsd-chat/2011-Novemb...
HTML was originally based on SGML, which no one ever implemented correctly. The standard then hopped onto the XML bandwagon and more parsing hell ensued.
Remember when in old browsers you had to eliminate all whitespace between elements just so you could style a list correctly? Or traverse the DOM in JavaScript without hitting nasty textNodes? The HTML would be difficult to write AND difficult to read for those browsers.
Author goes on to ask what the rendering of an HTML fragment looks like and then pulls out a CSS rabbit trick. The real answer is "depends on the user agent".
The CSS rules for whitespace handling were added to make predictable whitespace handling easier to achieve across the entire document. Everything can be a footgun in the wrong hands.
HTML is absolutely not in the same realm as programming languages. Quoting strings brings a whole slew of new problems with them. Not in the least another round of parsing hell in the browsers. But also everywhere HTML is concatenated to create a page. Since HTML had to be forgiving, closing tags can be implied. That alone accounts for some of the differences in whitespace handling between the beginning and end of a given text. Browsers tend to do mostly the right thing in those cases.
And if the author tried to be exhaustive about whitespace behaviour in HTML, I wonder why there's also no mention of the WBR element or its corresponding unicode character.
This has already gone way too far.
idk, perhaps he should see a shrink.
The point I was trying to make is that many "news" articles aren't really new. It's not unheard of that the publisher just wants your attention so they'll keep rehasing old stuff.
After 2 years, the control group all sat in a corner of their cage being fat and lazy. The other group continued powering their ferris wheel generators and were not being lazy at all.
They hypothesized that too much food made the body more prone to free radicals and the damage was more difficult to repair in the control group. Effectively making them age faster than the diet group.
ACRORD32.EXE was actually cmd.exe
WINWORD.EXE was actually Mozilla
...and so on
Edit: one of those exes was regedit and every time I sat down I'd delete all the keys named Policies as a routine excersize. After that, restart explorer with one of the tricks. I don't remember the specific one but it wasn't officially documented iirc.
https://superuser.com/questions/335917/how-can-you-do-a-clea...
https://www.theverge.com/2024/10/9/24266419/internet-archive...
linksys everywhere.
https://www.amazon.com/Wenqik-Cushion-Vibrator-Pressure-Acti...
That's enough wtf for me, I'll leave the Internet for a while.
As someone with a failed attempt, I hope this doesn't set an example for others to an hero.
WordPress continues to function in airplane mode with the airplane mode plugin.
And besides, you have to start somewhere. There could be a bunch of independant plugin and theme registries just like there are with Minecraft mods and resource packs. GitHub already serves this purpose for me with WordPress.
Much good could come from this.
finger, ftp, ssh, talk, telnet, tftp, maybe whois too?
The author went through the trouble of figuring out the protocol but never bothered to just run dict. Okay.
WordPress ;)
Beat that! ;)