| 10:26 pm on Jun 4, 2012 (gmt 0)|
You are looking at Firefox 12, NOT Firefox 4. Just want to be sure you realize that Firefox is currently at version 12.
| 10:34 pm on Jun 4, 2012 (gmt 0)|
I are confused.
Why did my last version say "3.6.24" and this one says "12".
Were there (8) major version upgrades in a year -- or just a change in numbering system?
NOTE: If this is v.12 -- someone please change the title of this thread.
| 11:37 pm on Jun 4, 2012 (gmt 0)|
Yup, FF has been jumping major version #s for the past couple of years at a rapid pace and has just recently jumped from 9 to 12 in very little time.
| 2:17 am on Jun 5, 2012 (gmt 0)|
Apparently the "Status-4-Evar" add-on was the official fix for the status bar issue. I couldn't live without it either.
You'll be excited to know that FF 13 will be out momentarily. ;)
| 7:00 am on Jun 5, 2012 (gmt 0)|
stuff that bugs me...
Right Click on Link: the fly-out always had "Open Link in New Window" first, then "Open Link in New Tab" second --- now they reversed the order.
I was wondering why new windows kept opening -- kinda sucks having to relearn the basics of a software package because it got upgraded.
(I'd still be on DOS 3.2 if I had my way.. it was the best OS from MS ever).
* Living on the rusty edge of technology *
| 6:04 am on Jun 6, 2012 (gmt 0)|
|Right Click on Link: the fly-out always had "Open Link in New Window" first, then "Open Link in New Tab" second --- now they reversed the order. |
Probably to get in sync with IE.
|You'll be excited to know that FF 13 will be out momentarily. |
My heart's pounding. I'm realizing that I must have turned off "nag me about updates" and I'm still on 11.0, wondering why everything was so peaceful. Do I want to fool with 12, or should I just wait for 13?
I'm not seeing a status bar on 11.0.
| 7:43 am on Jun 6, 2012 (gmt 0)|
If you allow it FF will now automatically update similar to Chrome, without nagging you at all. When I setup someone else's machine I always make sure the automatic update is turned on. That's a huge maintenance timesaver.
I can't recall when that disappeared officially, but this Mozilla KB article indicates it was sometime after version 4: [support.mozilla.org...]
| 8:43 pm on Jun 6, 2012 (gmt 0)|
- View Image: I'm frequently right-clicking on images and doing a "View Image", (to see the URL, or see if it is scaled via <img> tag width or height, etc). The image was always shown top-left in the window, on a white background -- now the image is centered on a black background... Not a biggie, just something different to throw me off kilter, (at first I thought it was the site I was looking at doing it -- then realized it was the browser).
Again -- I went from "3.6.24" to "12"... so don't know when this change happened.
| 7:28 am on Jun 7, 2012 (gmt 0)|
Yeah, the status bar has been missing a real long time, nothing new and quite annoying really. That little pop-out to show the URL where the status bar used to be isn't the same.
They should make it a checkbox on the VIEW menu and let those of us that want it, need it, and have REALLY BIG SCREENS enable the old status bar.
Browser UI is actually getting worse, not better, in the latest releases of MSIE and FF if you ask me and I can adapt to just about anything until it becomes next to ridiculously hard to use which FF is quickly becoming.
| 9:21 am on Jun 7, 2012 (gmt 0)|
|If you allow it FF will now automatically update similar to Chrome, without nagging you at all. When I setup someone else's machine I always make sure the automatic update is turned on. That's a huge maintenance timesaver. |
I look at updates differently. I view an update as a possible disruption/mess that I don't want to deal with while I'm in the middle of something important, so I like to be able to pick my time. Eg, if I'm relying on a FF extension during a project, I don't want to chance it will be disabled by an update... and I generally don't want to take time to check out how long my current extensions are predicted to work.
| 11:33 am on Jun 7, 2012 (gmt 0)|
My FF 12 just auto-updated to FF 13 so this thread is old new ;)
|if I'm relying on a FF extension during a project, I don't want to chance it will be disabled by an update... and I generally don't want to take time to check out how long my current extensions are predicted to work. |
Having your computer security held hostage over an add-on is a bad strategy.
Imagine some flaw in the browser allows your computer to get seriously hacked and you could have way more trouble on your hands than a disabled add-on, such as compromised server passwords, your machine being involved in a botnet spamming and hacking other computers, etc. etc.
Try explaining to your customer that your computer got hacked because you refused to update until his project was complete because you were afraid some FF SEO add-on might not work and now the machine is out at Geek Squad and may not come back for days or weeks and "... oh BTW, your FTP passwords were probably compromised..." or worse.
The next sound you hear will be the sound of his check bouncing off your bank account as he has the bank put a stop payment on it.
Not that there's anything wrong with using FF add-ons to do your work, I would just make sure I have a backup plan that will get the same job done in the event they no longer exist. I've been burned by a few add-on developers that literally just drop the ball and don't do timely updates to base a business strategy around any of them. If you can find any other alternate way to do the job, besides a FF add-on, I would opt for that route before banking on a single FF add-on. If you can't find anything, perhaps ask some developer your know to build it because others may be seeking an alternate solution as well, you never know!
But that's just me, YMMV.
| 5:54 pm on Jun 7, 2012 (gmt 0)|
I never liked auto updates for anything, and always had them set for manual when possible. MS made it nearly impossible to run that way -- I'd get near daily "Updates are Ready, Install Now or Wait (1 hour)" type messages -- eventually I caved in on the Windows automatic updates.
I still don't let browsers update automatically -- and I think it's with good reasons. How many times does a release need a "security update" 24-48 hours later because the NEW version introduced an exploitable bug?
I prefer to live on the rusty edge of technology -- give the software a year or so to age and mellow.
I think a lot of "updates" and "upgrades" are driven by marketing departments so they can say, "Look! New! Different! Improved!"... and all they did was rearrange the menus -- but it gets them some press.
I liked FF 3.6.24... it allowed me to skip several versions I never missed. I only upgraded because for some reason Adsense control panel no longer properly displayed under it. Now I have 4-5 new issues to deal with on the browser side -- and after a week, I'm already a version behind "the bleeding edge".