Tag Archives: Chrome

Farewell, Xmarks Bookmark Sync!

It’s not a huge surprise, with all the major web browsers adding their own bookmark sync services, but Xmarks (formerly Foxmarks) is shutting down in January.

I figure I’ll just use Firefox Sync, Chrome sync, Opera Link, etc. to share bookmarks between the desktop and laptop, but what I really liked Xmarks for was its ability to sync different browsers together. I’m always switching between Chrome, Firefox, Opera and Safari (and occasionally IE when I’m on a Windows box) and it’s nice to have them all on the same set of bookmarks.

I guess it’s back to periodically exporting from my main browser and importing in the secondary ones, unless I find a tool or find the time to read up on the bookmarks formats and write one.

Posted in Browsers | Tagged , , , , , | 3 Comments

Check Your Plugins!

We can check your plugins and stuff

It’s a safe bet that your web browser uses at least one plugin, and probably several. Maybe it’s just Flash for viewing animations and video (think YouTube and Hulu). Maybe it’s Silverlight for watching Netflix, or Shockwave for playing games. You’ve probably got Java installed.

Just like your web browser, these plugins must be kept up to date or you’ll run into problems: missing features, instability, or (worst case) security vulnerabilities. Unfortunately, most plugins don’t update themselves.

Several months ago, Mozilla introduced a service called Plugin Check that will identify the plugins you have installed and tell you whether they need to be updated — and how to do it. At first it only worked on Firefox, but now it’s been expanded to all major browsers: Chrome, Safari, Opera, and even Internet Explorer.

It’s worth taking a few moments to check. Think of it as a pit stop for your computer’s web browser.

Posted in Browsers | Tagged , , , , , , , | Leave a comment

Webkit display:table-cell Problem

I recently tried to retrofit a mobile layout onto an old table-based site using CSS. It was a fairly simple layout: A banner across the top, two columns, and a footer. I figured I’d use CSS to “unwrap” the table and make the sidebar and main content area into full-width sections instead of side-by-side columns.

In theory this should be simple: CSS handles tables by using the display property and assigning it table, table-row and table-cell for the <table>, <tr> and <td> elements. You can assign these properties to other elements and make them act as tables, or you can assign block or inline to these elements and make the table act like a series of paragraphs.

Initial testing worked perfectly in Firefox 3.6 and Opera 10.5x. Internet Explorer 8, as expected, ignored the changes entirely. Chrome, however, did something very strange, and Safari reacted the same way: The banner shrank, and the columns changed from a narrow sidebar to a 50/50 split…making it actually worse for small screens.

Clearly WebKit didn’t like something I was doing. Unfortunately, WebKit powers the exact platforms I was targeting: the iPhone and Android!

I dug around with the developer tools a bit to see if I could figure out what was going on. Was the browser not applying the property? Were the table cells inheriting the “original” property from somewhere else? Did I need to change properties on thead and tbody as well?

What I found was that WebKit did recognize the display:block I had added, but somehow the computed style was reverting to display:table-cell. This only applied to table and td, though. Table rows actually did what I told them to, which was why the result ended up looking bizarre.

If it hadn’t changed anything, I probably would have chalked it up to the capability just not being implemented yet. But since it worked on table rows, but not on cells, I decided to treat it as a bug in WebKit and went looking for the best way to report it. I ended up creating a WebKit Bugzilla account and reporting it as bug 38527.

Check out the testcase
in Firefox 3.6 or Opera 10.5 to see what it should look like, then take a look in Chrome 4 or 5 or Safari 4.

Posted in Web Design | Tagged , , , , , , , | 5 Comments

Browse-o-Smart

After a week of playing with Chrome as my main browser, I’m back to Firefox. Chrome’s fast, but sometimes too much like Breathe-o-Smart.

Me: Why won’t you show me the full (relatively long) URL of this link?

Chrome: You won’t want to look at the full URL with Chrome!

Me: But what if I do?

Chrome: Trust me, you won’t. You’ll never need a URL again.

Me: But what if I need to look at it just this once?

Chrome: Well, I suppose you could actually follow the link. Or copy it and paste it into a text editor. If you really must have the URL. Not that you’d want to, of course.

Me: Why should I have to do that just to look at a URL? *headdesk*

Posted in Browsers | Tagged , | Leave a comment

Getting Flash to work on Google Chrome for 64-bit Linux

I tried out the Chrome beta for Linux on two different computers yesterday. On the first one, Flash worked right “out of the box.” On the second, it wouldn’t even show up in about:plugins. I couldn’t figure out what was different.

  • Both are 64-bit systems running Fedora 12.
  • Both are running the 32-bit version of Flash from Adobe’s yum repository.
  • Both are running the 64-bit version of Google Chrome from the beta download page.
  • I had run mozilla-plugin-config -i to create the 64-bit wrapper on both computers after updating Flash. (A security update came out yesterday.)
  • Flash works just fine in 64-bit Firefox and Opera.

I looked thoroughly at my home computer last night and came up empty. This morning I took another look at my work computer — the one where Flash actually showed up — and I think I’ve found it.

