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 div.third {display: block}
----------
Then a body like: <body class="start">
And some Javascript that did: document.body.className="next";
Note that https://developer.mozilla.org/en-US/docs/Web/HTML/Element/body
points out that you can only have one body in a valid HTML page.
../Dave
On 3 July 2018 at 11:50, Warren Young <war...@etr-usa.com> wrote:
> On Jul 2, 2018, at 9:38 PM, David Mason <dma...@ryerson.ca> wrote:
> >
> > It's pretty common to put classes on <body> 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
> <body> tag on a given repository.
>
> That then makes me wonder if that would be another way to trick Fossil
> into serving a second <body> tag. Consider this pseudocode:
>
> <th1>
> return [concat "<body" [somefn $args] ">"]
> </th1>
>
> I say “pseudocode” because it’s probably horrid Tcl style, if it compiles
> at all. I speak only pidgin Tcl these days.
> _______________________________________________
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
