HTML5 output for feed link tag

thebombsite · 2014-02-10 16:11:19

Now we have a preference option for HTML5 I was thinking that the <txp:feed link /> tag ought to output HTML5 code which would mean no closing slash (/). I think I’m right on that one particularly in the “head” of the page. I know it’s not critical at the moment and won’t crash any site, plus I could just hand-code it, but in the future…

philwareham · 2014-02-10 17:31:45

The self-closing tag is still valid in HTML5 (it’s just optional now) so it might be easier (and maybe slightly better performance-wise) to just leave it as-is.

For code purists though (myself included), you’re quite right.

thebombsite · 2014-02-10 17:36:44

Thanks Phil. Hand coding it is then. ;)

gaekwad · 2014-02-10 18:24:06

Without wishing to be that guy, isn’t the HTML5 spec still at draft stage?

gaekwad · 2014-02-10 18:48:47

Also, welcome back Stuart – you might want to scrub the ProTextThemes link from your footer as it’s no longer working and up for sale at Sedo.

Bloke · 2014-02-10 20:55:05

gaekwad wrote #278766:

Without wishing to be that guy, isn’t the HTML5 spec still at draft stage?

Yeah, last I heard the W3C pencilled it in to become a standard in 2074. There’s some quality thinking to be thunk until then.

trenc · 2014-02-16 11:49:50

gaekwad wrote #278766:

Without wishing to be that guy, isn’t the HTML5 spec still at draft stage?

Yes and no.

Yes. Technically it’s in the so called draft stage.

No. Practically all browsers are supporting the core features (and some subsets) and the markup. So it’s usable.
Because of that it’s often called »living standard«.

Btw.: I myself won’t drop the closing slash. The XML-style of the markup enhances the readability of the code.

Last edited by trenc (2014-02-16 11:50:23)

monkeyninja · 2014-02-16 12:00:23

trenc wrote #278976:

Btw.: I myself won’t drop the closing slash. The XML-style of the markup enhances the readability of the code.

I’m much of the same opinion. It is helpful to see that tags have been closed; it greatly improves the readability of the code. I was disappointed when it was decided that the closing slash would be optional. It sends out mixed messages.

colak · 2014-02-16 12:39:14

+1 for keeping the closing slash.

maverick · 2014-02-17 01:03:34

echoing the previous sentiments on the closing slash.

Last edited by maverick (2014-02-17 01:03:59)

gaekwad · 2014-02-17 10:44:35

Perhaps a workaround to this might be to have an option to output single tags with or without closing tags, and do it with a plugin.

Making a sweeping generalisation, a large chunk of people using Textpattern won’t give a rat’s tuckus whether there are closing tags or not – but those that do will be able to install a plugin, tick a box, choose from a drop-down, whatever.

Textpattern CMS

Textpattern CMS support forum

#1 2014-02-10 16:11:19