>>It's a standard speed-dial interface from the blank homepage. I click on it to go
>>straight to the UT link rather than typing it in or selecting from a bookmark.
>So, basically, if you would have typed it, it would result in the same. Is that correct?

Yes.


>So, with that device, you cannot even access the home page. Is that correct?

I cannot go there with Dolphin JetPack. With normal Dolphin it works fine. And since it reboots rather than just force closes, I assume it's an error in the install itself. It reboots on any attempts to access any websites, not just UT.

With Firefox and all versions of Opera, it did not work properly.

See screenshots:
http://www.libsf.org/ut/chrome_incompatible.png

http://www.libsf.org/ut/firefox_ut_homepage.png
http://www.libsf.org/ut/firefox.png

http://www.libsf.org/ut/opera_beta_homepage.png
http://www.libsf.org/ut/opera_beta_initial_landing.png
http://www.libsf.org/ut/opera_beta_after_pinch_zoom_and_scroll.png
http://www.libsf.org/ut/opera_beta_after_pzas_input_box.png

http://www.libsf.org/ut/opera_mini_ut_homepage.png
http://www.libsf.org/ut/opera_mini_initial_landing.png


>If yes to both situations, the device mobile browser in used really don't like the
>HTML5 doctype declaration.

I don't know. Dolphin is pretty popular. It works on most everything else. I know UT uses variable sizing for its page width rather than enforcing a minimum. I think that's the cause of these issues. The original screen is viewed on a 480x848 page, which presents an atypical width for a webpage were the screen's size itself to be used (or some multiple thereof due to zooming). Maybe it should have a fixed minimum which would then enforce things to be at least at that width, allowing Dolphin to work from within those minimum specs and on up depending on zoom level. Maybe it already does and I missed it.