I've noticed this in a few cases.
Aqua has a crappy implementation of
{button}. If you use {input type="button"} you get Aqua, and if you use
{button}
you get some ugly button.
Plus, if the stylesheet specifies a style for
the button, such as a background-color or even text styling, the button reverts
to a different button.
I see this all the time, even in Safari, especially
in sites like Gmail that use buttons instead of input type="button". You
guys know what I'm talking about?
Adam
--- Camino List <[email protected]
wrote:
On May 3, 2007, at 1:20 PM, Paul Anderson wrote:
>
> > I've seen
this behavior for a while and wonder why it happens.
> >
> > At some sites,
Camino displays generic buttons.
>
> Depending on what you mean by "generic",
the specific answers are
> slightly different, but the short version is
that most form elements
> are always forced to look Aqua, and one specific
type of button that
> often has issues that way never looks Aqua, and will
follow the page
> styling (or just look like a grey, square button if there
is no page
> styling on it). In Camino 2.0 we'll benefit from work being
done in
> the Mozilla core that will make more buttons that have no styling
> look Aqua, and more buttons that do have styling look the way the
> page author probably intended, much like Camino handles input fields
> today.
>
> -Stuart
> _______________________________________________
> Camino mailing list
> [email protected]
> http://mozdev.org/mailman/listinfo/camino
>
_______________________________________________
Camino mailing list
[email protected]
http://mozdev.org/mailman/listinfo/camino
