Page 2 of 2 FirstFirst 12
Results 11 to 20 of 20

Thread: Google Forks WebKit As Blink Rendering Engine

  1. #11
    Join Date
    Sep 2007
    Posts
    311

    Talking

    My first thought:

    Donít blink.
    Blink and youíre dead.
    Donít turn your back.
    Donít look away.
    And donít blink.

  2. #12
    Join Date
    Oct 2012
    Location
    Cologne, Germany
    Posts
    308

    Exclamation Fingerprint

    Quote Originally Posted by AJenbo View Post
    Glad 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.
    Even worse, when you copied formatted strings to external programs.
    - It was like a fingerprint.

  3. #13
    Join Date
    Oct 2009
    Posts
    2,081

    Default

    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.

  4. #14
    Join Date
    Sep 2011
    Posts
    683

    Default

    Quote Originally Posted by archibald View Post
    They 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.
    While this does actually mean that we can't stay compatible with older versions of the browser, i do agree that it's an overall better solution.

  5. #15
    Join Date
    Jul 2008
    Location
    Greece
    Posts
    3,788

    Default

    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.

  6. #16

    Default

    This seems silly to me considering that Chrome on iOS will continue to use Webkit according to people in #blink on freenode.

  7. #17
    Join Date
    Aug 2012
    Location
    Pennsylvania, United States
    Posts
    1,875

    Default

    Quote Originally Posted by ryao View Post
    This seems silly to me considering that Chrome on iOS will continue to use Webkit according to people in #blink on freenode.
    I wonder if Apple has a rule that browsers on iOS HAVE TO use Webkit as their engine

  8. #18
    Join Date
    Oct 2008
    Posts
    3,079

    Default

    Quote Originally Posted by Ericg View Post
    I wonder if Apple has a rule that browsers on iOS HAVE TO use Webkit as their engine
    They do - no browser engines except Webkit are allowed. Firefox's browser on iOS had to use Webkit too, for the same reason, and that's why they eventually just killed their port.

  9. #19
    Join Date
    Jun 2006
    Posts
    352

    Default

    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

  10. #20
    Join Date
    Sep 2011
    Posts
    683

    Default

    Quote Originally Posted by Ericg View Post
    I wonder if Apple has a rule that browsers on iOS HAVE TO use Webkit as their engine
    Not only that it will have to be the bulidin version, so no browser updates either. An when apple updates your content better be ready.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •