Naver Whale browser running outdated Chrome engine (update: fixed)

Update 2:
Whale has recently been pushing updated versions faster so this is not an issue anymore. I'll leave the post up for reference but it really is no longer accurate. Let's applaud Naver for keeping Whale secure and current.

Update 1:
It's September now, and Whale is up to v60 with Chrome at v61. Opera is at v58. Not bad!

---

I'm generally a fan of Naver's new browser Whale, especially since it's based on Chromium. I figured it would be quick to receive crucial security updates. But while fooling around last night I noticed that the browser engine is out of date.

Screen cap from Whale info page

Whale lists itself as up-to-date in the Whale info page (whale://about/) on Whale version 0.9.34.10 beta. Sounds good, I guess.  

But curiosity got to me and I checked a profiler site to see what data was publicly visible regarding the browser, which included the specific browser engine version: 58.0.3029.110

Whale browser engine version. Source.

The site also pointed out that this made my Chrome installation out of date, so checked the Chrome Release logs to see when that version was applicable. It was released (or at least, announced officially in a blog post for the stable channel release) on May 9, 2017. 

Chrome release post for that version. Source: Google

The most recent stable Chrome engine release, meanwhile, is (at time of this blog post) version 59.0.3071.115, listed as released June 26, 2017. 

Digging through the Whale Changelog release notes shows that version 58 of the Chromium engine was incorporated into Whale build 0.9.34.9 beta on June 29, 2017. 

Whale change log capture

So there were 52 days between the release of v58 and its incorporation to the Whale code. 

Meanwhile, it's been 23 days since the release of v59, but it's not been added as of this blog posting. 

Now don't get excited. Please note that this is just to inform you, the potential user. Security patches are pushed out all the time, and 50 days is pretty good compared to using IE 11. And note that the other big Chromium-sourced browser, Opera, is also still running engine 58 in its latest version (v45). This is not a huge security issue for the average user, but something to bear in mind. Plus Whale is still in beta anyway.

For me, Whale's biggest problem is that by default, mouse middle-clicks open in the split-screen Whale "Spaces" thing instead of a new tab. Click behavior inside Spaces is unpredictable too, or else I'm too stupid to figure out the logic behind it. Maybe a little of both.