From 692147048648b2a5119434b8fbfb8822dfe301b8 Mon Sep 17 00:00:00 2001 From: "luke.schierer@502bb1c5e3da2bf0a6a8c76f17674b51d178247b" Date: Mon, 14 Sep 2020 15:37:19 -0400 Subject: [PATCH] --- ..._s_pubdate_wrong_when_using_xhtml5___34__mode__34__.mdwn | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/doc/bugs/html5_time_element__39__s_pubdate_wrong_when_using_xhtml5___34__mode__34__.mdwn b/doc/bugs/html5_time_element__39__s_pubdate_wrong_when_using_xhtml5___34__mode__34__.mdwn index 16be643cf..228847b4a 100644 --- a/doc/bugs/html5_time_element__39__s_pubdate_wrong_when_using_xhtml5___34__mode__34__.mdwn +++ b/doc/bugs/html5_time_element__39__s_pubdate_wrong_when_using_xhtml5___34__mode__34__.mdwn @@ -10,8 +10,10 @@ The pubdate REQUIRES a date, so e.g. `pubdate="2009-03-24T18:02:14Z"` > --[[Joey]] >> awesome, thanks for fixing my fix ;) --[[simonraven]] >>> This seems to be happening either still or again with version 3.20200202.3-1. I'm getting strings generated like ->>> Posted ->>> which shows up as an error on https://validator.w3.org/ +>>> +>>> Posted <time datetime="2007-12-06T05:00:00Z" pubdate="pubdate">Thu 06 Dec 2007 12:00:00 AM EST</time> +>>> +>>> which shows up as an error on https://validator.w3.org/ --Luke Schierer Otherwise the XML parser chokes. -- 2.39.5