karan

put it another way; in the case of open source software, you are selling service, not product. What you’re selling is the time you put in to make this theme.

Only obvious breakage with Firefox 1.0.4/Win is the calendar’s title being stuck to the left of the column while the rest of the sidebar is nicely padded. The Go button for the search doesn’t look like button – usuability issue, possibly.

Looks like a nice blog ?? hope you have a nice time with it.

just a suggestion, sheesh.

It just makes more sense to me to not bother with the Firefox buttons in Firefox. It just bugs me to see it over and over when I already have it. Think of a typical user – “ok I got firefox, now what? they’re still telling me to get firefox! What’s the point, it’s no different.” It’s different to the iPod billboard because we can do something about this, as opposed to the billboard. I’d love a billboard to looked to me as an ipod owner, “Hey cool you got an iPod. Here’s some stuff you can buy for it now!”

And obviously people have a difference of opinion regarding the use of browser-specific code. Doesn’t bother me, honestly, if it subtly alters the experience as necessary – how is this any different to the CSS box model hacks? Not much. Someone, give me a convincing argument against it (like “It’s not XHTML Valid” or “It still shows in Broswer Y when it shouldn’t” or “it breaks accessability guidelines”) and I’ll not use it.

Kafkaesqui, I was offering this as a more general suggestion than just the admin pages.

macmanx, it’s simply not necessary. you wouldn’t go to convert Christians to Christianity; why bother pushing Firefox to Firefoxians?

notthatugly, it’s not javascript, it’s just a HTML comment modified so IE interprets it.

confirming this as an issue in the 7/9 build too, I think it’s the install script not creating a ‘user_description’ column in wp_users table of the database. the mysql command

alter table wp_users add user_description varchar(255);

worked for me, though not everyone can run those commands… Once you add that, there’s no problems.

I played around with that but I couldn’t get it to work with WP 1.2, until I started digging into the actual function code…
this is what works for me:

<form name="archiveform" action="">
<select name="archive_chrono" onchange="window.location = (document.forms.archiveform.archive_chrono[document.forms.archiveform.archive_chrono.selectedIndex].value);">
<option value=''>By Month</option>
<?php wp_get_archives('format=option'); ?>
</select>
</form>