Page Navigation Bug with SM 1.0.x and 1.1.x? Working with Firefox 2, Konquerer 3.5 and IE6

Hi all, I seem to having been hit a bug in SeaMonkey which exhibit 
itself when visiting the following Knowledgebase web page at ZyXEL:

http://www.zyxel.com/web/support_knowledgebase_list.php?pid=20070115144001

If you visit that page, or any other of their Knowledgebase pages, you 
will be presented with a list of articles. Whenever the list is longer 
as to fit in one page, you are given navigation controls that allow you 
to proceed to to the next # of items e.g. by selecting 2, 3, Next or 
Last. Unfortunately these navigation controls don't seem to work when 
visiting these pages with SeaMonkey 1.0.x or SeaMonkey 1.1 - at least 
not for me :-(

I'm seeing this problem with SeaMonkey 1.0.7 on Windows/NT, and I have 
had someone else verify the problem for SeaMonkey 1.1, running on Linux.

The same page(s) seem to work fine when they are visited with Firefox 2, 
Konquerer 3.5 and IE6. The former two on Linux and the latter Windows.

To confirm this issue further, may I ask some of You to please visit 
that page with some of the browsers that You have at hand and report 
back Your experiences with it.

Please remember to specify browser and platform/OS too.

It's really annoying not being able to access those articles with SM.

Thank You All for Your kind assistance.

0
Rolf
2/15/2007 4:06:27 PM
mozilla.support.seamonkey 13721 articles. 0 followers. Post Follow

20 Replies
1298 Views

Similar Articles

[PageSpeed] 44
Get it on Google Play
Get it on Apple App Store

Rolf wrote:
> Hi all, I seem to having been hit a bug in SeaMonkey which exhibit 
> itself when visiting the following Knowledgebase web page at ZyXEL:
> 
> http://www.zyxel.com/web/support_knowledgebase_list.php?pid=20070115144001
> 
> If you visit that page, or any other of their Knowledgebase pages, you 
> will be presented with a list of articles. Whenever the list is longer 
> as to fit in one page, you are given navigation controls that allow you 
> to proceed to to the next # of items e.g. by selecting 2, 3, Next or 
> Last. Unfortunately these navigation controls don't seem to work when 
> visiting these pages with SeaMonkey 1.0.x or SeaMonkey 1.1 - at least 
> not for me :-(
> 
> I'm seeing this problem with SeaMonkey 1.0.7 on Windows/NT, and I have 
> had someone else verify the problem for SeaMonkey 1.1, running on Linux.
> 
> The same page(s) seem to work fine when they are visited with Firefox 2, 
> Konquerer 3.5 and IE6. The former two on Linux and the latter Windows.
> 
> To confirm this issue further, may I ask some of You to please visit 
> that page with some of the browsers that You have at hand and report 
> back Your experiences with it.
> 
> Please remember to specify browser and platform/OS too.
> 
> It's really annoying not being able to access those articles with SM.
> 
> Thank You All for Your kind assistance.
> 


Like you said, for  SM1.1 and Camino 1.1.

Awful pages according to validator.w3.org (235 errors)!


Partly work with Safari 1.3.2 (only the next,last,first and prev. 
buttons are working, not the 1,2,3 page).

Everything on Mac osX3.9

Marco
0
Marco
2/15/2007 5:43:35 PM
Rolf wrote:
> Hi all, I seem to having been hit a bug in SeaMonkey which exhibit 
> itself when visiting the following Knowledgebase web page at ZyXEL:
> 
> http://www.zyxel.com/web/support_knowledgebase_list.php?pid=20070115144001
> 
> If you visit that page, or any other of their Knowledgebase pages, you 
> will be presented with a list of articles. Whenever the list is longer 
> as to fit in one page, you are given navigation controls that allow you 
> to proceed to to the next # of items e.g. by selecting 2, 3, Next or 
> Last. Unfortunately these navigation controls don't seem to work when 
> visiting these pages with SeaMonkey 1.0.x or SeaMonkey 1.1 - at least 
> not for me :-(
> 
> I'm seeing this problem with SeaMonkey 1.0.7 on Windows/NT, and I have 
> had someone else verify the problem for SeaMonkey 1.1, running on Linux.
> 
> The same page(s) seem to work fine when they are visited with Firefox 2, 
> Konquerer 3.5 and IE6. The former two on Linux and the latter Windows.
> 
> To confirm this issue further, may I ask some of You to please visit 
> that page with some of the browsers that You have at hand and report 
> back Your experiences with it.
> 
> Please remember to specify browser and platform/OS too.
> 
> It's really annoying not being able to access those articles with SM.
> 
> Thank You All for Your kind assistance.
> 

Confirm:
*does not* work in SM 2.1 linux
*does* work in FF 1.5.0.9
0
NoOp
2/15/2007 6:04:49 PM
NoOp wrote:

> 
> Confirm:
> *does not* work in SM 2.1 linux
> *does* work in FF 1.5.0.9

Should be: SM 1.1 linux (I'm spending too much time in the OOo group :-)
and to clarify: FF 1.5.0.9 is linux
0
NoOp
2/15/2007 6:09:46 PM
Thank You all for confirming my earlier results.

What puzzles me is the discrepancy between Firefox and SeaMonkey.

In particular since the problem exists in both SM 1.0.x and SM 1.1, but 
not in Firefox 2. I wonder if Firefox *pre* 1.5/2.0 works okay?

Since Firefox and SeaMonkey share the same rendering engine, tells me 
that this cannot be a problem with Gecko - can it? Shouldn't be at 
toolkit transition problem either, since SM 1.0.x is using XPFE and SM 
1.1 XUL - right? Thus it must be somewhere in some kind of activation 
layer - whatever this is called - that differs between FF and SM.

If Firefox would exhibit the same symptoms I would feel comfortable with 
sending the report to ZyXEL instead. But since this seems not to be the 
case, I don't think I'm ready for that.

How would I suitable tag a SeaMonkey bug report for this issue?
0
Rolf
2/15/2007 7:49:11 PM
NoOp wrote:
> Rolf wrote:
>> Hi all, I seem to having been hit a bug in SeaMonkey which exhibit 
>> itself when visiting the following Knowledgebase web page at ZyXEL:
>>
>> http://www.zyxel.com/web/support_knowledgebase_list.php?pid=20070115144001
>>
>> If you visit that page, or any other of their Knowledgebase pages, you 
>> will be presented with a list of articles. Whenever the list is longer 
>> as to fit in one page, you are given navigation controls that allow you 
>> to proceed to to the next # of items e.g. by selecting 2, 3, Next or 
>> Last. Unfortunately these navigation controls don't seem to work when 
>> visiting these pages with SeaMonkey 1.0.x or SeaMonkey 1.1 - at least 
>> not for me :-(
>>
>> I'm seeing this problem with SeaMonkey 1.0.7 on Windows/NT, and I have 
>> had someone else verify the problem for SeaMonkey 1.1, running on Linux.
>>
>> The same page(s) seem to work fine when they are visited with Firefox 2, 
>> Konquerer 3.5 and IE6. The former two on Linux and the latter Windows.
>>
>> To confirm this issue further, may I ask some of You to please visit 
>> that page with some of the browsers that You have at hand and report 
>> back Your experiences with it.
>>
>> Please remember to specify browser and platform/OS too.
>>
>> It's really annoying not being able to access those articles with SM.
>>
>> Thank You All for Your kind assistance.
>>
> 
> Confirm:
> *does not* work in SM 2.1 linux
> *does* work in FF 1.5.0.9

Hmmm! That looks surprisingly like what I see design wise on Suntrust
Bill Pay section. The top and bottom are center and the center portion
shifted to the left. Ahhh! this confirms to be a Bug I turned into
bugzilla. So not necessarily the site.

-- 
------------------------------------------------------------------------
Phillip M. Jones, CET                                http://www.vpea.org
If it's "fixed", don't "break it"!            mailto:pjones@kimbanet.com
                             http://www.kimbanet.com/~pjones/default.htm
------------------------------------------------------------------------
0
Phillip
2/16/2007 12:23:08 AM
Rolf wrote:
> Thank You all for confirming my earlier results.
> 
> What puzzles me is the discrepancy between Firefox and SeaMonkey.
> 
> In particular since the problem exists in both SM 1.0.x and SM 1.1, but
> not in Firefox 2. I wonder if Firefox *pre* 1.5/2.0 works okay?
> 
> Since Firefox and SeaMonkey share the same rendering engine, tells me
> that this cannot be a problem with Gecko - can it? Shouldn't be at
> toolkit transition problem either, since SM 1.0.x is using XPFE and SM
> 1.1 XUL - right? Thus it must be somewhere in some kind of activation
> layer - whatever this is called - that differs between FF and SM.
> 
> If Firefox would exhibit the same symptoms I would feel comfortable with
> sending the report to ZyXEL instead. But since this seems not to be the
> case, I don't think I'm ready for that.
> 
> How would I suitable tag a SeaMonkey bug report for this issue?
Everyone go look at Bugzilla bug [Bug 370008]  and see if this describes
what your seeing the above website.

If so chime in on the bug.

-- 
------------------------------------------------------------------------
Phillip M. Jones, CET                                http://www.vpea.org
If it's "fixed", don't "break it"!            mailto:pjones@kimbanet.com
                             http://www.kimbanet.com/~pjones/default.htm
------------------------------------------------------------------------
0
Phillip
2/16/2007 12:27:27 AM
I just performed a test, downloading the zyxel page twice, with the help 
of wget, and comparing the contents that I received when using either of

"Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.8.0.9) Gecko/20061211 
SeaMonkey/1.0.7"   or
"Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.8.0.9) Gecko/20061211 
Firefox/1.0.7"

as the agent string, and then diff:ing the result. As you can see for 
yourself below there seems to be no difference in what the server serves 
when using either agent string. Thus the agent string doesn't seem to be 
the root of the problem, which IMHO leads pointing in the direction of 
this being a SeaMonkey specific bug.

% wget -nv -U "Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.8.0.9) 
Gecko/20061211 SeaMonkey/1.0.7" -O wget.out-SM-070216-zyxel-kb-page.html 
http://www.zyxel.com/web/support_knowledgebase_list.php\?pid=20070115144001
11:26:30 
URL:http://www.zyxel.com/web/support_knowledgebase_list.php?pid=20070115144001 
[65669] -> "wget.out-SM-070216-zyxel-kb-page.html" [1]
% wget -nv -U "Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.8.0.9) 
Gecko/20061211 Firefox/1.0.7" -O wget.out-FF-070216-zyxel-kb-page.html 
http://www.zyxel.com/web/support_knowledgebase_list.php\?pid=20070115144001
11:28:02 
URL:http://www.zyxel.com/web/support_knowledgebase_list.php?pid=20070115144001 
[65669] -> "wget.out-FF-070216-zyxel-kb-page.html" [1]
% diff wget.out-SM-070216-zyxel-kb-page.html 
wget.out-FF-070216-zyxel-kb-page.html
%

Any further suggestions, someone? Please!
0
Rolf
2/16/2007 10:42:00 AM
15/02/2007 18:06, /Rolf/:

> Hi all, I seem to having been hit a bug in SeaMonkey which exhibit 
> itself when visiting the following Knowledgebase web page at ZyXEL:
> 
> http://www.zyxel.com/web/support_knowledgebase_list.php?pid=20070115144001
> 
> If you visit that page, or any other of their Knowledgebase pages, you 
> will be presented with a list of articles. Whenever the list is longer 
> as to fit in one page, you are given navigation controls that allow you 
> to proceed to to the next # of items e.g. by selecting 2, 3, Next or 
> Last. Unfortunately these navigation controls don't seem to work when 
> visiting these pages with SeaMonkey 1.0.x or SeaMonkey 1.1 - at least 
> not for me :-(

It is not bug in SeaMonkey but bug in the web content.  Clicking on 
the page number "links" or on the "NEXT"/"LAST" buttons I observe in 
the error console:

Error: QueryForm is not defined
Source File: http://www.zyxel.com/web/includes/function.js
Line: 163

Line 163 in "function.js" reveals:

     MyObj = eval(xform);

where |xform| is a form (HTML FORM element) name.  This sort of 
trickery may work in Internet Explorer but is by no means a 
standard, nor is any good "feature" and the most important not 
compatible with SeaMonkey and other good browsers.  They should have 
really be using:

     MyObj = document.forms[xform];

The only thing you could do is inform the webmaster about the 
problem.  You could supply the above information also so they (the 
site maintainers) don't spend time figuring out the proper way.

-- 
Stanimir
0
Stanimir
2/16/2007 4:36:49 PM
16/02/2007 18:36, /Stanimir Stamenkov/:

> It is not bug in SeaMonkey but bug in the web content.  Clicking on the 
> page number "links" or on the "NEXT"/"LAST" buttons I observe in the 
> error console:
> 
> Error: QueryForm is not defined
> Source File: http://www.zyxel.com/web/includes/function.js
> Line: 163

It works in Firefox because there is some lousy browser detection 
which performs unnecessary different processing - the standard thing 
works for all browsers.  If one spoofs as Firefox it should be 
working in SeaMonkey, too.

-- 
Stanimir
0
Stanimir
2/16/2007 4:44:19 PM
16/02/2007 18:44, /Stanimir Stamenkov/:

>> 
http://www.zyxel.com/web/support_knowledgebase_list.php?pid=20070115144001
> 
> If one spoofs as Firefox it should be working in SeaMonkey, too.

And it does work for me that way.

-- 
Stanimir
0
Stanimir
2/16/2007 4:47:52 PM
Stanimir Stamenkov wrote:
> 15/02/2007 18:06, /Rolf/:
> 
>> Hi all, I seem to having been hit a bug in SeaMonkey which exhibit 
>> itself when visiting the following Knowledgebase web page at ZyXEL:
>>
>> http://www.zyxel.com/web/support_knowledgebase_list.php?pid=20070115144001 
>>
>>
>> If you visit that page, or any other of their Knowledgebase pages, you 
>> will be presented with a list of articles. Whenever the list is longer 
>> as to fit in one page, you are given navigation controls that allow 
>> you to proceed to to the next # of items e.g. by selecting 2, 3, Next 
>> or Last. Unfortunately these navigation controls don't seem to work 
>> when visiting these pages with SeaMonkey 1.0.x or SeaMonkey 1.1 - at 
>> least not for me :-(
> 
> It is not bug in SeaMonkey but bug in the web content.  Clicking on the 
> page number "links" or on the "NEXT"/"LAST" buttons I observe in the 
> error console:
> 
> Error: QueryForm is not defined
> Source File: http://www.zyxel.com/web/includes/function.js
> Line: 163
> 
> Line 163 in "function.js" reveals:
> 
>     MyObj = eval(xform);
> 
> where |xform| is a form (HTML FORM element) name.  This sort of trickery 
> may work in Internet Explorer but is by no means a standard, nor is any 
> good "feature" and the most important not compatible with SeaMonkey and 
> other good browsers.  They should have really be using:
> 
>     MyObj = document.forms[xform];
> 
> The only thing you could do is inform the webmaster about the problem.  
> You could supply the above information also so they (the site 
> maintainers) don't spend time figuring out the proper way.
> 

Excellent!

Learn a lot here how to find a problem in a web page.

Thanks Stan!

0
Marco
2/16/2007 6:02:57 PM
On 2007-02-16 17:47 CET,
Stanimir Stamenkov wrote:

> 16/02/2007 18:44, /Stanimir Stamenkov/:
> 
>>>
> http://www.zyxel.com/web/support_knowledgebase_list.php?pid=20070115144001
>>
>> If one spoofs as Firefox it should be working in SeaMonkey, too.
> 
> And it does work for me that way.

You are right. If I change the "general.useragent.extra.seamonkey" 
property, in 'about:config', from "SeaMonkey/1.0.7" to "Firefox/1.0.7" 
it works.

This means that SeaMonkey changes it's own behavior, e.g. to mimic 
Firefox, when spoofing the user agent string. Interesting!

Does it mimic IE too by just replacing the agent string? :-)

Since it's not the other way around, i.e. is an issue with Firefox 
instead of with SeaMonkey, I guess ZyXEL is less eager (whether it's a 
standard compliance issue) about fixing this, just because of a niche 
browser. If it had been Firefox that stumbled, I might stand a, at least 
slightly better, chance to make ZyXEL fix their web site (and their 
routers etc too).

<rant>
I'm sure ZyXEL have never heard of other standards than ICSA, WiFi etc. 
Standards like those of W3C ;-) . ZyXEL are YOU listening? Please visit 
this page http://validator.w3.org/ and You will soon be able to comply 
with yet another standard(s), and You will soon thereafter no longer 
need to put disclaimers (like requiring Internet Explorer) on your 
products, and thereby target the whole market.
</rant>

I guess I will have to file a SeaMonkey New Feature Request then, in 
order to have some accelerator keys added to SM, to easily mimic (switch 
between) the various user agent behaviors? ;-)

Seriously, is this a good or bad thing? And for whom?

I do appreciate the ability of SeaMonkey to follow the standards as 
strict as possible. Well, at least as long as it doesn't stand in my way 
when trying to accomplish - non-web-development related - work.

If the discrepancy between Firefox and SeaMonkey is there by purpose, it 
would be great to, at least, be able to relax the strictness of SM - 
other than changing the user agent string. Not advertising SeaMonkey, 
i.e. by spoofing the user agent string, doesn't help the proliferation 
of our GREAT SeaMonkey.

What's Your opinion about this?
0
Rolf
2/16/2007 6:30:36 PM
16/02/2007 20:30, /Rolf/:

> You are right. If I change the "general.useragent.extra.seamonkey" 
> property, in 'about:config', from "SeaMonkey/1.0.7" to "Firefox/1.0.7" 
> it works.
> 
> This means that SeaMonkey changes it's own behavior, e.g. to mimic 
> Firefox, when spoofing the user agent string. Interesting!
> 
> Does it mimic IE too by just replacing the agent string? :-)

Not really, but I think you know that.  SeaMonkey doesn't change its 
behavior but the script executed from the site searches for 
"Firefox" in the UA string and executes different code if found.

-- 
Stanimir
0
Stanimir
2/16/2007 7:02:43 PM
On 2007-02-16 20:02 CET,
Stanimir Stamenkov wrote:

> 16/02/2007 20:30, /Rolf/:
> 
>> You are right. If I change the "general.useragent.extra.seamonkey" 
>> property, in 'about:config', from "SeaMonkey/1.0.7" to "Firefox/1.0.7" 
>> it works.
>>
>> This means that SeaMonkey changes it's own behavior, e.g. to mimic 
>> Firefox, when spoofing the user agent string. Interesting!
>>
>> Does it mimic IE too by just replacing the agent string? :-)
> 
> Not really, but I think you know that.

Yes, of course :-)

> SeaMonkey doesn't change its
> behavior but the script executed from the site searches for "Firefox" in 
> the UA string and executes different code if found.

You seem to have missed one of my earlier posts Stanimir. The one where 
I pulled the same page twice. The first time with user agent set to 
"SeaMonkey" AND the next to "Firefox", and thereafter diff:ing the 
results. From the result one can see that the server DID serve the 
exactly same code in both cases. But SeaMonkey seems to handle with it 
differently depending on if UA is set to SeaMonkey or Firefox.

Do You have an explanation for that? I don't.
0
Rolf
2/16/2007 8:37:01 PM
Stanimir Stamenkov wrote:
> 16/02/2007 20:30, /Rolf/:
> 
>> You are right. If I change the "general.useragent.extra.seamonkey" 
>> property, in 'about:config', from "SeaMonkey/1.0.7" to "Firefox/1.0.7" 
>> it works.
>> 
>> This means that SeaMonkey changes it's own behavior, e.g. to mimic 
>> Firefox, when spoofing the user agent string. Interesting!
>> 
>> Does it mimic IE too by just replacing the agent string? :-)
> 
> Not really, but I think you know that.  SeaMonkey doesn't change its 
> behavior but the script executed from the site searches for 
> "Firefox" in the UA string and executes different code if found.
> 

Changing the UA in SM 1.1 linux did not make any difference for me... at
first. I tried FF and IE, no difference. Cleared disk & memory cache,
history, etc before trying each.

UA's used:
Windows IE:
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
FF:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.8) Gecko/20061115
SM:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.2pre) Gecko/20070117
SeaMonkey/1.1

And on the actual FF (which does work for me):
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.9) Gecko/20070126
Ubuntu/dapper-security Firefox/1.5.0.9

I realized that my UA spoof was missing the "Firefox/1.5.0.9" bit, so I
changed it to match the actual FF:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.9) Gecko/20070126
Ubuntu/dapper-security Firefox/1.5.0.9
and the page *does now work* for me in SM w/UA spoofed to FF.

So I decided to experiment a little; I change may SM actual to:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.2pre) Gecko/20070117
Firefox/
note the blank revision. And that works.

This is the age old problem of the website designers triggering on
"Firefox/" part rather than the Gecko part of the UA. They don't care
what revision it is, they only are looking for "Firefox/" or "Firefox".

Did another test: changed the UA to just "Mozilla/Firefox/" - that worked.

Now tried it as: "Mozilla/SeaMonkey/" - that *did not* work.




0
NoOp
2/16/2007 9:02:14 PM
/NoOp/:
> Stanimir Stamenkov wrote:
>
>> Not really, but I think you know that.  SeaMonkey doesn't change its 
>> behavior but the script executed from the site searches for 
>> "Firefox" in the UA string and executes different code if found.
> 
> Changing the UA in SM 1.1 linux did not make any difference for me... at 
> first. I tried FF and IE, no difference.
[...]
> So I decided to experiment a little; I change may SM actual to:
> Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.2pre) Gecko/20070117
> Firefox/
> note the blank revision. And that works.

Note, I've already pointed one needs just to put "Firefox" somewhere 
in the UA string (for this site) - no need to use "authentic" 
Firefox UA string.

-- 
Stanimir
0
Stanimir
2/16/2007 10:15:30 PM
/Rolf/:
> On 2007-02-16 20:02 CET, 
> Stanimir Stamenkov wrote:
> 
>> SeaMonkey doesn't change its 
>> behavior but the script executed from the site searches for "Firefox" 
>> in the UA string and executes different code if found.
> 
> You seem to have missed one of my earlier posts Stanimir. The one where 
> I pulled the same page twice. The first time with user agent set to 
> "SeaMonkey" AND the next to "Firefox", and thereafter diff:ing the 
> results. From the result one can see that the server DID serve the 
> exactly same code in both cases. But SeaMonkey seems to handle with it 
> differently depending on if UA is set to SeaMonkey or Firefox.
> 
> Do You have an explanation for that? I don't.

Yes.  The same I've said before - the script [1] linked in the page 
(its content) is one and the same, served no matter what 
'User-Agent' is given during the request, but the script is executed 
on the client side (in your browser) and it contains:

   if (navigator.userAgent.indexOf("Firefox") >= 1) {
     // code for Firefox
   } else {
     // specific IE code
   }

The Firefox code will work in IE, too, by the way.  Seems the guys 
which have written the script have pretty poor DOM knowledge because 
no specific browser code is really needed - just standard things 
which work in all modern browsers.

