It has been about 3-months since I last posted. I had to retire the machine I was running Windows 10 on, an old Dell Optiplex as it was having hardware issues. I did not want to be putting money into a system that is over 10-years old, especially since I only paid $25 for it last year. Yet, I currently do not plan on upgrading anytime soon to Windows 10 on either of my two machines (Gateway Windows 8 Desktop and HP Windows 7 Laptop). Still not sure what I am going to do as I would like to try out Windows 10…
Read More
This very odd statement is from Microsoft MSFT 108,22 +1,32 +1,23% Marketing chief Chris Capossela. “We do worry when people are running an operating system that’s 10 years old that the next printer they buy isn’t going to work well, or they buy a new game, they buy Fallout 4, a very popular game, and it doesn’t work on a bunch of older machines,” Capossela stated. “And so, as we are pushing our ISV [Independent Software Vendor] and hardware partners to build great new stuff that takes advantage of Windows 10 that obviously makes the old stuff really bad and not to…
As we reported earlier, on December 17th NetFlix has started offering HTML5 videos for Firefox users. While this not a big deal for the Win32 users as they could still use Silverlight with Firefox, this is not the case for the Firefox Win64 users. The newly released Win64 Firefox browser does not support NPAPI plugins (except Flash). Note: Silverlight is planned on being supported with the upcoming Win64 version of Firefox 44. However, by the end of 2016 Mozilla plans on removing support for the very outdated NPAPI plugins (except Flash) from Win32 and Win64 versions of Firefox. Google Chrome ended support earlier this…
At least for a while as Mozilla still plans on deprecating Silverlight support sometime in the future (much as Google and Microsoft already have). Bug 1225293 which was made public today indicates Mozilla’s short term plans to support Silverlight in the Win64 builds. When exactly Silverlight will return to the Firefox 64-Bit builds is not exactly known. It could (but not likely) be with Firefox 43 already in Beta and due out December 15th, 2015 or (more likely) Firefox 44 still in Developer’s Edition (Aurora) and due out in late January 2016 or Firefox 45 currently in Nightly builds and due out…
The title of this post sounds quite like a marketing gimmick by Microsoft to promote their new Windows 10 browser. It could be for a TV commercial or online advertisement. Actually it is the messages Windows 10 users may see if a new ‘feature’ in a forthcoming Windows 10 update is left in place when they attempt to change their default browser to Google Chrome or Mozilla Firefox. Microsoft has already made it a pain for users to change their default browser by making them do it from within the Windows 10 settings instead of allowing from within the browser itself. But, now…
Following in the footsteps of Google and Microsoft, Mozilla plans to eliminate support for the ancient NPAPI plugins (with the exception of heavily sandboxed version of Flash) in the next year. This would include the 32-bit versions of Firefox. There has been a lot of heated discussions in the past few months in regards to Mozilla removing the support of NPAPI plugins (mainly Silverlight and Java) from the upcoming (Firefox 43?) Windows 64-bit (Win64) version of Firefox. I agree this needs to be done as NPAPI plugin technology is over 20-years old from the Netscape days and is badly outdated…
People are still complaining about how Mozilla is removing support for NPAPI plugins (Silverlight and Java specifically) in the upcoming Windows 64-Bit release of Firefox (now tentatively scheduled for Firefox 42 in November) even though the move is not that unusual given the trend to move away from NPAPI plugins by other browsers. Microsoft’s Edge Browser (Windows 10 only) does not support Active X or any of the NPAPI plugins (Flash is integrated not a plugin). On Tuesday, September 1st Google released Chrome 45 which ended the browser’s support of NPAPI plugins as well. I found this out when I…
Back in July Mozilla’s Dave Camp had talked about in his email how to get Firefox away from being dependent on XBL and XUL. At that time, many on mozillaZine were concerned that this could have dire consequences on the future of Firefox as trying to move away from a development system that has been used for the past decade would not be easy. If anything, it would require a complete rewrite/redesign of the desktop version of Firefox. Many had hoped this would be like a campaign promise and people would forget about it. Unfortunately, Mozilla has lived up their…
“You can check if your browser supports all the codecs for YouTube by checking the YouTube HTML5 Video Player website, which list everything supported on your PC. If you have a Linux systems and Firefox 40, it’s likely that some of those codecs will have a red sign, meaning that they are not enabled. All you have to do is open about:config and make the following changes. Please make sure that you don’t change anything else. …” Source: Softpedia
Mozilla is moving right along with getting Firefox 41 ready to ship for the September 22nd release. Having had a chance to play with the current Beta version of Firefox 41, here are THREE major changes users should be aware of to avoid headaches upon updating/downloading: New ‘New Tab’ behavior. Gone are the days users could set their preference as to what comes up when they open a new tab via the browser.newtab.url preference in about:config. Nope, that was being ‘exploited’ so Mozilla removed this functionality that has been in Firefox since Firefox 13 (June 2012). There is a simple solution, Custom New…