Slashdot Mirror

← Back to Stories (view on slashdot.org)

Development, Privacy, and Standards for Chrome

Posted by Soulskill on from the chrome-chrome-chrome-chrome-chrome dept.

Continuing our coverage of Google Chrome, snydeq points out an Infoworld story about looking at the new browser from a developer's perspective, and another about how WebKit should be the focus of development efforts, rather than the browsers that use it. TGdaily notes that Chrome's search box will fetch all types of data, and can be made to display banking information with little effort. ABC and coderrr have slightly more paranoid articles questioning Google's commitment to privacy. NetworkWorld suggests that Chrome's unique process model (explained here) will require the development of new measurement standards.

4 of 114 comments (clear)

  1. Gears and the storage API by Simon+(S2) · · Score: 5, Insightful

    So google stripped the HTML 5 standard local storage api from Webkit to use their own implementation Google Gears. Why? The api was already there, and it worked, so they had to strip it out to go with google gears, their own, not w3c compliant. I think they are starting to become evil.

    --
    I just don't trust anything that bleeds for five days and doesn't die.
  2. Bug by The+MAZZTer · · Score: 3, Insightful

    Indexing of HTTPS pages is most certainly a bug. Did the poster of the article report it to make Google Chrome a better product or is he just going to complain? It's only in beta.

    And the work around is simple: Use Incognito mode for all sensitive work. Which is what it's for.

    1. Re:Bug by DancesWithBlowTorch · · Score: 4, Insightful

      It's only in beta.

      I don't accept this excuse from Google, because they have effectively destroyed the concept of a beta version. Even gmail is still in beta, and it's probably among the world's top three email providers now.

      Google, please do official releases of your products. Or, if you really need to childishly continue to call them development versions, invent a new category. Maybe, call them "gamma" versions. You are spoiling a useful metaphor for everyone else.

  3. Re:Completely good and noble by kestasjk · · Score: 4, Insightful

    I don't see why a rendering engine can't have security vulnerabilities, just like any other software which processes input from an untrusted source.

    --
    // MD_Update(&m,buf,j);