[1] http://www.zyxel.com/web/includes/function.js

-- 
Stanimir
0
Stanimir
2/16/2007 10:16:21 PM
/Stanimir Stamenkov/:
> /Rolf/:
>
>> Do You have an explanation for that? I don't.
> 
>   if (navigator.userAgent.indexOf("Firefox") >= 1) {
>     // code for Firefox
>   } else {
>     // specific IE code
>   }

If the above hasn't been clear enough: the "code for Firefox" will 
be executed if "Firefox" is found in the UA string, the "specific IE 
code" will be executed for every other browser.  The "code for 
Firefox" will naturally work for SeaMonkey as both browsers use the 
same engine, but it happens it would work for any modern browser, if 
that stupid browser detection hasn't been included.

-- 
Stanimir
0
Stanimir
2/16/2007 10:22:01 PM
Dear Stanimir, of course, You were of course right on the spot all the time.

I think it's time for me to have a really good and long sleep, since my 
head seems to act just like it has never ever heard about something 
called script files, that are linked into web pages. And then, once I 
have recovered(!?) ;-) confront ZyXEL with their web related issues :-)

I'm really sorry for having waisted Your time - where has my head been?
0
Rolf
2/16/2007 11:04:38 PM
Rolf wrote:
> ... As you can see for 
> yourself below there seems to be no difference in what the server serves 
> when using either agent string. Thus the agent string doesn't seem to be 
> the root of the problem, which IMHO leads pointing in the direction of 
> this being a SeaMonkey specific bug.

