corenominal

Full stack web developer, interested in all the things, but especially the web, code, design, Linux, OS X, PHP, WordPress, JavaScript & robots.

Tagged: chrome

The day Google Chrome disables HTTP/2 for nearly everyone: May 31st, 2016 image/svg+xml

According to this post, it looks like Ubuntu 16.04 LTS is one of the only Linux distributions that ships an OpenSSL package that is compatible with Chrome’s new negotiation protocol. My servers are still running Ubuntu 14.04 LTS and I had planned on keeping it for another 24 months, but if the details in this post are correct, I’ll probably be upgrading very soon.

Login Forms over HTTPS, Please image/svg+xml

In Firefox 46 Developer Edition, we display a prominent warning to developers about this risk.  When a page with a password field is not delivered securely, Firefox displays a lock with a red strikethrough in the address bar.

Seems like a waste to restrict this to the Developer Edition, I think Mozilla should follow Google’s lead and highlight all non HTTPS enabled sites.

New iPad And Web Browsers On iOS

A belated Merry Christmas to you. This year, Becky (my wife) gifted me a new iPad Air 2, it was a wonderful and totally unexpected surprise. I’ve never owned an iPad before, I’ve owned an Android tablet and I’ve used a lot of Android tablets at work (where I develop apps for them), but this is the first time I’ve used an iPad for longer than a minute or two at the local Apple store.

The iPad Air 2 is a fantastic device. IMHO, it’s far superior to any of the Android devices I’ve used. The retina display is just beautiful, and compared to Android, iOS is silky-smooth and a joy to use. In case you can’t tell, I’m really pleased with it. Thank you Becky :)

Anyhow, I’m not writing about my gift to post a review of the device, but just to note some initial observations.

First observation: browser rendering

I’ve been using the device to browse the web, using both Safari and Google Chrome. One of the first sites that I visited was this one (narcissism FTW) and I quickly found out that my technique of detecting the browser’s scroll position and applying various CSS rules depending on said position is totally broken. It works with all browsers on all OS’s on desktops, but it does not work on iOS.

Crap.

So, I spent a little while fixing it for Safari, only to find that it was still broken in Chrome. This was somewhat frustrating and I attempted a number of different approaches to solve the problem, but the more I fiddled with it, the more unhappy I became with the fugly hacks I was applying. In the end, I decided that the best solution would be to scrap the technique altogether and remove it from my design. Sometimes the most elegant solution to a problem is to remove the problem.

I will no doubt revisit this in the New Year, also, it’s a good lesson learned; I need to test my designs more, on more devices.

Second observation: doodling

The iPad Air 2 is a fantastic doodling device :)

A doodle of a robot in space.

A doodle of a robot in space.