811

Rims.com Official Launch

Rims.com, your premier source for rims and tires

Rims.com, your premier source for rims and tires

As many of you know, I tend to work about 600 hours a week on my own projects, my blog being one of them. On Monday, February 23rd, we officially launched Rims.com, an online store selling custom rims and tires.

lasha

Lasha rocks.

Within the last week, we’ve had a ton of great feedback and even some promising sales numbers. In the coming weeks we will also be rolling out a stock rims store with over 20,000 products, so be sure to watch for that.

If you’d like to show your support for Rims.com and buy a sweet shirt, you can be almost as cool as Lasha with his sweet Rims.com shirt by visiting our CafePress store which has some awesome shirts, hoodies, mousepads, even a MinoHD camcorder! Yes, I know, you want one of those. So do I.

Comments have been disabled for this post.
Sort: Newest | Oldest

Hm, really weird that you still couldn't see it. Looks perfect now though!

Again, I like the clear fix over at quirksmode. I find myself very much in agreement with his views on CSS hacks/bug fixes/front end development.

Kevin, it's just another clearfix solution that avoids the usage of cluttery markup. I've removed it from the header, it wasn't even needed. I still can't see the problem, even after using FF 3.0.7. Is the issue resolved now?

Yeah I'm in FF 3.0.7 windows, try updating and you'll see :)

It's odd that it works fine on the home page, but breaks on the shopping pages. Changing .clearfix to display:block; fixes it, but might introduce problems for you in other browsers.

I'm curious though, what's the inline-block for? A quick google search only turned it up as a bugfix for the dead IE5/mac

Uh oh, in FF 3/win, on the shop pages (http://shop.rims.com/packages.asp), the header is "floating" to the left of the #container, due to display:inline-block; IE7 is fine.

I personally use overflow:hidden; for my float clearing needs http://www.quirksmode.org/css/clearing.html

Yes, it is something I have heard from a few people on FF 3.0.6 for Mac, but I could never see it in FF 3.0.6/Windows. I will definitely get it fixed soon even though not many visitors use Firefox. Issues in IE 6/7 take up the majority of my bugfixing time. Thanks for the heads-up though! Always appreciated!

Nice! But don't you mean 60 hours per week instead of 600? ;)

Good job with the site!