Originally posted by Ericg
View Post
Announcement
Collapse
No announcement yet.
Google Forks WebKit As Blink Rendering Engine
Collapse
X
-
-
When Opera switched to WebKit I was bummed (monoculture, Chrome+skin, abandoned Presto, etc) but thinking that at least they got WebKit and this might be a good this in the end felt right. But now... daaam
also http://prng.net/blink-faq.html
Leave a comment:
-
Originally posted by Ericg View PostI wonder if Apple has a rule that browsers on iOS HAVE TO use Webkit as their engine
Leave a comment:
-
This seems silly to me considering that Chrome on iOS will continue to use Webkit according to people in #blink on freenode.
Leave a comment:
-
Was about f'ing time. Many Chromium bug reports were closed as upstream WebKit problems, with Google unable to do anything about them. It was getting ridiculous.
Leave a comment:
-
Originally posted by archibald View PostThey aren't going to have a prefix. If something's not ready then they're going to hide it behind an "enable experimental features" button, but it will always use the non-prefixed form.
Leave a comment:
-
My first thought is that hopefully they can get rid of the absolutely TERRIBLE performance problems, but then I realized that other khtml browsers are actually fast, so its not the rendering engine at fault.
In other words... who the hell cares? Chrome is going to remain a complete turd.
Leave a comment:
-
Fingerprint
Originally posted by AJenbo View PostGlad it is dead, this made me ban Safari as a web browser in an all Mac environment because of how badly it behaved with WYSIWYG. Back then Safari also had a tendency to crash when undoing or just randomly.
- It was like a fingerprint.
Leave a comment:
-
My first thought:
Don?t blink.
Blink and you?re dead.
Don?t turn your back.
Don?t look away.
And don?t blink.
Leave a comment:
Leave a comment: