From: Matt Gushee <mgushee@havenrock.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] developing apps with ocaml exercices web pages
Date: Sat, 29 Jan 2005 16:34:04 -0700 [thread overview]
Message-ID: <41FC1D6C.8000705@havenrock.com> (raw)
In-Reply-To: <41FC0FBC.1090101@rftp.com>
Robert Roessler wrote:
>> The web pages with exercises in "Developing applications with OCaml"
>> are unreadable with mozilla/firefox (i guess that the "layer"
>> attribute "visibility" is ignored). Maybe there is a quick fix? I'd
>> rather have the solutions always visible (i.e. remove all related
>> javascript).
>
> Actually, according to the W3C markup and CSS validators, the Exercise
> pages (and stylesheets) are... compliance-challenged. :)
>
> And it isn't all about the "layer" element,
I don't doubt you're right. Nonetheless, I did get the pages to display
fine in Gecko-based browsers by simply removing all the <layer> tags.
--
Matt Gushee
Englewood, CO, USA
next prev parent reply other threads:[~2005-01-29 23:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-29 11:25 Radu Grigore
2005-01-29 22:35 ` [Caml-list] " Robert Roessler
2005-01-29 23:34 ` Matt Gushee [this message]
2005-01-31 8:26 ` Stefano Zacchiroli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41FC1D6C.8000705@havenrock.com \
--to=mgushee@havenrock.com \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox