Updating Flash Player Manually on Chrome for OS X

Recently (late November), Adobe finally got around to releasing an update to Flash Player for OS X that comes with the long-awaited hardware-based rendering of H.264-encoded videos. However, for those of us that use Chrome, there is no way to updated to the latest 10.2 beta of Flash; Chrome uses its own copy of Flash that comes built-in and cannot be externally updated. These steps below will guide you through the process of using Flash Player 10.2 with Google Chrome on OS X:

Continue reading

Chrome’s Coolest Feature: File Upload Progress Indicator

Google Chrome 4.0 went live a couple of weeks ago, and it has a feature that’s been missing in most mainstream browsers ever since the Web was invented: a progress bar that actually shows, well, the progress of uploads. It’s really frustrating to be uploading a large file to a website or as an attachment to an email or forum post and not know whether or not it’s taking this long because it’s just slow or because it’s really stuck.

Chrome 4.0 now shows the status of file uploads as a percentage, making it very clear just how quickly (or not) your uploads are progressing – and it’s something that all browsers should add ASAP. Many social websites rely heavily on uploads of photos, videos, music, and other files and are forced to implement nasty workarounds (such as using Flash upload forms) to present a more user-friendly upload system.

Continue reading

Does it GTK/QT/Win32 Really Matter for Chrome?

128px-GoogleChromeLogo.pngA recent article on OSNews highlights the changes expected to come in Google’s Chrome 2.0 for Windows and the progress being made on the Linux and OS X fronts for Google’s new browser.

In the article, Ben Goodger, lead Chrome UI developer, states

[Google avoids] cross platform UI toolkits because while they may offer what superficially appears to be a quick path to native looking UI on a variety of target platforms, once you go a bit deeper it turns out to be a bit more problematic.” [... Your applications end up] speaking with a foreign accent.

But there’s something we’re not getting here. Obviously given enough brilliant programmers and a good team lead to keep the different codebases in sync, going with native APIs is the better approach. But the reasons Goodger is offering aren’t very convincing.

Continue reading