For those having issues with the Internet Explorer on Windows Phone 8.1 and the way it renders websites, your troubles might soon be over as the upcoming WP 8.1 Update 1 is set to change that.
According to Microsoft, a lot of websites don’t recognize IE as a mobile web browser and shows desktop content instead, resulting in a much different web experience compared to Android or iOS. However, thanks to the WP 8.1 Update 1 (coming to developers next week), which among other changes also brings different User Agent string and webkit prefix support, there was a 40% user experience improvement among 400 top mobile sites that Microsoft has tested.
Windows users rejoice.
Good news, Google has just announced the availability of 64 bit builds for Windows users on its Beta channel.
The best part: when you install it, it will replace your existing installation with all the settings intact. As if now, it’s available for Windows 7 and 8 users only so if you are still rocking Vista or XP, time to switch.
Here is one for the desktop PCs.
Recently, Mozilla has released the beta version of Firefox 32, which brings some rather unimportant features (with the exception of HTTP caching (v2), which includes expected performance improvements), at least for the average user and more HTML5 / developer goodies.
Want to know full details? Check them below,
Another month, another CEO.
It seems like Mozilla has been replacing CEOs more often than some people replace their socks and today the open source organization has announced “the chosen one”: Chris Beard.
Who is he? Mr. Chris Beard first joined Mozilla back in 2004 so he does know a thing or two about the company. Earlier this year he re-joined the company as the member of the Board of Directors and the interim CEO.
Another good day for Android users.
If Chrome is not exactly your cup of tea then rejoice, as here comes a new version of Firefox for Android and this is what’s new:
You can now customize your home screen pages, re-order them, chose the default ones, hide them and so on. Additionally, a browser will no longer have to be restarted when switching between different languages although it’s not like people do that very often anyway. For developers, there is a new set of APIs and you can learn more about them here.
Brings one neat feature.
Following the desktop release, here comes one for your handhelds and it does look pretty good. Thanks to the recent improvements, you will no longer have to sign in on Google web sites again (gMail, Maps, Search), which is a very welcome step.
In addition to that, the latest Chrome build now also includes glimpses of Googles’ Material Design language (see screenshots here), which will roll out to all products in the coming months.
Say hello to BoringSSL.
After the recent Heartbleed bug paranoia, it looks like Google took a pretty significant step to minimize such risks in the future. According to the report, the search giant is replacing OpenSSL with its own BoringSSL (yes, they did call it like that) in an effort to streamline security patches and improve overall user security.
Grab it while it’s hot.
Today, a bunch of folks from Norway have released the final version of Opera 23 where the addition of the heart icon (where it will now take two instead of one click to add sites to Speed Dial or bookmakrs) is touted as the most significant new feature.
When it comes to other changes, startup time will be faster for Opera Turbo users with slower connection, insecure content will no longer load on HTTP pages, also, a support for Pepper plugins and better user experience during plugin freeze.
With DirectWrite (Windows only) support and more.
It seems like there was a while since a decent Chrome update, which actually brought useful features, at least up until now as the latest Beta version does deliver.
First in the list is DirectWrite support, which is Microsoft’s latest text layout and glyph rendering API introduced in Windows 7. Thanks to this, text will no longer look like from the Windows XP era (see the picture below).
Talk about priorities.
A battery draining bug that was first reported back in 2010 is now being investigated by Google, according to the reports.
The issue stems from a poorly set system clock tick rate (1.000ms) while Microsoft themselves recommend developers to use (15.625ms). So what does that mean? It means that the processor is being woken up far more frequently that it should be, affecting battery usage by as much as 25%.