Chrome is using nswrapper_32_64.libflashplayer.so according to about:plugins. The actual file is in /usr/lib64/mozilla/plugins-wrapped/. This system has two symbolic links to that file, one in /usr/lib/mozilla/plugins/ and one in /usr/lib/mozilla/plugins-wrapped/. IIRC Only one of these was present on my home computer.

So I think this will fix it:

ln -s /usr/lib64/mozilla/plugins-wrapped/nswrapper_32_64.libflashplayer.so /usr/lib/mozilla/plugins/

Run the command as root or using sudo.

I’ll check back tonight and update this entry to show whether it worked.

Update: Yes, it worked!

Posted in Computers/Internet, Troubleshooting | Tagged , , , , | 21 Comments

Updating…

  • Google Chrome beta on Linux seems to work well so far, though the Xmarks-for-Chrome beta mangled my bookmarks. Yay for backups. #
  • Busy download day: patches, Thunderbird 3, Chrome extensions, Chrome for Mac/Linux… #
  • It’s time to update Flash (and AIR) on your computer — Adobe’s released a security fix #

Posted in Computers/Internet | Tagged , , , , | Leave a comment

Windows 7 Chart, Opera for Android, Chrome

Posted in Computers/Internet | Tagged , , , , , | Leave a comment

The Network PC Returns

So if I’ve got this right, Google Chrome OS is essentially booting your computer directly to a web browser? Thin clients really are back. #

Posted in Computers/Internet | Tagged , , , , | Leave a comment

Upgrading the Web: IE8 Released

Internet Explorer.Microsoft released Internet Explorer 8 yesterday, for Windows XP and Vista. So if you’re still running IE6 it’s once again time to think about upgrading. (Assuming, of course, that you’re not locked in by corporate policy or another piece of software.)

IE6 is now two versions behind the current release.

IE6 is almost 8 years old (it was released in 2001).

IE6 is lacking in many capabilities that all other modern web browsers have, in web technology, in security, and in features you can use.

You can read a review at Wired, a write-up from the IE team, or a summary of technical changes from WaSP.

Of course, Internet Explorer isn’t the only option out there. There’s Firefox, Opera, Chrome and a host of other alternative browsers that are worth checking out.

If you’re still running Windows 2000 or some other old version of Windows that can’t run IE7 or IE8, I’d absolutely recommend Firefox or Opera. Either will be much better than IE6, both will run on Windows 2000, and Opera will even run on Windows Me and Windows 98 (but you really ought to move to something more current than Windows Me.)

[Opera Logo] [Chrome Logo] [Firefox Logo]

Posted in Browsers | Tagged , , , , , , , | 1 Comment

First Impressions of Google Chrome

Now that it’s live, I’ve downloaded the Google Chrome beta on my Windows box at work.  Thoughts so far:

Good:

  • Site compatibility seems to be fine so far, with a couple of minor issues (see the “Bad” section).  Mostly I’ve tested it with a couple of forum sites, LiveJournal, Slashdot, and WordPress.
  • I like the simple settings box, with “Basics,” “Minor Tweaks,” and “Under the Hood.”
  • It does feel fast.
  • Showing the URL of links in the lower left-hand corner is a perfect compromise between the spatial advantages of a permanent status bar and the extra room provided by leaving it out.
  • I like the task manager for the browser itself.  It’ll be good for developers, but it’ll also be good for users: as the comic points out, if your browser starts chewing up all available resources, you’ll be able to tell what page/plugin/program is at fault instead of just blaming the browser.

Bad:

  • Gears support doesn’t seem to work quite right.  WordPress.com doesn’t detect that it’s available.  Local WP installs with Bad Behavior can’t sync completely.  (It doesn’t send an Accept header on the request for one of the TinyMCE files, which causes Bad Bahavior to think it’s a spambot and triggers a 403.)
  • Cookie management is too simplistic.  I like to accept all cookies temporarily, but clear everything when I end my browsing session, with exceptions for sites where I want to stay logged in.  This is easy in Firefox, a little trickier in Opera, and doesn’t seem to be an option in Chrome.
  • I have seen it pause a couple of times, with as few as 5 tabs. [edit: these seem to be related to Flash content]
  • No Incomplete spell-check.
  • I keep hitting the forward-slash key to search within a page, since that’s the shortcut I’m used to in Firefox and Opera.
Debatable:
  • The UI does indeed stay out of your way.  I guess this sort of makes Chrome the Anti-Flock.
  • DNS Pre-Fetching is enabled by default.  This is different from full HTTP pre-fetching in that all it does it look up the IP addresses of the links that you might click on.  It’s not clear at what point it does this — I don’t remember seeing it mentioned in the comic, which (ironically) isn’t searchable.  I suppose it could either hit the domains of all the links on a page, or just those that would trigger HTTP pre-fetching, or even just send the query when you hover over a link (to get a split-second head start before you click). Update Sep. 17: Google has a blog post explaining pre-resolving in detail. Apparently it does check the domains for all the links on the current page.

Posted in Browsers | Tagged , , , | 12 Comments