| 5:25 pm on Aug 6, 2013 (gmt 0)|
Quite interesting. Will have to take her on a test drive.
| 7:10 pm on Aug 6, 2013 (gmt 0)|
The mixed-content blocking by default is good. I've had it set to block for years and build websites accordingly.
I think FF needs to be improved a LOT more, including full provision for the latest TLS protocol - TLS/1 is another exploitable protocol.
Firefox is still, in my opinion as a daily and frequent user, one of the best and safest of browsers but it could be a lot safer, within the context of a badly broken internet.
Lots of info about all of this on threatpost[dot]com.
| 1:53 am on Aug 7, 2013 (gmt 0)|
The big news I noticed was that they have dropped support of the
| 1:55 am on Aug 7, 2013 (gmt 0)|
I've been reading about this new release for a while. 3 things that caught my eye:
the defeat of browser hijacking
the death of blink
1- Disarming Browser Hijackers When we type something into the URL bar, other than a URL, Firefox does a search on it. The default engine is Google. This can be controlled with the preference 'keyword.URL' in 'about:config'. Apparently, malware creators and unscrupulous add-on developers have been using this preference setting to type in their own landing pages. Sometimes it's ads, sometimes it's a drive-by.
Jorge Villalobos, Add-ons Developer Relations Lead for Mozilla, says [blog.mozilla.org ]
|keyword.URL has been the bane of our support team since pretty much ever. It is changed by most unwanted add-ons, pointing to unwanted search engines, with highly unwanted results. With this bug fixed, the URL bar now uses the selected search engine from the search box as the keyword search. While this will be an annoyance to power users in the short term, it should be easy to override with an add-on. |
And this statement from the Bugzilla forum where the proposal to change the keyword.URL preference was discussed
|50% of release users have the keyword.url pref set to something other than default which can only be done by editing about:config or by an external application. I think it's safe to assume these are being changed by external applications like software and add-on installs. Historically this is the largest issue reported to support. |
and also this one-
|50% of our users have a non- standard keyword.URL |
make it very clear!
So what they've done is eliminate 'keyword.URL' and now the default search engine in the URL bar is the same as the one in the 'search bar'. The user can change both by clicking on the arrow next to the icon on the left side of the bar. I guess the idea is that there is no preference to reset except the one controlled by the search bar, and that if that gets changed the user can change it back. Here's hoping for the best for the beleaguered Firefox team.
Furthermore some other buttons in options have been eliminated (though I don't really care about them :) [mozilla.org ] "Load images automatically", and "Always show the tab bar"
3-The Death Of Blink [developer.mozilla.org ]
Now I'm pissed! I have used the CSS text-decoration: blink; ever since my first web site. Judiciously. In my nav towers, boxes, and bars, in particular. It is a usability factor. It enhances navigability and legibility. Only Firefox and Opera have supported it, but I've put it in as a little bonus for these users :(.
You can read the all too festive discussion on implementing this move in the Bugzilla forum.
[bugzilla.mozilla.org ] Celebrated CSS guru Eric A. Meyer drops in to make a few comments.
| 2:07 am on Aug 7, 2013 (gmt 0)|
Thanks for noticing Bill, glad somebody cares :)
If you are viewing the page in the link in Engine's original post, with Firefox (but not FF 23), the entry announcing the death of blink is freaking blinking!
| 2:24 am on Aug 7, 2013 (gmt 0)|
Somebody tell me why this is a good idea.
I turn JS on/off several times a day depending on what site I'm headed for, so this would be a big inconvenience.
| 2:47 am on Aug 7, 2013 (gmt 0)|
Until then, I have discovered that you can bookmark search results pages in 'about:config'. It works like this-
(edited 45 min. later because I gave the wrong instructions. These are now correct!
| 6:46 am on Aug 7, 2013 (gmt 0)|
|I have used the CSS text-decoration: blink; ever since my first web site. Judiciously. |
It is not every day that you see the words "judicious" and "blink" in the same paragraph. I was horrified to learn that any browser, anywhere, still supports either form (tag or attribute).
:: detour to CSS3 text-decoration module with depressing results ::
| 7:14 am on Aug 7, 2013 (gmt 0)|
| 11:57 am on Aug 7, 2013 (gmt 0)|
| 12:16 pm on Aug 7, 2013 (gmt 0)|
Where's the ROFL icon when you need it?
:: shuffling papers ::
Oh, here. (Site name suppressed, duh.)
#1 visitor arrives on site
#2 visitor discovers that site will not work
#3 visitor leaves in disgust
#4 site studies visitors to inner page and discovers that 100% of them have the software configuration required by site
| 12:32 pm on Aug 7, 2013 (gmt 0)|
Lucy, no, because you can detect visitors who did not have JS on at step 1.
Of course you need to look at new, not returning visitors.
The numbers for JS off are very low even on sites that work perfectly without JS.
It is also perfectly easy to notify visitors why the site is not working, and those who turn off JS should know how to turn it back on.
| 3:39 pm on Aug 7, 2013 (gmt 0)|
Sure you don't mean Java there?
|brotherhood of LAN|
| 3:47 pm on Aug 7, 2013 (gmt 0)|
I hope their web dev tools can be switched on and off, I might want to scour the DOM for a particular site, but not on every page load. Alas, that's why firebug gets turned off and on all the time, for me... as it slows it all riiight dowwwnnn... particularly for JS heavy sites manipulating the DOM.
| 4:02 pm on Aug 7, 2013 (gmt 0)|
That's another point I always like to make. Those who turn it off know what they're getting into and know what to do.
|those who turn off JS should know how to turn it back on. |
| 5:25 pm on Aug 7, 2013 (gmt 0)|
I just love blink. And In reading, I am very sensitive to annoyances, since I drink a lot of coffee. Also, I am a bit of a perfectionist. Yet, I have found it to be a very handy signifier for something of particular importance on a web page, that the viewer needs to know is there. This is usually a nav link. But it can be an announcement, a warning, etc. If placed on the page with politeness and forethought, it is a usability aid. Or at least it was :)
Well, that's it for me, at least for a while. I'm traveling with no computer. Using portable apps on a thumb drive. And this morning I discovered that my thumb drive has been stolen in a library for the 4th time! Lost most of my work each time. I can't do much without it. I'm tired and moving on.
Thanks everyone for everything. Hope I get back on the web with some new hardware someday, but I'm giving up today. Going to spend some time watchimg the sunsets and maybe eat some ice cream. Ciao for now...
| 5:42 pm on Aug 7, 2013 (gmt 0)|
| 6:07 pm on Aug 7, 2013 (gmt 0)|
I'm aware of other ways to turn JS on/off and that most people surf with it on.
I'm still waiting for someone to tell me why removing the easy option button/checkbox is a good idea.
| 6:55 pm on Aug 7, 2013 (gmt 0)|
Cause no one uses it and they can use the space for something else. It's also something else that doesn't need maintaining or testing.
| 7:16 pm on Aug 7, 2013 (gmt 0)|
FF 22 and below let you prevent JS from disabling the context menu. Hopefully we can still do that from about:config.
| 8:14 pm on Aug 7, 2013 (gmt 0)|
commanderW - my tirade was using yesterday's FF. Linux upgraded to 23 today. :)
An add-on to turn JS on/off - surely you're all using NoScript!? Anyone not using that excellent add-on is simply asking for trouble. It does FAR more than turn JS on/off.
Java has been a known virus vector for a decade or more and anyone in their right mind has it turned well off!.
| 9:08 pm on Aug 7, 2013 (gmt 0)|
|Java has been a known virus vector for a decade or more and anyone in their right mind has it turned well off!. |
But I'm entering my 10th year of developing for the web. I've never met a developer, or any technical person, who ever turned js off. Sitting here in a client's office, I look at the five others here who are coding like mad on many different systems and I don't have to check to see if any have js off. The guy next to me is snickering as I write this.