Jonathan Turkanis wrote:
There was a discussion a couple weeks ago about the javascript menu in Robert Ramey's serialization docs. I suggested making a
"Martin Wille" <mw8329@yahoo.com.au> wrote in message news:410764D9.6010105@yahoo.com.au... menu
component available Boost-wide and testing it on a large number of browsers to address portability issues. I've written a preliminary version, documented here: ... I've verified that it works -- with varying levels of functionality -- on 26 browsersincluding some antiques such as IE3.02.
Didn't we agree on a non-JavaScript policy not too long ago?
Yes.
FWIW, the Tree Control doesn't work with links2
I should have put this in the documentation: The control should (I hope) work on any browser if one of the three following conditions is satisfied: 1. It supports no javascript at all (and understands the 'noscript' element) 2. It is reasonably conformant with the W3C DOM (level of required conformance currently unspecified) 3. It is a old version of IE, Netscape or Opera. In cases (1) and (3), the control displays in a fully expanded state. My idea was to presume that untested browsers satisfy (2), thereby allowing the control to function optimally on as many browsers as possible, and to add browsers to (3) as needed.
(The tree isn't visible. Instead, there is a link labeled "sync"; clicking it doesn't produce any result)
Thanks. I'll check it out. [sync] won't do anything unless the tree is displayed. Jonathan