>>That's one of the features of Dolphin (and presumably other mobile browsers). When you double-tap to zoom in using Dolphin, it reformats the text so it's only displayed as wide as the screen is when using a normal, readable-sized font. This is true of all web-content no matter the source. The mobile browser compensates for the small screen by providing this ability outside of the website's knowledge or ability to do this itself. This feature then also removes the issue of having any issue of the 10s panel overlaying the content area when reading (as I can't read zoomed out anyway, the font point is too small on my phone).
>
>So, based on what I read, you seem to get an advantage using Dolphin that other mobile devices don't have.

I don't know what other browsers have. But I do know that I don't have issues with Dolphin on most sites. I have a few issues with its handler of input boxes. Sometimes the flashing caret is off the screen and the only way I can see what I'm typing in is to look in the word-suggestion area as I type. Doesn't happen all the time though. The new UT site actually fixed that issue, but introduced a new one where once I press "reply" it scrolls too far down so that I have to manually scroll the text back down about 6 or 7 lines to see the caret again, and then touch the input box to put focus there.

It's why the whole concept of the web+browser as it is today needs to be completely thrown out. There are far better ways to convey data with explicitly desired formats than to go through this complex cascade-style rendering system employed by legacy ideologies. The Liberty Software Foundation will author this (if I ever get the time).


>>I am, but I don't need those for general use. And if I do need to see all of the buttons, I just click on the message number link to open in another tab and it's free from 10s panel intrusiveness, with all buttons shown.
>>
>>UPDATE: Well ... after posting the above I looked and realized you've taken that link ability away at the message level. We can only now click on the thread ID number and not the individual message number. So, there's another issue. The workaround is to copy the thread-level link, and then alter the message Id. It seems to work that way, but is obtuse.
>
>The Universal Thread is a contained environment. As soon as you move out a link from it, you might and can loose the ability to several options. This is not tested as I have a lot of options that are dependant of the container.


FWIW, it always worked in the old site. I used it often in Dolphin because of this very 10s panel issue. It would do some weird things though from time to time. The other window only seemed to have a correct scope so long as I opened the other window, did my thing, and then closed it. If I tried navigating in the meantime it caused an issue, or would someday update the content in the other tab, rather than in the current window. Just odd stuff.