Re: [WSG] ainput//a - how wrong?
Barney Carroll wrote:
...snip...
Update:
Couldn't get csshover.htc to work - dumped it in with my stylesheets
and called it via body{behavior:url(stylesheets/csshover.htc)} but it
wouldn't have any effect... May turn out to be a stupid oversight...
...snip...
Regards,
Barney
Hi Barney,
I knew there was something not quite straightforward about the htc,
forgot to add this link. It may be to do with your hosting provider, if
you can get in touch and confirm the mimetype they deliver htcs with is
set to text/x-component it should work. If thats not the issue send us a
link or test page.
http://support.microsoft.com/kb/306231
Rob
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
[WSG] ainput//a - how wrong?
Styled buttons are a bucketful of issues. Normally it's practice to
complain about the current release of WebKit, but I've just bumped into
the issue of :hover and all those other pseudo-classes IE believes
should be reserved for as exclusively.
My client complains that my heavily styled buttons do not obey the
modern convention of highlighting when mouseovered (which they do in FF,
but of course my hover properties are ignored by IE) - hence being
ambiguous in their interactivity. They're entirely right, but do I have
to strip my buttons of their styling to be able to achieve this?
Moreover, just how evil would it be for me to simply wrap the buttons in
as, and giving the CSS [a:hover input.button{cursor:pointer}]?
Regards,
Barney
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
Re: [WSG] ainput//a - how wrong?
On Tue, Jan 09, 2007 at 01:15:14PM +, Barney Carroll wrote:
Styled buttons are a bucketful of issues. Normally it's practice to
complain about the current release of WebKit, but I've just bumped into
the issue of :hover and all those other pseudo-classes IE believes
should be reserved for as exclusively.
Isn't that fixed in IE 7?
My client complains that my heavily styled buttons do not obey the
modern convention of highlighting when mouseovered (which they do in FF,
but of course my hover properties are ignored by IE) - hence being
ambiguous in their interactivity. They're entirely right, but do I have
to strip my buttons of their styling to be able to achieve this?
Moreover, just how evil would it be for me to simply wrap the buttons in
as
I wouldn't like to gamble on browser interpretation of wrapping
buttons with links (and IE6 supports :hover only on links, not just
any anchor).
I'd attach an event handler (with JavaScript) that toggles a class
onmouseover and removes it onmouseout. The JQuery library makes this
very easy.
and giving the CSS [a:hover input.button{cursor:pointer}]?
If its just the cursor property you are playing with, then don't worry
about :hover. It describes the mouse pointer only when over that
element anyway.
--
David Dorward http://dorward.me.uk
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
Re: [WSG] ainput//a - how wrong?
On 1/9/07, Barney Carroll [EMAIL PROTECTED] wrote:
Moreover, just how evil would it be for me to simply wrap the buttons in
as, and giving the CSS [a:hover input.button{cursor:pointer}]?
Or, you could use JavaScript to apply mouseover/mouseout behaviour to the
buttons to replace the broken :hover.
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
Re: [WSG] ainput//a - how wrong?
Have you tried using button instead? There was a thread about this
just yesterday.
They're much more flexible:
http://kay.zombiecoder.com/index.php/archives/forget-input-typesubmit-use-a-button
On 1/9/07, Barney Carroll [EMAIL PROTECTED] wrote:
Styled buttons are a bucketful of issues. Normally it's practice to
complain about the current release of WebKit, but I've just bumped into
the issue of :hover and all those other pseudo-classes IE believes
should be reserved for as exclusively.
My client complains that my heavily styled buttons do not obey the
modern convention of highlighting when mouseovered (which they do in FF,
but of course my hover properties are ignored by IE) - hence being
ambiguous in their interactivity. They're entirely right, but do I have
to strip my buttons of their styling to be able to achieve this?
Moreover, just how evil would it be for me to simply wrap the buttons in
as, and giving the CSS [a:hover input.button{cursor:pointer}]?
Regards,
Barney
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
--
Kay Smoljak
business: www.cleverstarfish.com
standards: kay.zombiecoder.com
coldfusion: kay.smoljak.com
personal: goatlady.wordpress.com
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
Re: [WSG] ainput//a - how wrong?
couple of points input:hover for type =submit (and others if my memory serves me) is pretty useless for Safari and limited for Camino, because you can only change a few properties on input. background-color, color and background-image are not affected by style (all to do with the form widgets built into Safari and Camino). You can use the button element instead of the input element if you want more control in these browsers. Why you use hover.htc instead of custom javascript for hover effects. 1 it saves you time 2 if you use in a number of places in your site, it saves users time, it only needs to be downloaded once 3 good browsers do not download it 4 if a good browser has js turned off effect still works 5 in really bad browsers (some versions of NS4) js can crash the browser, but these browsers ignore .htc files 6 of course .htc files do not work if js is turned off, they are js files for ie only. If you turn of js all javascript, .htc .js and inline stops working. 7 I have never had problems with hover.htc and IE5, 5.5 and 6 on windows. -- Nick Cowie http://nickcowie.com *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