Not quite.  It also points to Javascript in the page.  (The script code
could be, and seems likely to be, checking the user agent string.)

Daniel



0
Daniel
2/20/2007 6:01:20 PM
Reply:

Similar Artilces:

SSL Security on the SeaMonkey 1.0.x and Firefox 1.0.x and 1.5.x
Sir: You really need to know that SSL 2 has been broken for most uses. In your Edit -> Preferences -> Privacy & Security -> SSL tab look to see if SSL 2 is enabled and disable it. Then look at the EDIT CIPHERS for SSL 3 and TSL and uncheck all the 40-bit and 56-bit cyphers. This includes the extra Ciphers tab. This change has already been done for the trunk, but you need to manually make the change in your current browser. Only re-enable SSL 2 if your bank requires it, but I'd be complaining to them. -- Bill Thanks a Million! HI William Thanks for ...

enigmail-1.0.1 for TB-3.0.x and enigmail-1.1.2 for TB-3.1.x available
Hi, enigmail-1.0.1 (TB-3.0.x) and enigmail-1.1.2 (TB-3.1.x) are available at http://enigmail.mozdev.org. Note for Seamonkey-2.0.x you can download and install enigmail-1.0.1. Have fun, Walter ...

Enigmail-1.0.1 for OS/2 TB-3.0.x and SM-2.0.x available at enigmail.mozdev.org
I'm glad to announce that after a while, where some smaller quirks had to be ironed out, enigmail-1.0.1 can be downloaded from enigmail.mozdev.org. Thanks to the developers for the upload to their site. Enigmail-1.0.1 works only with Thunderbird-3.0.x and Seamonkey-2.0.x. If you still use TB-2.0.0.x or SM-1.1.x you should stick to enigmail-0.95.7. In case of trouble please post to this list here. Have Fun, Walter ...

