beth (defunct)

@bethposting

rip

she/her
bsky.app/profile/bethposting.bsky.social

i guess follow me @bethposting on bsky or pillowfort

discord username:

bethposting

beth (defunct)@bethposting3/22/2023, 4:31 AM

beth (defunct)@bethposting

beth (defunct)@bethposting3/21/2023, 10:34 PM

ing bad

#Breaking Bad # # #html

@rem3/21/2023, 10:36 PM

when handcoding my website i very specifically went and put terminating slashes on all the self-closing tags and then a week later read it's actively discouraged to do that and very specifically went and took them all back out. html is SO cool. it's like all the sludge and weird technical debt of the rest of tech, but objectively so much less evil

beth (defunct)@bethposting3/21/2023, 10:37 PM

oh damn i gotta go edit some posts

(jk eh it's not worth it but good to know for the future)

beth (defunct)@bethposting3/21/2023, 10:38 PM

tag urself: 1. 2. 3.

beth (defunct)@bethposting3/21/2023, 10:45 PM

i also just learned about this today. stack overflow sez apparently most modern parsers will just strip out the slash and it ends up being just   underlyingly no matter which one you write, so i guess there's no real reason to put it unless you want your stuff to work with old browsers

beth (defunct)@bethposting3/22/2023, 4:31 AM

on the other hand, the cohost markdown reference has a written out

https://cohost.org/rc/content/markdown-reference

# #markdown reference

You must log in to comment.

in reply to @rem's post:

Chimerelda E. Error, layabout @chimerror3/21/2023, 10:40 PM

It is‽ Well screw that, I like them

@rem3/21/2023, 10:42 PM

absolutely! to be clear they're not invalid html, the slashes are just ignored by compliant html parsers, but therefore are prone to break buggy parsers

Chimerelda E. Error, layabout @chimerror3/21/2023, 11:14 PM

That's their problem then, lol

@rem3/21/2023, 11:15 PM

agree! i have no real justifications for a lot of my prescriptions other than 'i just like the validator to yell at me as little as possible'

nortti OH1CAU @nortti3/22/2023, 12:15 AM

terminating slashes on self-closing tag have never been part of HTML per se. HTML 5 parser ignores them as a compatibility hack for (vast majority of) XHTML pages, probably so that a user agent doesn't need to implement two similar-but-incompatible parsers

(specifically, XML has no concept of a self-closing tag, so all such tags were converted to an opening-closing pair. in XHTML <tag/> is just shorthand for <tag></tag>, whereas in HTML 5 <tag/> is equivalent to <tag>. this does mean in XHTML you could do stuff like <div/> to create an empty div which would no longer work in HTML 5, but I guess it was rare enough they did not care to add further corner cases)