bug-texinfo
[Top][All Lists]
Advanced

[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: Wed, 2 Jan 2019 11:08:12 -0800
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.3.1

On 1/2/19 10:57 AM, Gavin Smith wrote:
On Mon, Dec 31, 2018 at 01:14:28PM -0800, Per Bothner wrote:
It wraps all nodes (anything processed by _convert_heading_command) in a <div> 
block.

-  $result .= "<a name=\"$element_id\"></a>\n"
+  $result .= "<div cmdname=\"$cmdname\"";


What is the thinking behind the 'cmdname' attribute?  I could find no
reference to this attribute on the web, e.g. nothing at

It may be helpful for styling, to see which div corresponds to what 
section/node,
but using "class" would probably be better. The only issue with class is if
there maybe some conflict with other uses of the same class name for <div>:
It would be undesirable to have <div class='section'> to
mark two different kinds of division, but there is no conflict between
<div class='section'> and <h2 class='section'> since css can trivially
distinguish them.   I'm guessing there is no problem, but I thought I'd mention 
it.

Note, in case you didn't know it: It is perfectly OK to have a list of two or
more names in a class:
   <div class='chapter node'>

I originally put in the "cmdname" for debugging - to see what is happening.
--
        --Per Bothner
address@hidden   http://per.bothner.com/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]