ditto
kiwifarms.net
- Joined
- Aug 17, 2019
JSX has brought them back with vengence.Self-closing tags are deprecated and, at best, syntactic sugar.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
JSX has brought them back with vengence.Self-closing tags are deprecated and, at best, syntactic sugar.
Kiwifarms was not the place I thought I'd discover that I've been generating thousands of emails with a bunch of deprecated HTML.Self-closing tags are deprecated and, at best, syntactic sugar. The slash is technically still allowed (on void elements* - anywhere else it is an error), but meaningless. I'd personally discourage using it but it's a possibility that some validator is still expecting you to follow that old standard.
As a general rule it's simply ignored -<br/>
is exactly the same as<br>
, and<div/>
(valid under HTML4) is technically illegal but will be treated exactly the same as<div>
... i.e. a subsequent matching</div>
is still expected.
The question really isn't clear on what the problem is though. I thought he was saying it was adding a line break when it shouldn't be.
*<br>
,<img>
,<hr>
, etc... these elements cannot have any child nodes
Presuming we're talking about HTML5, they're optional, yes, but officially deprecated, no. Personally I still use them everywhere since it's an easy visual cue that the tag doesn't have a close tag anywhere. Yes, I could tell that by reading the tag name, but just seeing the slash makes it all the more explicit and easier to spot. I'd encourage people to keep using them.Self-closing tags are deprecated and, at best, syntactic sugar
<!DOCTYPE html>
as the very first line.I stand corrected. But I'd still say my preference is to leave the slash out, as it's meaningless and I personally don't find that it helps readability.Presuming we're talking about HTML5, they're optional, yes, but officially deprecated, no.
Well you know, it's one step closer to the impossible dream of XHTML and conveniently parsing web content with your favorite XML parser.Self-closing tags are deprecated and, at best, syntactic sugar.
Or, or: did you not copy-paste at all, and instead did you actually type this code live into the Xenforo code box line-by-line? Because I'll absolutely make fun of you for that.
I'd sooner replace xml and html with some s-expression based syntax.Well you know, it's one step closer to the impossible dream of XHTML and conveniently parsing web content with your favorite XML parser.
But given that XHTML is never, ever, ever happening, I prefer unclosed BR's.
Ordinarily I'd disagree and say that we need a human-readable format, but HTML (or as I prefer to call it, the Javascript/CSS+HTML operating system) is pretty much a compiled language at this point anyway. So you know what, go nuts.I'd sooner replace xml and html with some s-expression based syntax.
What can I tell you, it would be terrible, just terrible to have a uniform syntax for the code and markup language. Who needs that anyway? You know what I need? Tags. I need tags everywhere. The more visual noise, the better. I'm not generating data, I'm a fucking code artisan and get paid by the isOddOrdinarily I'd disagree and say that we need a human-readable format, but HTML (or as I prefer to call it, the Javascript/CSS+HTML operating system) is pretty much a compiled language at this point anyway. So you know what, go nuts.
I want this just so we can give front end devs macros that they will poorly implement. The more chaos the better.I'd sooner replace xml and html with some s-expression based syntax.
Still a better commit message than "asdf" or "x".
git commit --amend
(and not pushing after every goddamn commit) is your friend.Or work on a branch, commit, push, amend, force push, who cares?Still a better commit message than "asdf" or "x".
But yeah,git commit --amend
(and not pushing after every goddamn commit) is your friend.
git add .
then pushing a 450MB binary blob by accident.Close. Replace coooomiter with troon who needs to have [[[XER]]] commits validated and you're there.
Or "wip"Still a better commit message than "asdf" or "x".
Work in progress.Uh... why would you say that?
That's what I do. I usually have WIP commits when working on something new or just want to save my progress.Work in progress.
Also fuck around with all the throwaway commits you want. Just squash them into one logical unit before spamming them to the world at large.