From 1335c31e852ed89637b529c8d4f6f7b9a0a19dae Mon Sep 17 00:00:00 2001
From: "luke.schierer@502bb1c5e3da2bf0a6a8c76f17674b51d178247b"
 <lukeschierer@web>
Date: Mon, 14 Sep 2020 15:34:58 -0400
Subject: [PATCH]

---
 ...9__s_pubdate_wrong_when_using_xhtml5___34__mode__34__.mdwn | 4 ++++
 1 file changed, 4 insertions(+)

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 def5bcc2a..16be643cf 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
@@ -9,6 +9,10 @@ The pubdate REQUIRES a date, so e.g. `pubdate="2009-03-24T18:02:14Z"`
 > No, `pubdate="pubdate"`. It's a boolean attribute. applied && [[done]]
 > --[[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 <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/
+ 
 
 Otherwise the XML parser chokes.
 
-- 
2.39.2