Date: Thu, 11 Sep 2003 22:06:11 -0500 From: Jeremy Messenger <mezz7@cox.net> To: Adam McLaurin <blueeskimo@gmx.net> Cc: freebsd-ports@freebsd.org Subject: Re: Warning: Galeon 1.3.8 is buggy (unusable?) Message-ID: <oprvc9klf58ckrg5@smtp.central.cox.net> In-Reply-To: <oprvc9e9b48ckrg5@smtp.central.cox.net> References: <1063334273.40543.9.camel@jake> <oprvc9e9b48ckrg5@smtp.central.cox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 11 Sep 2003 22:02:59 -0500, Jeremy Messenger <mezz7@cox.net> wrote: > On Thu, 11 Sep 2003 22:37:53 -0400, Adam McLaurin <blueeskimo@gmx.net> > wrote: > >> Galeon 1.3.8 seems to have some problems with forms on some websites. >> The problem doesn't seem to occur on everyone's installation (one of my >> boxes is fine, and Marcus's box is fine), but myself and another guy in >> #galeon (GIMPnet IRC) are having the exact same problem. >> >> Essentially, when you fill out a form and submit, the data isn't >> processed correctly. The processing script ends up with no data at all. >> I've reproduced this problem on both POST and GET forms, so it's not >> specifically related to method. >> >> Two websites that are known to cause problems for both of us are: >> http://boston.craigslist.org/nfa/ >> http://www.freebsdforums.com/forums/search.php >> >> Anyhow, we're both researching the problem now, and will discuss it with >> the Galeon team tomorrow morning. We both suspect it's a Javascript >> error, but we haven't proven anything definitively yet. > > I personal don't think it's JavaScript issue, because the first link > doesn't has any of it. The second page, it has very small JavaScript[1] ^^^^^^ Err, I mean link.. :-) Cheers, Mezz > and I don't know how it can cause the GET/POST forms problem, since this > only does the refresh job. > > [1] <a href="javascript:window.location=window.location"> > > Cheers, > Mezz > >> For now, I'd recommend perhaps holding off on upgrading. If we can prove >> this is a problem specifically in Galeon 1.3.8, a fixed version should >> follow quickly. >> >> If you DID upgrade to 1.3.8 and find yourself having this problem, you >> might have to remove ~/.galeon and downgrade back to 1.3.7. Going back >> to 1.3.7 without removing the settings didn't fix the problem for me. >> Once I removed the settings, all was fine again (well, as fine as it was >> before I started messing with 1.3.8). >> >> If you need further help with this, swing by #freebsd-gnome on FreeNode >> IRC. > > -- bsdforums.org 's moderator, mezz.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?oprvc9klf58ckrg5>