[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: modernizing html output
From: |
Per Bothner |
Subject: |
Re: modernizing html output |
Date: |
Tue, 1 Jan 2019 17:46:11 -0800 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.3.1 |
On 1/1/19 1:49 PM, Gavin Smith wrote:
Thanks for working on this. What else needs to be changed so that the
output is valid for HTML 5?
It's worth clarifying that all of the changes in my patch produce valid HTML 4:
Using 'id' attributes on arbitrary elements is part of HTML 4, and I believe
it has been supported by all non-toy browsers for 20 years.
So the only reason for not unconditionally changing things according to my patch
is if we are concerned about third-party css stylesheets or JavaScript (such as
texinfo-js) depending on the "old" html output and hence breaking if we make
these changes unconditionally. I also suggest we should make these changes
at least the default (and possibly unconditionally) in a future texinfo release.
When if comes to texinfo-js, I would prefer to modify it so it works with
(and depends on) the "html5" output - I think that would make the texinfo-js
code simpler and cleaner.
I'll let you judge which is more important: the risk of breaking third-party
css/js vs the extra maintainance and documentation burden of a switch.
--
--Per Bothner
address@hidden http://per.bothner.com/
- Re: modernizing html output, Gavin Smith, 2019/01/01
- Re: modernizing html output, Per Bothner, 2019/01/01
- Re: modernizing html output, Per Bothner, 2019/01/01
- Re: modernizing html output,
Per Bothner <=
- Re: modernizing html output, Gavin Smith, 2019/01/02
- Re: modernizing html output, Gavin Smith, 2019/01/02
- Re: modernizing html output, Per Bothner, 2019/01/02
- Re: modernizing html output, Patrice Dumas, 2019/01/03
- Re: modernizing html output, Gavin Smith, 2019/01/03
- Re: modernizing html output, Gavin Smith, 2019/01/03
Re: modernizing html output, Gavin Smith, 2019/01/28