Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
×
Google Software Technology

Google Quashes 13 Chrome Bugs, Adds PDF Viewer 177

CWmike writes "Google on Thursday patched 13 vulnerabilities in Chrome 8 (stable), and debuted Google's built-in PDF viewer, an alternative to the bug-plagued Adobe Reader plug-in, and included support for the still-not-launched Chrome Web Store. The 13 flaws fixed in Chrome 8.0.552.215 are in a variety of components, including the browser's history, its video indexing and the display of SVG (scalable vector graphics) animations. Next up: Adobe and Google have collaborated to put the Flash Player plug-in inside a sandbox within the dev build of Chrome, an effort by the two companies to better protect users from attacks."
This discussion has been archived. No new comments can be posted.

Google Quashes 13 Chrome Bugs, Adds PDF Viewer

Comments Filter:
  • PDF viewer (Score:5, Insightful)

    by hether ( 101201 ) on Friday December 03, 2010 @09:56PM (#34440454)

    "The viewer renders PDF documents as HTML-based pages"

    I hope it does a better job than the PDF viewer built into Google search...

  • Re:-13 +1 (Score:2, Insightful)

    by Anonymous Coward on Friday December 03, 2010 @10:03PM (#34440500)

    The problems with pdf security are either due to the latter standards that allow excusable to be imbedded or due to poor security in the adobe and apple readers. You never hear about evince or ocular being a security risk.

  • Re:Adobe (Score:5, Insightful)

    by Guillermito ( 187510 ) on Friday December 03, 2010 @10:23PM (#34440618) Homepage

    Adobe makes money with PDF authoring tools, not with reader. Since PDF is marketed as a universal format, I guess it is in Adobe's best interest for end users to have a seamless experience accessing PDF content in every possible platform.

  • by Zero__Kelvin ( 151819 ) on Friday December 03, 2010 @11:36PM (#34441018) Homepage
    Any website that warns about unsupported browsers is by definition designed by someone who doesn't know how to design websites. Properly designed websites follow standards, and web browsers comply with those standards. When a web developer speaks in terms of which browsers they do and don't support that is a direct indication that they don't understand even the most basic and fundamental concepts of website design.
  • by bogaboga ( 793279 ) on Friday December 03, 2010 @11:48PM (#34441108)

    ...and here's why:

    The fact that after all these releases, Google still does not see it prudent to had 'print preview' added to Chrome as one of its features.

    Folks, this feature is a killer for me...and I am not alone. Trust me on this.

  • Finally! (Score:4, Insightful)

    by 93 Escort Wagon ( 326346 ) on Friday December 03, 2010 @11:58PM (#34441150)

    I'm not a fan of PDF at all - but if you want to use a browser for work, decent PDF handling is a necessary evil. The old "solution" - pulling the PDF into Google Apps - couldn't handle PDF files accessed through https. That made it a non-starter in my work environment.

    All you young'uns are free to bitch and moan about PDF itself; but in the real world you usually have to be pragmatic.

It's a naive, domestic operating system without any breeding, but I think you'll be amused by its presumption.

Working...