Sorry if I was confusing... You'd only have one body tag, but the class
might change while the page is loaded... and it might be initialized to
something.
You might have CSS like:
-
div.first, div.second, div.third {display: none}
body.start div.first,
body.next div.second,
body.last
On Jul 2, 2018, at 9:38 PM, David Mason wrote:
>
> It's pretty common to put classes on tags, to use CSS to conditionally
> choose different renderings by simply changing the class of the body tag.
I think you’d have to write TH1 code to get Fossil to serve more than one
tag on a given
It's pretty common to put classes on tags, to use CSS to
conditionally choose different renderings by simply changing the class of
the body tag.
../Dave
On 3 July 2018 at 00:23, mario wrote:
> Mon, 2 Jul 2018 17:20:17 -0600 Warren Young :
>
> > Under what conditions would you have two
Mon, 2 Jul 2018 17:20:17 -0600 Warren Young :
> Under what conditions would you have two different tags in a
> single document differing only by class, and thus need a CSS selector
> to differentiate them?
Of course you wouldn't want two tags.
But that's exactly the bug I ran into:
On Jul 2, 2018, at 8:11 AM, mario wrote:
>
> This misses anything but plain tags in the header
> ↓
> if( sqlite3_strlike("%%", zHeader, 0)!=0 ){
>Th_Render(zDfltHeader);
> }
>
> It might rather be %%, so any style attributes
> like get recognized still.
This misses anything but plain tags in the header
↓
if( sqlite3_strlike("%%", zHeader, 0)!=0 ){
Th_Render(zDfltHeader);
}
It might rather be %%, so any style attributes
like get recognized still.
Perhaps zDfltHeader[] could even contain a short HTML comment
6 matches
Mail list logo
