- From: Charles McCathieNevile <charles@w3.org>
- Date: Mon, 25 Feb 2002 12:17:53 -0500 (EST)
- To: "Rzepa, Henry" <h.rzepa@ic.ac.uk>
- cc: <www-amaya@w3.org>
Well, the code looks fine to me, and Amaya should display the internal text... Chaals On Mon, 25 Feb 2002, Rzepa, Henry wrote: Some two years ago we wrote a simple page to test <object> handling. We were anticipating generating XHTML display code from XSLT transform of XML content, and wanted to make the result as robust as possible. http://www.ch.ic.ac.uk/chemime/tests/object/browsers/scheme2.html was tested against the then range of browsers, with pretty disappointing results. Only one browser (iCab) passed the tests. Revisiting this test some 20 months on, I found things certainly improving. Thus Netscape 6 is pretty good, and now matches iCab. Assuming however that Amaya is the gold standard, I expected the result http://www.ch.ic.ac.uk/chemime/tests/object/browsers/mozilla_x.jpg (actually from Mozilla on MacOS X, for which neither plugins nor Java are currently enabled; a situation which I presumed matches Amaya precisely). In fact, the latest Amaya does not perform as I had expected (try for yourselves)., attempting to display the plugin and Java, even though it cannot do either. Can anyone comment on whether in fact our code is wrong, whether there is a genuine bug in Amaya, or whether the interpretation is ambiguous? -- Charles McCathieNevile http://www.w3.org/People/Charles phone: +61 409 134 136 W3C Web Accessibility Initiative http://www.w3.org/WAI fax: +1 617 258 5999 Location: 21 Mitchell street FOOTSCRAY Vic 3011, Australia (or W3C INRIA, Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France)
Received on Monday, 25 February 2002 12:17:54 UTC