The Chrome 35 beta was notable for several enhancements targeted at developers. It has now been promoted to the stable version, but not all of its features are included.
The list of fixes and improvements in Chrome 35 for Windows, Mac and Linux provided by Karen Grünberg on the Chrome Releases Blog is:
More developer control over touch input
Unprefixed Shadow DOM
A number of new apps/extension APIs
Lots of under the hood changes for stability and performance
The enhancement that has progressed is that web content on desktop computers will now receive mouse scroll wheel events with the ctrlKey modifier set, which gives devs the freedom to do something other than simply zooming.
The one that has been delayed is the touch-action CSS property, which provides a mechanism to selectively disable touch scrolling, pinch-zooming, or double-tap-zooming on web content.
Grünberg also notes that 23 security fixes are included in this release and lists six that were discovered by external researchers leading to payouts totalling $9,5000. Two researchers each earned $3000 for high impact vulnerabilities:
Use-after-free in styles
Integer overflow in audio
Three payouts of $1000 were made, one for a flaw rated High:
Use-after-free in SVG
and two for Medium ones:
Out-of-bounds read in media filters
UXSS with local MHTML file
Another Medium bug was awarded a payout of $500:
UI spoofing with scrollbar
Chrome 35 for Android has also been released. Its features include:
Undo Tab Close
Fullscreen video with Subtitles and HTML5 controls
Support for some multi-window devices
Support for casting some web videos with Chromecast
Having tested the Chromecast functionality with the edX and FutureLearn platforms, I can now view MOOC videos on a full screen TV rather than my Android which is helpful.
Google has just revealed the fact that it has applied for at least six patents on fundamental neural network and AI. This isn't good for academic research or for the development of AI by companies.&nb [ ... ]
The story of MathML is not a happy one. It is a good idea - create a markup language for mathematical equations - but for some reason people just don't seem to want to get behind it. Will the ne [ ... ]