Ketika Windows Phone dikira Android

Mulai sejak Windows Phone 8.1 U1, Internet Explorer 11 akan mengikutkan string iOS 7 dan Android 4.0 ke User Agent-nya. Tujuannya, agar pengguna IE11 di Windows Phone dapat menikmati fitur-fitur HTML5 secara penuh, seperti teman-teman lainnya.

Ini contoh User Agent-nya (dikutip dari WMPoweruser):

Mozilla/5.0 (Mobile; Windows Phone 8.1; Android 4.0; ARM; Trident/7.0; Touch; rv:11.0; IEMobile/11.0; NOKIA; Lumia 930) like iPhone OS 7_0_3 Mac OS X AppleWebKit/537 (KHTML, like Gecko) Mobile Safari/537

Kabar baiknya, pengguna Windows Phone bisa mendapatkan tampilan atau UX yang sama dengan pengguna iOS/Android atau browser lainnya. Berita kurang baiknya, jangan kaget kalau saat browsing, muncul pop-up atau pesan/iklan seperti pada gambar di bawah ini…

Windows Phone browser

Tips: Kalau ditawari untuk menginstall antivirus Android, abaikan saja ya 😉

Pretended to be iPhone

IE11 with WIndows Phone update

Internet Explorer (IE 11) di Windows Phone (versi 8.1) terpaksa harus “berpura-pura” (spoofing) menjadi iPhone (melalui string User Agent) agar penggunanya bisa mendapatkan pengalaman browsing yang setara dengan pengguna browser lainnya, yang sebagian besar berbasis WebKit.

Dikutip dari IEBlog:

We updated the User Agent string in IE on Windows Phone to increase the number of sites that would correctly deliver the best mobile content. This continues an unfortunate pattern that all browsers have had to deal with and most web developers have run into.

Sedikit ironis sih menurut saya. Dulunya browser-browser lain yang spoofing User Agent-nya ke IE karena saking populernya IE waktu itu, sekarang malah IE yang spoofing.

Google forked WebKit into Blink. What does that mean?

Krzysztof Kowalczyk:

Apple is in a tight spot. Suddenly WebKit will be getting 50% less code.That’s a big drop.

Which is why Apple is in a tight spot: if WebKit suddenly looses non-Apple contributions, they’ll have a hard time catching up with Blink. And while they really don’t care if web technologies advance quickly, they’ll be forced to at least keep pace with Mozilla and Google, both of which are putting the foot on the pedal recently.

Google forks WebKit, calls it Blink

Blink

However, Chromium uses a different multi-process architecture than other WebKit-based browsers, and supporting multiple architectures over the years has led to increasing complexity for both the WebKit and Chromium projects. This has slowed down the collective pace of innovation – so today, we are introducing Blink, a new open source rendering engine based on WebKit.

And thus Chrome now uses Blink, which is forked from WebKit, and pretended to be Safari, and WebKit pretended to be KHTML, and KHTML pretended to be Gecko, and all browsers pretended to be Mozilla.

John Resig: WebKit adalah jQuery dari browser

Berita mengenai Opera yang beralih ke WebKit mendapat perhatian dari John Resig, pembuat jQuery, the missing JavaScript library. John Resig berpendapat bahwa WebKit bagi browser layaknya jQuery bagi JavaScript.

I would argue that WebKit (a common framework for implementing the standards-compatible portion of a web browser) is exactly like jQuery (a common framework for implementing a DOM standards-compatible experience in a web page) at this point.

John Resig

Selain itu, John Resig juga mengomentari beberapa argumen terkait masalah WebKit dan web standar. Misalnya, tentang stagnasi, dan masalah bug yang bisa menjadi de facto.

As to the bugs: WebKit is a common code base that a number of browsers contribute to, however every browser vendor has the ability to make changes to their own fork of the code base. I see no reason why these “now-standard” WebKit bugs wouldn’t be fixed by any single vendor.

Anda bisa membacanya secara lengkap dari blog John Resig.

“Sad day for the Web”

The news about Opera switching to Webkit is disappointing. It’s a sad day for the Web, since I thought highly of their Presto engine and their Web standards work. Their impact on Web standards will be dramatically reduced, especially where they want to do something differently to Apple and Google.

Robert O’Callahan

-o-pera beralih ke -webkit-

WebKit

Opera mengumumkan bahwa saat ini pengguna browser Opera telah berjumlah sekitar 300 juta orang.

Namun saya tidak peduli dengan jumlah tersebut, berita yang lebih penting dari pengumunan tersebut adalah Opera akan beralih ke WebKit 🙂

On the same day as announcing that Opera has 300 million users, we’re also announcing that for all new products Opera will use WebKit as its rendering engine and V8 as its JavaScript engine. It’s built using the open-source Chromium browser as one of its components.

Seperti yang diungkapkan di blognya, produk Opera berikutnya akan menggunakan WebKit sebagai rendering engine dan V8 sebagai JavaScript engine-nya. Spec seperti ini memang mirip dengan yang digunakan pada Google Chrome karena pada dasarnya komponen tersebut dikembangkan dan digunakan pada Chromium, proyek open source dari Google Chrome milik Google.
Continue reading “-o-pera beralih ke -webkit-“

Why other browsers have “Mozilla” in the User Agent

Inilah sejarahnya mengapa di setiap browser punya User Agent yang ada “Mozilla”-nya:

And then Google built Chrome, and Chrome used Webkit, and it was like Safari, and wanted pages built for Safari, and so pretended to be Safari. And thus Chrome used WebKit, and pretended to be Safari, and WebKit pretended to be KHTML, and KHTML pretended to be Gecko, and all browsers pretended to be Mozilla, and Chrome called itself Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/525.13 (KHTML, like Gecko) Chrome/0.2.149.27 Safari/525.13, and the user agent string was a complete mess, and near useless, and everyone pretended to be everyone else, and confusion abounded.