Showing posts with label firefox 3. Show all posts
Showing posts with label firefox 3. Show all posts

Thursday, August 26, 2010

Google Toolbar broken, can't update, breaks tooltips in Firefox 3

Google Toolbar doesn't work any more. No idea why. None of the buttons show up, can't search with it, can't change options. Uninstalling and reinstalling doesn't work ... and for an added bonus, Google no longer posts updates through Firefox's add-on manager. Why? Same reason Microsoft jacks around with stuff, to drive traffic to their site. "Don't be evil" my ass. All big companies operate the same way; they do so because they can. Market pressures are the only things that prevent smaller companies from screwing their customers as much as possible ... after all, that's the ideal business relationship for a company, everything for them and nothing for you.

For another added bonus, if the broken toolbar is installed, you get no tooltips anywhere. Why? Don't ask me, I'm just a user. (Of course, it could also be something on Mozilla's side, like the script that runs to infinity after I've updated the add-on and can't be killed because it starts up again right away. Nothing like going to Task Manager to kill Firefox so that you can finish installing an add-on.)

I find it interesting that this happened basically the same day that they added a new "feature" to Gmail, which of course means something else that none of us really wanted in the first place. This time it's the ability to make phone calls. woo! Way to undercut the market for your Android phones, Google.

plus ça change, plus c'est la même chose.

Wednesday, August 27, 2008

Follow-up

Today, I start by discovering a solution and a problem.

Solution: IE 7 and Firefox 3 do not treat <button> elements the same. If IE sees a button of type submit, it will assume that what you want to do when someone clicks this button is to submit the form; if there is any JavaScript in the onclick event, it will run that in addition to submitting the form. Firefox sees the JavaScript and runs it instead of submitting the form.

This is kind of a problem if your JavaScript calls the submit() function. :)

So I changed the type from submit to button and everything was fine.

Then I found my problem. We have passwords in a database, I want to check the user's password against the database password. Done: I use <cfqueryparam> in the query to ensure they don't put funny little things in there.

But you can also change your password. If you do that, and you log out, when you log in again, I want to check for your new password. I can't do that if the query is cached. The problem is that I can't make the query un-cache (we don't have CF 8 on this server, although I'm not sure that would help much) because you can't use cacheafter or cachewithin when you use cfqueryparams.

So I need a solution for that.

After a sub-optimal day, I return home and find poop in different places, of course. Here's one spot, right by the box I want to use to return my defective headphones. And look, there's something sticking out of it, like a twig. (Um, these are indoor cats ...)

And I pick it up, but it's light, and I drop it on my hand ... oh, at least it's dry ... wait a minute.

That is kind of a twig. This isn't poop. It's a leaf.

d'oh.