|
spitfire -> RE: IE forms and whatever:hover (4/6/2006 12:57:29)
|
quote:
ORIGINAL: Tailslide It just seems too easy - I want to know if anyone's found an issue with using csshover.htc for this purpose. Err... in some trepidation, slap me down with a diesel-driven deck-cloth it you will, 'cos I've already been told my tabbing skills are deficient today and I've never used whatever:hover to my eternal shame [&:] But are the two input fields meant to show a pale blue background in both IE and Fx - form 2 (and form 1 in Fx), on hover and focus in the same way the textarea does? input:focus, select:focus, textarea:focus {background:#f4f4f4;}
input:hover, select:hover, textarea:hover {background:#f4f4f4;} They do not change for me. Opera, on the other hand, shows pale blue on all three fields on hover and tab (for non-links). Is there anything of import in these little notes insofar as they relate to IE, but, apparently, not to Fx? From peterned quote:
NOTE 1: The rules for HTCs have changed a bit in Windows XP SP2. Users with SP2 installed may not see it working correctly, because webservers have to send htc files with the mime-type set to text/x-component. For more info on this, check Aldo's blog. then... a bit of a ramble quote:
NOTE 3: Version 2.0 also supports the :focus pseudo class for A, INPUT and TEXTAREA elements. However, because a selector like "input:focus" is returned as "input:unknown" by IE's stylesheet object, the script has to attach focus and blur events based on these unknowns, which might as well be other unrecognized pseudo classes. Hence, when using the 2.0 version, you CAN NOT use pseudo classes that are not recognized by IE on A, INPUT or TEXTAREA elements, since they would be used as focus styles. If you need these classes anyway, use 1.4. Got me beat [X(]
|
|
|
|