CameraGassed?

[smiler]

OK I give up. I have tried to list an item for sale on Cameragas half a dozen times and the site will not allow me to type in the description window. Have sent two emails without response. Anybody out there had similar problems?

 

[cmedin]

You try a different browser? I use Firefox mainly and on occasion some sites just flat out don't work and I have to use IE...

 

[MP Guy]

If you are using Safari that could be the problem. I have run into several sites including CG where Safari just does not work on all the fields. If it is not an inconvenience, try Firefox. Before you know it, you will never use Safari again.

 

[shadowfox]

Safari sucks, that's one weird program that Apple put out and never enhance. Try to be smart with javascript, it'll work on Firefox just fine, but not on Safari... noooo, it's too exclusive.

 

[climbing_vine]

Javascript works just fine in Safari... in fact, I've only come across one site that did broken and wrong things that didn't work in Safari, compared to dozens that don't work in Firefox (which I used for a year and the only good thing I can say about it is, at least it's not IE).

Not sure why the different experiences... I do know it's nothing to do with Safari being "exclusive", but sites using broken javascript that some browsers may "enable" by trying to guess at what it's supposed to do. Or just letting it run as it may even if it's incorrect, which is a huge security and usability hole.

I was trying to test it to let you (and the site designers) know what the actual problem is, but it's taking god knows how long for their registration confirmation email to get through, so.... first impression, not so hot.

 

[shadowfox]

Ok, here's an easy example, try to use the for...in statement in Safari. Not so well, eh?

Why won't safari support a w3c standard *statement* (not a volatile API, but statement)? I would call that being exclusive, wouldn't you?

There is plenty of time and opportunity for Apple to fix the bug. But they can't/wouldn't/won't/whatever.

There are other problems that prevented me to write a generic javascript across browsers especially when I use AJAX libraries. And I tried my best not to write "broken" javascript code.

I have nothing against Safari other than it makes my job harder than it needs to be. Sure javascript works on Safari, most of the time, I did mention "try to be smart" 🙂.

Javascript works just fine in Safari... in fact, I've only come across one site that did broken and wrong things that didn't work in Safari, compared to dozens that don't work in Firefox (which I used for a year and the only good thing I can say about it is, at least it's not IE).

Not sure why the different experiences... I do know it's nothing to do with Safari being "exclusive", but sites using broken javascript that some browsers may "enable" by trying to guess at what it's supposed to do. Or just letting it run as it may even if it's incorrect, which is a huge security and usability hole.

I was trying to test it to let you (and the site designers) know what the actual problem is, but it's taking god knows how long for their registration confirmation email to get through, so.... first impression, not so hot.

 

[climbing_vine]

Ok, here's an easy example, try to use the for...in statement in Safari. Not so well, eh?

Why won't safari support a w3c standard *statement* (not a volatile API, but statement)? I would call that being exclusive, wouldn't you?

Well, it does support it, but it had a bug in that it "doubled" the results (there's lots of reading about this one on Google, and frankly, it seems as if Safari was the one doing right thing, strictly speaking, according to the ECMA spec--there's debate on this, but by the letter of the law it looks right to me).

There is plenty of time and opportunity for Apple to fix the bug. But they can't/wouldn't/won't/whatever.

It's fixed in the Safari 3 Beta, though of course I understand that leaves lots of people unaccounted for, for the moment. 🙂

I have nothing against Safari other than it makes my job harder than it needs to be. Sure javascript works on Safari, most of the time, I did mention "try to be smart" 🙂.

Heh. Fair enough. I haven't done a whole lot of JS work, but I do know that for HTML and CSS Safari works exactly as it should nearly 100% of the time, whereas Mozilla/Firefox are nearly as obviously stupid in CSS interpretation as IE. I guess everyone has their cross to bear, heh!

 

[somecanuckchick]

You try a different browser? I use Firefox mainly and on occasion some sites just flat out don't work and I have to use IE...

Wow. So much for w3 standards, cross-platform development and browser workarounds...

:bang::bang::bang::bang::bang: