pjp wrote:It doesn't scale to the size of the device. A lot of UI elements take up a fixed amount of space that may look fine on a larger screen, but on a phone or ~7" tablet, they become visibly unusable (at least from a practical standpoint if not a literal one).
I concur, fixed dimension elements would be a problem on a smaller screen. However, I think the answer to those is to have the CSS specify responsive positioning, so that the browser can reflow elements as needed to make things fit. My concern with the original request is that I read it as a request for a parallel site, designed specifically for mobile, and stripped/modified as needed for that sole purpose. In my opinion, mobile browsers ought to be able to consume the same site as desktop browsers, aside from the concern you raised about fixed dimension elements that require extensive scrolling.
As I understand CSS and responsive design, it's possible, although sadly not nearly popular enough, to write the CSS such that users with laptop-or-bigger display area get full use of their screen, and users on tiny mobile screens get something that works as well as can be expected - and all without needing special Javascript to generate the pages dynamically.
pjp wrote:However, I have no idea how mobile users expect to be able to interact with code tags, even if they have the awful embedded horizontal scrolling window.
I expect most mobile users won't be able to post the diagnostics we typically request, but they might be able to read the forum well enough to receive posted advice and apply it to try to repair a distressed Gentoo system.
pjp wrote:I can't imagine the requests for help from such limited devices (though I think I have seen some), and I can't imagine how challenging it would be to try helping someone from a mobile device.
Agreed, it generally wouldn't work well. However, for respondents, it might be sufficient when the response can be to post a link to a page which describes the problem/solution in more detail, particularly when the user is requesting help with a known and previously reported bug. Similarly, given how often users fail to post standard files, such as the
build.log, respondents might find it feasible to use a mobile device to remind the user to follow Portage's instructions, so that by the time the respondent has access to a laptop/desktop to do more research and extended composition, the requester will have posted the information necessary to direct that research. (The alternative is that the respondent waits until laptop access just to remind the user to follow instructions, then has to wait hours or days more for the user to follow through, after which the respondent will finally have enough information to compose a meaningful response.)