Gossamer Forum
Home : Products : Gossamer Mail : Discussion :

Macintosh problems with GMail

(Page 2 of 2)
> >
Quote Reply
Re: [brewt] Macintosh problems with GMail In reply to
In Reply To:
Bruce only has IE 4.01 on his Mac, so that's all he could test it with. He says that the <input type="image" ...> doesn't show at all, but the regular <input type="submit" ...> worked fine. Does anyone have Mac IE 5? My guess is that Mac IE 5 isn't submitting the name="do= ...." properly, so Gossamer Mail doesn't know what to do with the submitted form.


Download Netscape for the mac and test it on that - then it'll work on IE as well - guaranteed.

http://www.versiontracker.com/...etscape+communicator

Yes, I've had problems before trying to use an image as a submit button on a mac - but that was with a php script. If you want I can test it on Netscape and IE.

r

Last edited by:

ryel01: May 7, 2002, 2:04 PM
Quote Reply
Re: [brewt] Macintosh problems with GMail In reply to
We had the same problem here, with a lot of our users using IE 5.x on OS X.

I found the problem with the templates. The issue is that IE on the Mac is unable to handle <input type="image"... tags properly.

It dies when you try to do more than one or two in a group.

The current work arround (that we're using now) is to change them into normal buttons; definitely not as pretty, but simple. I suppose another option would be to rewrite the page to use <img> and <a> tags to get the same behaviour - and retain the pretty graphics - although it would be trickier as it would require some additional coding.

Has this been fixed in the unrelease 2.1?

Unsure
Quote Reply
Re: [zoherest] Macintosh problems with GMail In reply to
In Reply To:
We had the same problem here, with a lot of our users using IE 5.x on OS X.

I found the problem with the templates. The issue is that IE on the Mac is unable to handle <input type="image"... tags properly.

It dies when you try to do more than one or two in a group.

The current work arround (that we're using now) is to change them into normal buttons; definitely not as pretty, but simple. I suppose another option would be to rewrite the page to use <img> and <a> tags to get the same behaviour - and retain the pretty graphics - although it would be trickier as it would require some additional coding.

Has this been fixed in the unrelease 2.1?

Unsure



there's a new release due out shortly (i'm long overdue for an upgrade) so will be testing it to death before i go live with it. it'll be a simple template issue so no major hassle if it's still there.

cheers,
regan.
> >