not really...
being vision impaired is not a fault
viewing your site on mobile device which don't understand css or js is
not a fault
you are just loosing your potential visitors, anyway, its up to you
anyway...
what i concern is we are doing web development, not game developement,
don't use s
Honestly when i develop, im not really worried about browsers that dont
understand css or javascript. If they chose to use an incredibly outdated
browser, thats their fault.
On 6/23/07, howa <[EMAIL PROTECTED]> wrote:
On 6月23日, 上午2時17分, "Glen Lipka" <[EMAIL PROTECTED]> wrote:
> I am not sure
On 6月23日, 上午2時17分, "Glen Lipka" <[EMAIL PROTECTED]> wrote:
> I am not sure how it diminishes accessibility.
What if your browser don't understand css and js?
for jquery's solution, it is fine, you can still see the original
image, but only drop the hover effect
for css solutions, you might drop
As much as using 1 image and shifting the background seems, as you
would say, `hacky`, as far as w3 is concerned it would rather have
you use that way.
1. Less Images - Less Images = Less HTTP calls = Better
2. Less Code - Less Code = Faster call... yes i know its not very much
difference, but i
I use sprites all the time. It reduces the overall filesize and number of
http calls.
Plus it's easier to manage.
This really has become standard practice around the web.
I am not sure how it diminishes accessibility. Most hover effects are used
to highlight or accentuate and are usually not co
I completely agree CSS can do the job
but IMHO, css's ways are even more `hacky`
i.e. use of single image and simply shift the background
think abt it, this is accessibility evil!
On 6月22日, 下午1時16分, "Ambient.Impact" <[EMAIL PROTECTED]> wrote:
> I very much disagree with the following two poin
On Jun 22, 2007, at 5:51 AM, howard chen wrote:
As discussed previously in the group, I make a very simple plugin to
rollover an image..
Something similar here:
http://www.appelsiini.net/~tuupola/823/sequentially-preloading-images
--
Mika Tuupola http://www.appelsiini.
I very much disagree with the following two points:
On Jun 21, 10:51 pm, "howard chen" <[EMAIL PROTECTED]> wrote:
> 2. Put rollover stuffs into CSS is no good: CSS for layout & design,
> JS for effect
> 1. CSS can't preload image, the plugin can
2. This is a subject that's certainly debatable, s
tks for the tip about the preload ;D
On 6/21/07, howard chen <[EMAIL PROTECTED]> wrote:
As discussed previously in the group, I make a very simple plugin to
rollover an image..
Codes:
jQuery.fn.swapimage = function() {
$(this).hover(function() {
currentImage = $(this).attr('src');
9 matches
Mail list logo
