Re: Interframe communication
- From: Thomas 'PointedEars' Lahn <PointedEars@xxxxxx>
- Date: Sat, 01 Dec 2007 11:43:11 +0100
Randy Webb wrote:
Thomas 'PointedEars' Lahn said the following on 12/1/2007 5:24 AM:
Randy Webb wrote:
Thomas 'PointedEars' Lahn said the following on 11/30/2007 11:47 AM:You are missing the fact that these are graphical links.
Wael wrote:Yeah, we all know how well supported :hover is on images in the most
and to make the page look a lively a bit, i was going to have an iconYou don't need frames for that. Probably you don't even need client-side
displayed in the frame that i cannot access.
scripting; :hover could suffice.
http://www.w3.org/TR/CSS21/
predominant browser on the web. Makes it pretty useless.
Has nothing to do with whether it is a "graphical link" or not. Telling
someone to use something that is not supports in the most predominant
browser on the web is a wasted effort. It is almost as bad as telling
someone to use an IE-only feature.
IE supports the :hover pseudo-class for `a' elements, too.
PointedEars
--
var bugRiddenCrashPronePieceOfJunk = (
navigator.userAgent.indexOf('MSIE 5') != -1
&& navigator.userAgent.indexOf('Mac') != -1
) // Plone, register_function.js:16
.
- Follow-Ups:
- Re: Interframe communication
- From: Randy Webb
- Re: Interframe communication
- References:
- Re: Interframe communication
- From: Randy Webb
- Re: Interframe communication
- From: Thomas 'PointedEars' Lahn
- Re: Interframe communication
- From: Randy Webb
- Re: Interframe communication
- Prev by Date: Re: odd problem about innerHTML & img under IE
- Next by Date: Re: Img on error works in safari but not firefox,(leopard) what can I do to fix that.
- Previous by thread: Re: Interframe communication
- Next by thread: Re: Interframe communication
- Index(es):
Relevant Pages
|