by therube » Mon Apr 06, 2009 2:54 pm
That's a very good question.
Perhaps that is normal for you (& others) in Sweden?
Here is another "secure.footprint.net" URL,
https://login.live.com/login.srf?id=2&vv=650&lc=1033 .
With that one, in SeaMonkey 1, I get the IFRAMES & the login box.
In SeaMonkey 2, I get the same - initially, & then it rolls over to
JavaScript required to sign in, yet JavaScript is enabled for
live.com?
Alright, just confused myself.
SM1 live.com had been allowed. And I received the login dialog.
If I Forbid, then I get the JavaScript page.
SM2 with live.com allowed, I get the redirect to the JavaScript page.
SM2 with live.com Forbidden, I get the login dialog along with an (NoScript) redirection arrow - which if clicked would take me to the redirected JavaScript page.
Why the difference between the two (SeaMonkey's)?
[quote]https://secure.footprint.net/?[/quote]
That's a very good question.
Perhaps that is normal for you (& others) in Sweden?
Here is another "secure.footprint.net" URL, https://login.live.com/login.srf?id=2&vv=650&lc=1033 .
With that one, in SeaMonkey 1, I get the IFRAMES & the login box.
In SeaMonkey 2, I get the same - initially, & then it rolls over to [url=https://login.live.com/jsDisabled.srf?lc=1033]JavaScript required to sign in[/url], yet JavaScript is enabled for [b]live.com[/b]?
Alright, just confused myself.
SM1 live.com had been allowed. And I received the login dialog.
If I Forbid, then I get the JavaScript page.
SM2 with live.com allowed, I get the redirect to the JavaScript page.
SM2 with live.com Forbidden, I get the login dialog along with an (NoScript) redirection arrow - which if clicked would take me to the redirected JavaScript page.
Why the difference between the two (SeaMonkey's)?