SeaMonkey 1.0.1 and Firefox 1.5, 2.0, 3.0 version can be said to be a same at code level
Dear, I am pursuing my research in the field of sotware maintainence at preventive level. i had published some of my research paper in ACM SIGSOFT SEN. As per my research i designed the metrics model for smelly classes with the help of firefox three versions and then i had validated or tested the metrics model with the one version of SeaMonkey. I got the review upon my research that SeaMonkey and Firefox are same at the code level. These cannot be treated as two different data set. But what i had read is they both only usage the same Gecko engine from your website. Some more from yo...

SeaMonkey 1.1.x/Firefox 2.0.0.x/et al. Xrender version dependency
I'm not sure where to post this (the old .unix group is gone). If these are the wrong groups, I apologize. I'm having problems building SeaMonkey 1.1.1 on Solaris 9. (I'm sure the same error will strike me when trying to build Firefox 2.0.0.3 or Thunderbird 2.0beta2.) First I had to give up using Forte 6 Update 2 due to Template support issues. I've installed Sun Studio 11 to deal with that, and have gotten much further. The problem now is that there is code in the 1.8 branches that now introduces an Xrender version dependency on UNIX/Linux platforms. Spe...

superreview cancelled: [Bug 335028] Firefox 1.5.0.2 Linux topcrash [@ IM_get_input_context] : [Attachment 219454] Patch rv1.1 for 1.8.x
Robert O'Callahan (Novell) <roc@ocallahan.org> has cancelled superreview: Bug 335028: Firefox 1.5.0.2 Linux topcrash [@ IM_get_input_context] https://bugzilla.mozilla.org/show_bug.cgi?id=335028 Attachment 219454: Patch rv1.1 for 1.8.x https://bugzilla.mozilla.org/attachment.cgi?id=219454&action=edit ------- Additional Comments from Robert O'Callahan (Novell) <roc@ocallahan.org> Actually, let's wait until we can verify that this fixes the real issue. Do we know anyone who can reproduce the crash here? ...

superreview granted: [Bug 335028] Firefox 1.5.0.2 Linux topcrash [@ IM_get_input_context] : [Attachment 219454] Patch rv1.1 for 1.8.x
Robert O'Callahan (Novell) <roc@ocallahan.org> has granted Masayuki Nakano (Mozilla Japan)(Offline: 4/29 to 5/1 JST) <masayuki@d-toybox.com>'s request for superreview: Bug 335028: Firefox 1.5.0.2 Linux topcrash [@ IM_get_input_context] https://bugzilla.mozilla.org/show_bug.cgi?id=335028 Attachment 219454: Patch rv1.1 for 1.8.x https://bugzilla.mozilla.org/attachment.cgi?id=219454&action=edit ------- Additional Comments from Robert O'Callahan (Novell) <roc@ocallahan.org> The code is fine, but can you explain why aArea can be null or owningWindow can...

Firefox 1.5.x.x to 2.0.x.x
Name: David Kalish Product: Firefox Summary: Firefox 1.5.x.x to 2.0.x.x Comments: I had Firefox 1.5 and I knew that 2.0 was out. I went to Help > Check for Updates, and it indicates that there was no newer version available. I think this will cause some confusion, and may result in people not installing 2.0 If 1.5 can't be updated to 2.0, I suggest at least adding a link to the main download page. Browser Details: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1 ...

From 2.1.2 to 3.1 or 2.1.2 to 3.0.13 to 3.1
I'm checking back in after being away for a couple of months and I missed the 3.1 release. I can't seem to find any info on what's new in 3.1 and also what the upgrade path should be. So, is the recommended path for upgrading from v 2.1.2 to go directly to 3.1 or do I need to go to 3.0.13 first? Are there any big issues in 3.1 that make it a "gotta have it" version?I did a couple of 2.1.2 to 3.0.12 upgrades but haven't upgraded to or tested 3.1 yet. I have one 2.1.2 site that is commercial and I need it to be down as little time as possible. It also has a lot of third party modules...

espn.com crashes Firefox 1.0.x and 1.5.x on OS X
Name: Thad Email: buzolich_at_gmail.com Product: Firefox Summary: espn.com crashes Firefox 1.0.x and 1.5.x on OS X Comments: Going to espn.com causes my processor to spike. It's been happening for a few weeks and eventually (right away, sometimes a few minutes) firefox will crash. OS X 10.3.9 This doesn't happen on my winxp laptop with firefox. Thanks. Browser Details: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b4) Gecko/20050908 Firefox/1.4 ...

