Paul, I don't mean to be a jerk, but isn't it clear that this is somehow related to your mac install or your specific profile? A few people have confirmed there is no problem with the Citibank site. You've played with your profile, installed extension programs, moved and copied files, played with development snapshots, and tested several ways to do things... whatever the problem is, it doesn't appear to be related to a default install of Camino, since no one else can replicate this problem. Is that fair?
Nobody likes losing their cookies, preferences, bookmarks, etc, but at some point you have to accept that preserving your profile may be preserving whatever problem exists. Am I wrong here? AS --- Camino List <[email protected] wrote: At 12:00 PM -0800 3/6/07, [EMAIL PROTECTED] supposedly scribed: > > >It's not clear to me from that description that you are are checking > >the right files at the right time. The value of prefs.js at launch is > >irrelevant if you have another value in user.js. > > > >If you haven't already tried exactly this: > >- Quit Camino > >- Move aside your profile > >- Launch Camino to create a new profile, then quit (don't visit the > >site during this launch) > >- Install UserAgent, and nothing else > >- Launch, and spoof as Firefox 2 (don't visit the site before > >switching your UA to FF2) > >- See if the site works (and if so, if it works if you quit, relaunch, > >and visit again) > > > >-Stuart > > Stuart, I'm not trying to make you crazy, but am going slowly mad > myself. Saw a 104 release and got it. BTW, I think I AM checking the > right files... I don't have a user.js, so pretty sure it's all from > prefs.js. I only "look" into that file when Camino is NOT running. I > don't edit that file manually, just open it to see what is in there. > > Anyway, I quit and re-launched Camino, checked UserAgent to see it's > set for Firefox 2. Connect to the bank, it's renders correctly. > Interesting. Quit and re-launch Camino, go to bank, does NOT render > correctly. Confirming behavior from yesterday when it worked > correctly, but a quit and re-launch made it NOT work correctly. Used > UserAgent to set it back to default, quit Camino, checked prefs.js, > no override listed, quit BBEdit, re-launched Camino. > > Go to bank, ah-ha, now I get the "supported browsers" page as I'd > expect, the one I ALWAYS got when using 103. A ha, it renders > correctly. Quit and re-launch, two in a row, renders correctly. But, > after a third launch, back to bad rendering. > > I can't really see much sense in this; all I DO know is that it never > failed to render correctly when I was using 103. And it appears that > there ARE times it can and can't render spoofing FF2 and it can and > can't render with no spoofing going on. Oh, obviously going to the > site so frequently MAY add issues, typically I'd go there, do my > business and leave only go 2-3 days before I'd go there again. > > Next, I followed your suggestions to the letter (I also copied my > bookmarks file over, I can't imagine how THAT file could have any > impact), BUT it did not render correctly on the first try (spoofing > did happen because I did NOT get the "supported browsers" page. > > THEN I remembered the cache, so along with several cache empties, I > repeated. NOW it seems to work through at least 2 launches. BUT, I'm > not so sure I want to "give up" all my cookies OR the large list of > extra search engines from prior (something is odd there, I notice in > my old profile, the SearchURLList.plist file is default, yet I did > have more than default engines listed, so I have to find out > where/how). > _______________________________________________ > Camino mailing list > [email protected] > http://mozdev.org/mailman/listinfo/camino > _______________________________________________ Camino mailing list [email protected] http://mozdev.org/mailman/listinfo/camino
