>>I'm not sure how much "enhancing" of the interface would be required. As I explained earlier:
>>
>>- when in a secondary tab, "View the map of this thread" respects the tab and behaves exactly as expected. This already works great.
>>
>>- why can the subsequently available "View" button not work the same way?
>
>I cannot consider investing time to support something out of the interface. If you have something to suggest within the interface, then I would be happy to consider implementing the required addition or change into the applications.

Well, in this instance, there are two, related issues.

My immediate request is for the "View [marked messages]" button to work similarly to the "View the map of this thread" button. If it were me, I'd compare the code behind the two buttons to see if anything could be quickly or easily done. Clearly you already have code that is known to work this way.

The larger question is full support for multi-tab or multi-window browsing, which as you point out could mean major architectural changes and expense. With the UT you already have one of the best interfaces for threaded discussions on the Web. You are converting it to .Net/SQL Server, which will make it (more) saleable to others. I'd argue that full support of multi-tabbed browsing, with modern browsers, would be a significant selling point.