Page 1 of 1

AMO Link Fail

Posted: Tue Apr 20, 2010 4:31 pm
by dhouwn
  1. Image
  2. Image

Re: AMO Link Fail

Posted: Tue Apr 20, 2010 5:03 pm
by therube
What link? URL?

NoScript is quite out of date, only showing 1.9.9.63 at this point.

NoScript :: Add-ons for SeaMonkey
https://addons.mozilla.org/en-US/seamonkey/addon/722

Not unusual for AMO to be outdated, but running on 5 days now with NoScript.

PS: There was no .67 #dev/release ?

Re: AMO Link Fail

Posted: Tue Apr 20, 2010 11:41 pm
by dhouwn
The image hoster lost his domain, re-uploaded the images.

Re: AMO Link Fail

Posted: Wed Apr 21, 2010 12:15 am
by GµårÐïåñ
I have not had any problem with the AMO link and is usually pretty updated, unless there is a pending dev version floating, in which case the RSS for that keeps me posted. I know that sometimes AMO links fail saying the download is missing or something, I had been told that's due to the server being picked, usually a restart fixes that. And I don't think you mean the version number is wrong, because that is showing fine right now, and whenever I have had the need to check. Maybe this is some faulty localization issue with Fx/AMO?

Re: AMO Link Fail

Posted: Wed Apr 21, 2010 1:04 am
by dhouwn
The problem is simply that it is an <iframe> and that when I click the link it is opened in the frame.

To sum it up, iframes are baaaaad (or '… considered harmful').

Re: AMO Link Fail

Posted: Wed Apr 21, 2010 5:56 am
by GµårÐïåñ
Unfortunately I can't say I have ever seen iframes on AMO (I hardly need to be on there) but if they are on there, then certainly not good practice given that its one of the blocked "potentially" harmful or bad elements. However, at some point you either trust the site or you don't; although I am certainly sensitive to your concern about potentially bad coding that could create an exploitable situation and/or be hijacked or intercepted or whatever method of your choice; but simply said, the simple presence of an iframe doesn't make it evil.

Anyway, I have either missed your initial point, or we are talking about something else or perhaps we are all thinking of something different, but I will let Giorgio or others chime in on this from this point. Also, could be something that has to do with the developmental nature of the version of your Fx and its not behaving accordingly or as expected, not sure.

Re: AMO Link Fail

Posted: Wed Apr 21, 2010 7:29 am
by Giorgio Maone
Again, having a Gecko UA would help ;)

Re: AMO Link Fail

Posted: Wed Apr 21, 2010 4:20 pm
by dhouwn
GµårÐïåñ wrote:Unfortunately I can't say I have ever seen iframes on AMO (I hardly need to be on there)
It's on the NoScript site: http://noscript.net/getit

Re: AMO Link Fail

Posted: Wed Apr 21, 2010 8:42 pm
by GµårÐïåñ
dhouwn wrote:
GµårÐïåñ wrote:Unfortunately I can't say I have ever seen iframes on AMO (I hardly need to be on there)
It's on the NoScript site: http://noscript.net/getit
Ok, you are talking about NoScript.net, since I trust Giorgio and have the site whitelisted, its not an issue for me; plus I am pretty sure its part of the ajax coding, I could be wrong. As he has already said, it seems that having the proper element in the UA fixes it, so let us know if that works for you. As for the use of iframes and why, I again will defer to Giorgio, if he's using it, I am sure it has a purpose and again simple use of a certified html element, doesn't make it evil, its how its coded and used that could create problems.

Re: AMO Link Fail

Posted: Wed Apr 21, 2010 8:56 pm
by Giorgio Maone
GµårÐïåñ wrote:
dhouwn wrote:
GµårÐïåñ wrote:Unfortunately I can't say I have ever seen iframes on AMO (I hardly need to be on there)
It's on the NoScript site: http://noscript.net/getit
Ok, you are talking about NoScript.net, since I trust Giorgio and have the site whitelisted, its not an issue for me;
It's the famous "Benign Clickjacking" I talked about here.

Re: AMO Link Fail

Posted: Thu Apr 22, 2010 6:47 am
by GµårÐïåñ
Giorgio Maone wrote:It's the famous "Benign Clickjacking" I talked about here.
Yes that's the one, thank you for the link again.