Re: [PATCH 1/3] gitweb: Fix an ancient typo in v1.7.7-rc1-1-g0866786
- From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
- Date
- Sep 21, 2016, 17:17 UTC
- Message-ID
- <CACBZZX73N4A0WBOG0G6DUg2fbn0mCmfuApcC6gG=6b-6-UrW7Q@mail.gmail.com>
- In-Reply-To
- <8b43ba22-9634-e2b8-8de7-d70c258f4034@gmail.com>
On Wed, Sep 21, 2016 at 7:14 PM, Jakub Narębski <jnareb@gmail.com> wrote:
Show 17 quoted lines
> W dniu 21.09.2016 o 16:17, Ævar Arnfjörð Bjarmason napisał: >> On Wed, Sep 21, 2016 at 3:33 PM, Jakub Narębski <jnareb@gmail.com> wrote: >>> W dniu 21.09.2016 o 13:44, Ævar Arnfjörð Bjarmason napisał: > [...] > >>>> -# Sanitize for use in XHTML + application/xml+xhtm (valid XML 1.0) >>>> +# Sanitize for use in XHTML + application/xml+xhtml (valid XML 1.0) >>> >>> Nb. I wonder how common is use of XHTML nowadays, with HTML5 as standard... >> >> It's sent to modern browsers, I noticed it because when doing the rest >> of the patches in the series the slightest mistake in the HTML syntax >> would cause the page not to render in Chrome, because >> application/xml+xhtml activates its anal parsing mode. > > What I wanted to say is if we should support XHTML mimetype at all; > the future is HTML5 and perhaps gitweb should always use 'text/html'.
Regardless of what MIME type we'd normally use, as long as browsers support application/xml+xhtml developing with it is very handy, because you get the instant equivalent of compile errors for your HTML, as opposed to the usual behavior of "oh this doesn't parse, but let's try to make sense of it anyway", which often leads to fruitless debugging sessions just because you forgot to close some tag or quotation.