Laurent Laville wrote:
I've runs all my tests on these browsers :
IE 6(SP2), Mozilla 1.7.3, Firefox 1.0.4, Opera 7.54
If someone has still a problem with his browser, please tell me !
Michael Wallner wrote:
Just a side note: you should lowercase all JS event attributes
for XHTML compliance.
It's ok now, thanks Michael :)
Bertrand Mansion wrote:
On Safari, seems to work ok except in dual select mode where style attributes
(and disabled elements) seem to not be taken into account. There might be a
similar problem in Konqueror, although I haven't tested.
On IE5 mac, in single select mode, an horizontal scrollbar appears making it
difficult if not impossible to use the element. There are also some problems
difficult to describe that break the layout when in dual select mode.
On Camino, it works fine except the selects are slow to update but this is
definately a browser issue that will surely be fixed in a next version as Camino
shares Firefox rendering engine but with customized (and better looking)
widgets.
Bertrand
Thanks Bertrand to run tests on others platform.
Even after fixed JS event attributes and form name attribute to make it
XHTML compliant, i've still a problem and i don't know (until now) how
to solve it.
Perharps someone could have the solution !
The problem is with dual select boxes :
When selected list is empty (most case) when you begin ,
html code generated is something like
<select name="fruit[]"></select>
Notice there are not yet any options; and this case must not be validate
to do a page XHTML compliant
Before to publish a package to PEAR, i would like to solve this; but is
it possible ??
Laurent