Currently, the WebHUD window works as any other browser. In
particular, when it receives a redirect request, it follows it. This
is probably not desirable, because the tabs of the WebHUD correspond
to some URL and the redirect violates this principle.
I propose this:
When a redirect comes in, the main window (the parent of the WebHUD)
is redirected.
This allows a flow such as the following:
1) User clicks the "add" tab
2) User selects a content-type, fills out the "properties" form (with
title and description, needed to generate an id) and hits "Save".
3) The system redirects to the view of the new content object.
Hence, with the proposed change, (3) will have the affect of the main
browser window reloading, which will refresh the WebHUD tabs. This
makes a lot of sense. Note that for non-WebHUD enabled browsers, e.g.
Firefox, it makes sense, too.
Of course, this mainly concerns Stefan, who implemented the WebHUD plugin.
\malthe