I recently downloaded Firefox browser which I love so far, however when I come to this site and try to post/reply/edit I can't. those buttons just don't show up to click on. any ideas why?
It might be something specific to your configuration.
Firefox (Phoenix, whatever) has been my primary browser for quite a while, at least since before I registered here with my current ADT handle (July 2003).
I've certainly encountered a few hiccups at various sites, but nothing close to what you have described here for ADT. My guess is that your cookies or preference file has been corrupted.
My guess is that of my ~1255 posts, perhaps 1240 have been with a Firefox browser (or predecessor). I'm running Firefox on both Mac OS X and Windows 2000 computers.
Have you tweaked some colors in the Fonts & Colors under Tools -> Options -> General? Is a downloaded theme messing up? the css file could be screwed or have been incorrectly edited?
I do think it could be a cookie issue. Those buttons don't show up if the server doesn't think you're logged in. Are you logged into your forum profile?
Thanks all for your responses. I goofed. I used FF to view this site while still running Opera, so what happened was that I was logged in from Opera, but not from FF. that's why I couldn't see those buttons.
Aside from the ones mentioned above I use these daily:
Image Zoom 0.1.7 (which hole is that cock in? ) Duplicate Tab 0.5.1 Web Developer 0.8 (there's a handy option to disable referrer logging, which is how some sites block picture links) Text size toolbar 0.2 (useful on notebooks to read small text)
jrv-if you just want to disable referrer logging, isn't it easier to type about:config in the location bar, scroll down to "network.http.sendRefererHeader" and just change the value from 2 to 0? the reason i ask is that web developer, while incredibly versatile, writes TONS of new code for firefox to go through and it does slow things down a bit if you're just changing one thing.
There are some sites that need referrer logging to work right and Web Developer is a relatively easy way to switch on and off. I think adultcdmovies is one such site.
damn you jrv, and damn your refusal to type about:config into the the location bar and change network.http.sendRefererHeader from 2 to 0. i'm onto you and your scheme to take webdeveloper public and rule the world.
I tried Firefox. Not sure that I think it is faster than IE. But it was able to display one site that IE had a problem with. Maybe I will try it a little more.
#SDNY he's all yours. -- Michael Steele 5110 Posts 3/03
Posted - Mar 31 2005 : 10:57PM
Pete, try this: open a new tab and type "about:config" in the address bar. Go down the long list of stuff that comes up and find the line that starts with "network.dns.disableIPv6." If the value shown is "false" instead of "true," double-click on the line, which will toggle the value. Close the tab.
FireFox seems to draw/render differently than IE, so it may seem different even when you're download-speed limited.
Broadband users can try the Tweak Network Settings 1.0 extension, to have FF download more page elements and to use pipelining when possible.
Dial-up users might turn off favicon display.
I've never tried it, but you can tune the way "reflows" happen. This is when the browser draws a partial page as the page downloads. This might make it feel better, even though the result is no faster.
what jrv's talking about is the placebo effect you're missing when firefox shows the outline of an image while it loads which ie doesn't. it's at browser.display.show_image_placeholders, try setting it to false.
i've been totally unimpressed with firefox's development for the last year having used it since 2003 or maybe a few months earlier. it's autocomplete stores your credit card info in plain text, so you have to choose between disabling it all the time, using something else for ordering stuff, or having it totally unprotected and visible to anyone who sits at your desk for a second and thieves online. it's not a classic memory "leak", but it still sucks at handling unused space and it's getting dumbed-down by the release.
the real problem is with the developers. a disturbing number of the important ones have stopped working on it, practically nobody's still there for reviews, they're at other companies or just are fed up with people too new to be competent, over-trademarking, soul-selling to google and the general apathy of their peers. right now, 2.0 is optimistically late 2006, maybe a ways into 2007. it's tied to the same gecko engine as the mozilla suite and has traditionally lagged a little in adoption to new shit. when they recently announced the suite was abandoned, they just lost all of the cross-platform people and a bunch of forward-momentum they provided. there was a lot of trickle-down benefit from the suite and who chose to develop it and aren't interested in joining current projects, let alone ones becoming a mess.
If that happens it is an error of the website builder, a properly setup creditcard payment page should use https for starters and use the right type of form so that it doesn't happen.
Oh and a tip for about:config, you don't have to scroll that long page, just type what you are looking for in the filter at the top and press enter, you will end up with only those entries that match your searchstring.
The idea that 16 digit numbers are somehow more sensitive than 15 or 17 digit numbers is peculiar. Their basic argument probably goes you need to have OS security anyway, that the credit card companies don't care & haven't done anything about card number security, and that there's no way to tell what is and isn't sensitive.This is what I call the Microsoft syndrome, where you look around and realize that the last person who left forgot to turn off the lights, and nobody has yet realized the building is empty...
The FireFox guys should spend more effort on recruiting programmers. FF is huge and has a big learning curve. I could fix your complaint above by hacking in a test into autocomplete, rejecting saving if a regular expression matched: “...-..-....” might be another good one for Americans in addition to 16 numerals. Coding that is easy, but finding the spot to do it, and making the regexp's configurable, would take a long time to figure out.
even if the developers aren't going to accomodate something webmasters do wrong commonly enough to be a problem, it's just totally crazy to have it complete sixteen-digit numbers. there are probably nine people who have to constantly type numbers with exactly that many digits in constantly on the face of the planet. i'm almost positive i've never typed 16 numbers in for something other than a credit card number, that's so easy and so wise to disable it kills me.
I found the code ... and there isn't a useful comment in sight, nor a hint of how extensions hook in. I guess someone skipped reading RMS's style guide. It's objectified C++ code with abstracted data typing. Ug.
I don't see a regex library for their string type? That's hard to believe. No wildmat either. My enthusiasm for hacking this in is fading rapidly...
A webbrowser should perform according to the standards set by the W3C and not cater to lazy websitedevelopers, otherwise we'll end up with more crap like IE.
And I would seriously think about what else a website will have done wrong if their creditcard form is written so sloppily, that's not a good sign...
As most websites are built around the majority browser it is quite possible that there are crappy non w3c conforming sites out there. I know that the css I did for one site doesnt work properly in firefox the only solice is the client doesnt check the site in firefox
Just before I throw my PC out of the window ...I've been using Firefox for months and months, all working fine -- until this evening when I've been trying to update my blog with blogger and I started getting the "This document contains no data" alert. Which means I can't get into blogger, which means I'm annoyed and vexed. I had look around the Firefox forum -- very difficult to find any solution. Has anyone else had this problem? Any ideas on how to fix it would gratefully appreciated.
Thanks jrv, your comment prompted me to try IE which worked. When I got into the blogger status page in help there was a mention of difficulties being experienced with the advice to clear cookies. It is working now I'm pleased to say.
Edited to add I of course spoke too soon still wierd things going on -- maybe it's time for bed and I'll hope the good computer fairy fixes it while asleep.
Lou for help on computer problems please use my 0870 support number ;) or mail me or start a new thread - entitled my pc is broken who will nick the thieving winkies now?
Besides regular expressions and wildcard matching libraries (which I am surprised to hear the absence of and point out "some 19 year old developers may be brilliant slackers but they're still slackers") I hereby submit: a "creditcard" text <input> type. If that was integrated into the w3c standard, all browsers could be set to never autocomplete a field of that type.
