Just wanted to let you know that we've figured out what was causing that
problem. It actually turned out to not be the Browser widget at all, but
rather a piece of code we had that ran when the browser location began
changing. On every other platform this code works fine when you pass in
javascript, even though it's not really valid.