Firefox has an interesting little “issue” (apparently not a bug) with firing the change event on dropdowns when using your keyboard instead of your mouse. I ran into this recently, as there were certain fields on a page which should hide or show based on the value of a dropdown. In all browsers except Firefox, they would show up immediately, but in Firefox they would show up only when the dropdown lost focus.

The initial fix I came up with was to attach a call to the change event on the keyup event of every select element on the page. This didn’t work, because the value hadn’t been saved yet.

My second fix, which I discovered here, was to call the blur event and the focus event. This seemed to work, but there were a few fields where calling blur had unintended side effects. This solution wouldn’t work for me either.

After thinking about it for a few more days, I came up with a solution. If you’ve run into this issue as well, here’s a bit of jQuery magic to make it work:

if (navigator.userAgent.indexOf("Firefox") > -1) {
    $(document).on("keyup", "select", function () {
        $(this).val($(this).find(":selected").val());
        $(this).change();
    });
}

Hopefully, this is useful to someone out there. I know it took me a long time to wrap my head around it.

The limitations I can see on it are if you don’t have all unique values, and you’re using the text values of the options to do your javascripting. If that’s the case, you can probably adjust this accordingly. The most important piece is the $(this).find(":selected") – even though Firefox doesn’t change the value of the dropdown, it does mark the option that’s been selected as such. That’s the bit I was really missing before.

Continue reading


From The Verge

Lastly, I am very curious to know how much HTC’s new status as the lead partner for Windows Phone played a part in sealing these negotiations, if at all. Apple and Microsoft have a very friendly patent relationship, and if HTC has decided to focus on Windows Phone instead of Android it could have certainly helped wrap things up. That’s total and complete speculation on my part, but it’s something to consider.

Speculation or not, it draws an interesting map for the next few years. If it turns out to be the case, phones could be swinging the opposite way they did when Windows basically destroyed the Mac. People don’t want bad phone hardware, so only the best make it – and the landscape we would end up with is 3 companies vying for their phone platform: Samsung with Android, HTC or Nokia with Windows Phone, and Apple with iOS. Of course, Windows Phone and Android will have other manufacturers, but so did the Mac OS at one point – they just weren’t hugely relevant.

It’ll be interesting to watch what HTC does. So far, based on reviews, the 8X seems like a nicer phone than Nokia is putting out there, camera notwithstanding. They might be onto something.

Continue reading


From The Verge

Twitter originally said that developers would have until January or March of 2013 to comply with the platform’s API changes, so Tweetro developers are questioning why their app has been cut off so early — especially when Twitter has yet to release its own official app for Windows 8.

It’s still strange to me that Twitter is doing such a crackdown, so it boggles my mind that they’ve started so early – it’s just a matter of time before MetroTwit and TweetBot follow the same fate.

Tweetro has reached out to Twitter to discuss the future of their app, and says it may pull the app from the Windows 8 store and re-launch with a paid app if Twitter does not agree to loosen its policy.

I do wonder if that would fall within Twitter’s policies – can you just relaunch your app once they shut it down?

I’ve finally gotten around to updating this site to be responsive – that was the plan from the start, but I simply never got around to it.

It’s still in the early stages, but I’m happy with it for the hour of work I put into it (much of which was spent figuring out best practices for responsiveness).

The design itself still seems to have some issues on iOS devices – the transition between pages, in particular, seems to cause some issues, and scrolling in the article viewer doesn’t ‘flick’ in the way that it should.

Go ahead and test it out – just resize your browser width to give it a whirl!

Any feedback can be sent to me @simon360.

Update: Noveber 11, 5:16 PST

I’m continuing to work on this – the site is now responsive on larger screens, opting for a sidebar to show a list of articles, and using the right side to display the full article selected.

Continue reading


This post started as a reaction to Joshua Topolsky’s piece on gadget fatigue, but it quickly spiralled into an editorial of my own. In fact, it ended up as something that was barely related to the original post at all. But I think it’s still an interesting thought.

We’ve all heard the word: fragmentation. Android users hate the idea of it. They deny it. But it still exists on some level, and it’s impossible to get around that reality. But it also exists on other platforms: the iPhone and iPad have started getting quite fragmented lately, with Apple disabling features on older handsets for no reason other than to move more hardware.

But it wasn’t always like this, nor does it need to stay this way.

Continue reading


For those of you who have read Apple’s Human Interface Guidelines for iOS, the following passage may seem familiar to you:

iOS applications should start as quickly as possible so that people can begin using them without delay. When starting, iOS apps should:

Display a launch image that closely resembles the first screen of the application. This practice decreases the perceived launch time of your application.

When I first read this, the idea made a lot of sense. If an application looks like it’s already loaded, then the device feels snappier. If I can “decrease the perceived launch time” of my application, my user’s will be impressed at how quickly my application seems to launch, and will be more likely to keep using it.

Except it doesn’t work.

Why? Well, take another read of the above paragraph.

See it?

The key to this idea is that it’s a trick. And like most tricks, this one grows old after you see it done too many times.

Continue reading