Bug DNN 3.1.1 Upgrade from 2.1.2 -> 3.1.0 ->
Somewhere along the process, (I missed when) a portal upgrade created a problem with portal creation. The site is created fine, but the password for the admin is never correct. I have to use host to correct it. Anyone faced this ?Do you know the truth when you hear it? are you using the same hash keys in your web.config? this got me one time-DarrenNeese.com-DNN ROCKS!-DeveloperSchool.com Thanks, this helped me narrow it down and realize it was possibly the upgrade from DNN2 to DNN 3. Since there are no hash keys in DNN2 because it uses an encryption key, how did you solve it?Do you know ...

Firefox 1.5.0.9, Firefox 2.0.0.1 and Thunderbird 1.5.0.9 Security & Stability Updates
As part of Mozilla Corporation�s ongoing stability and security update process, Firefox 1.5.0.9, Firefox 2.0.0.1 and Thunderbird 1.5.0.9 are now available for Windows, Mac, and Linux for free download from getfirefox.com (http://www.getfirefox.com) & getthunderbird.com (http://www.getthunderbird.com). We strongly recommend that all Firefox users upgrade to this latest release. This update is available immediately in 41 languages including Spanish, Japanese, Arabic, Hungarian and more. Note: Firefox 1.5.0.x will be maintained with security and stability updates until Apr...

Firefox 1.5.0.9, Firefox 2.0.0.1 and Thunderbird 1.5.0.9 Security & Stability Updates
As part of Mozilla Corporation�s ongoing stability and security update process, Firefox 1.5.0.9, Firefox 2.0.0.1 and Thunderbird 1.5.0.9 are now available for Windows, Mac, and Linux for free download from getfirefox.com (http://www.getfirefox.com) & getthunderbird.com (http://www.getthunderbird.com). We strongly recommend that all Firefox users upgrade to this latest release. This update is available immediately in 41 languages including Spanish, Japanese, Arabic, Hungarian and more. Note: Firefox 1.5.0.x will be maintained with security and stability updates until Apr...

Is it just me or has the Fandango site stopped working with FF (1.5.0.7, 1.5.0.9, 2.0) on eComStation 1.2 ?
Hi all, I've possibly messed up my Firefox installations, but other pages still seem to work OK. Has anyone else had problems recently with http://www.fandango.com ? The home page comes up, and then completely hangs my system, and even if I ctrl-alt-delete and kill Firefox with TOP, I just get a black screen and have to re-boot. It used to work fine. If it's just me, does anyone have any advice for what might be happening or how to go about figuring it out ? Thanks in advance, Karen Roberts On Sat, 3 Mar 2007 19:13:13 UTC, Karen Roberts <kvroberts@comcast.net>...

Web resources about - Page Navigation Bug with SM 1.0.x and 1.1.x? Working with Firefox 2, Konquerer 3.5 and IE6 - mozilla.support.seamonkey

Navigation - Wikipedia, the free encyclopedia
It is also the term of art used for the specialized knowledge used by navigators to perform navigation tasks. All navigational techniques involve ...

Navigation - Wikipedia, the free encyclopedia
It is also the term of art used for the specialized knowledge used by navigators to perform navigation tasks. All navigational techniques involve ...

South China Sea: Audio reveals RAAF plane issuing warning to Chinese Navy during 'freedom of navigation' ...
... over the South China Sea. "China Navy, China Navy," the voice says. "We are an Australian aircraft exercising international freedom of navigation ...

Was Russian aircraft shot down because its satellite navigation was wrong?
... fly between the two sides. But it's entirely possible both sides are right—based on different data sources. With precision satellite navigation ...

Subaru partners with Magellan for smartphone-based navigation
Filed under: Subaru , Infotainment , Technology Subaru announces Magellan's smartphone-based GPS map and navigation app for future vehicles. ...

Maps Minutes Hack #8: Set your home and work addresses for easy navigation
... a difference. So here’s another helpful trick for how you can save a few extra minutes every time you use Google Maps for directions or navigation. ...

Smartphones are revolutionizing indoor navigation for the visually impaired
British non-profit Wayfindr is attempting to set a global standard for using audio description to help visually people impaired navigate urban ...

Mitac Magellan SmartGPS navigation system adopted by Subaru
Mitac International has announced that its Magellan SmartGPS navigation system has been adopted by Japan-based automaker Subaru for vehicles ...

Microsoft updates navigation headset for the blind
In 2011, Microsoft UK teamed up with charity Guide Dogs to create 'Cities Unlocked,' an organization that worked to create a headset designed ...

WayRay Debuts Holographic Navigation System for Vehicles
The Swiss startup is focusing on the advancement of connected car telematics, in partnership with Orange Business Services.

Resources last updated: 1/15/2016 2:33:38 PM