W3C home > Mailing lists > Public > www-amaya@w3.org > April to June 2001

INPUT's in Amaya 4.3.2

From: David A. Cobb <superbiskit@home.com>
Date: Sat, 26 May 2001 20:57:30 -0400 (EDT)
Message-Id: <>
To: www-amaya@w3.org
Eager to try out the Annotea, I fired up my new Amaya and cruised over to 

Not a happy experience.  I noted in passing that the "menu buttons" at the 
top of the
entry page have ugly separations between them using Amaya that aren't there 
Mozilla (0.9).  Also, the first clue that <input .. > was going to be a 
problem was the rather strange look about the SEARCH on that page.  Moz. 
renders it as a small input with the button to the right; Amaya renders a 
big input space with the search button kind of awkwardly at the lower left 
of the input.

That wasn't enough warning, so I went to register with the database.
The problem was so much more severe there that I was totally unable to 
complete the form successfully.  I gave up and came back to it with Moz. to 
finish the job.
Then I went in with Amaya and left an annotation on the database input page 
to the effect of what I'm writing here.

Annotations are cool, indeed.
But form layout has been around a long time now.  Is there something that 
makes it difficult to do right?

But I didn't just post to grinch about Amaya!  This reminded me of a real 
need -- a whole forest of pages, preferably under w3 control containing 
very carefully crafted, canonically correct HTML of whatever version where 
we know precisely how it is intended to be rendered; say one page for each 
characteristic to be exercised.  Thus, voila! a way to compare browsers 
where the page content isn't also a variable.


David A. Cobb, Software Engineer, Public Access Advocate, All around nice guy.
Get my PGP key at
"By God's Grace I am a Christian man, by my actions a great sinner."
--The Way of a Pilgrim, R. M. French [tr.]
Received on Wednesday, 30 May 2001 05:50:20 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:53:23 UTC