type http://w3 into the URL widget, hit return, and watch it loop.

It turns out this is content bug on http://w3. I've notified them of the problem and am awaiting a response. Once they've resolved the issue I'll close this bug. The problem is that, because we don't support some of the javascript in the page, we get kicked into parsing the normal html which contains a meta http-equiv refresh tag which is malformed. When we get a malformed refresh tag, we refresh to the original url.

setting component field

The w3 content guys resolved the content issue. The looping no longer occurs. However, this has given rise to a new crashing bug, #745.

it stopped looping, but the content looks all messed up for this page.. I'm filing a separate bug on this page...

This looping bug still occurs at: https://apps.facebook.com/uab_app/