4 ms·

One thing to note is that when you think mobile, WebKit (Chrome, Safari, Android, iPhone) is already a dominant force. We don't know what our primary web brows

• masklinn 15y ago
  > One thing to note is that when you think mobile, WebKit (Chrome, Safari, Android, iPhone) is already a dominant force. Warning: there is no webkit[0] especially not on mobile[1]. While not completely true, it's important to remember three things about webkit: 1. The core engine progresses fast, and actual browser implementations fork the core, two webkit browsers may have very different capabilities and bugs due to the precise trunk revision they were forked from 2. Webkit relies on a number of abstract interfaces which are implemented differently on each port, depending on the quality of the port and the underlying platform's capabilities two webkits on two different platforms (or toolkits) may behave very differently 3. Webkit is an HTML/CSS rendering engine, javascript engines are built separately, which means (again) two webkit browsers may have very different behaviors and capabilities as far as JS and DOM go, and provide completely different sets of APIs. [0] http://ariya.blogspot.com/2011/06/your-webkit-port-is-special-just-like.html http://ariya.blogspot.com/2011/06/your-webkit-port-is-specia... [1] http://www.quirksmode.org/webkit_mobile.html http://www.quirksmode.org/webkit_mobile.html