Today Google released Chrome 48 and has deprecated RC4 as encryption protocol because it’s broken.
This means that if you have an older version of Domino that doesn’t support some other encryption protocol for https.
Domino 9.0.1 FP4 or FP5 will give you the support you need to use updated protocols.
And I really hope Google would implement the Swedish error page for everybody 🙂
Google breaks with Webkit and starts a competitor rendering engine Blink and the main reason is that they don’t want to be controlled by Apple what goes into the engine or not. Opera also annouced they will start using this engine. I think this started when Apple did throw out Google from IOS 6, now they throw out Apple from a free ride to browser rendering.
Checkout the developer Q&A
Another big news today was the that Firefox and Samsung is developing their own nextgen rendering engine Servo. Samsung announced earlier that they are going to switch focus from Android to their own smartphone OS Bada, I think that will be difficult for Samsung, look at HP and Web OS.
Facebook also announced an Android facebook takeover application that will take over your phone with Home. It will replace homescreen, dialer and messaging app in your android phone with Facebook Home.
I got a strange error today. I loaded some data using Ajax from a Domino view.
Looped thru the data and did some addition with the numbers. Nothing strange with this and
this code have been in production for a long time.
This code stopped working in IE9 both with and without compability mode. The code worked in Chrome and Firefox. If I ran the code using the IE9 debugger it also worked. But in IE9 it started to display the last parttot in the tot variable.
Strange or what???
It gets more strange. I changed the code to