Jennifer Grucza

Well last night at around 11pm, we at DigitalAdvisor launched a new version of the site! The look and feel has totally changed, and we now have a new feature: Questions and Answers. We’re hoping that it will help people in their research of electronics they’re thinking of buying (or already own, for that matter). And if you help other people out by answering their questions, you can get points and recognition.

Even though I’m not a graphic designer by any means, I’m the closest we have, so most of the work on the look and feel is my doing (with plenty of input from the rest of the company, of course). The layout on some of the pages is not final, and there are plenty of improvements that can be made (there’s more functionality coming, too). But I’m still pretty happy with how it looks.

Go check it out, maybe even ask or answer a question yourself!

Garcia’s Pizza

Jarling’s Custard Cup (see definition of frozen custard)

Steak & Shake

Dinner: grilled pork chops with brown sugar barbeque sauce, onions, and zucchini.

Dessert: peaches and blueberries with sugar.

The zucchini and peaches I got from the Cambridgeport Farmers Market today while I was out biking.

It drives me nuts when people use the word “interweb“. It’s “web” or “internet”, people! Pick one!

Even writers you think would know better use it. And if they’re just being ironic, well they’re being a bit to subtle about it.

Today I was wracking my brain, trying to figure out why Internet Explorer wasn’t respecting some of the rules in my CSS file. It finally occurred to me that perhaps it was getting tripped up by the attribute selectors I had grouped into the same rule. IE, of course, doesn’t understand attribute selectors. But I thought it would safely ignore these and apply the properties to the other selectors in the group. Here is what I had:

input[type="text"],
input[type="password"],
input[type="file"],
textarea,
select,
.reply,
.viewQuestion #yourAnswer {
    border-color: #ccc;
}

IE was ignoring the gray border I wanted for these elements. It seems stupid to me that it would throw out the whole rule instead of merely ignoring the selectors it didn’t understand and applying the rule to those it did. But it turns out this behavior exactly follows what is in the CSS 2 spec!

To fix my problem, I split my rule into two - one with the attribute selectors, and one without. Not terribly elegant, but the spec doesn’t really leave much choice.