New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Forum should never show mobile mode on desktop #38
Comments
How do I bump the priority of this? This is far and away the most important bug right now. |
I remember that we determined you could get the desktop view by increasing the width of your browser window by 3 pixels. 😆 |
And I told you immediately afterwards that that window width is too wide for comfortable reading of paragraphs. |
Whatever. Let's fix the bug now. |
See the second answer. You can add a property to media queries to "ignore" them for a specific class, then simply add that class to the BODY tag of the page. The "brilliant geniuses" at the W3C neglected to provide a "disabled" property on the CSSMediaRule type, otherwise you could solve this in JS without even touching the CSS. |
This bug should be taken seriously, because even on a Full HD screen it's showing the mobile version of the composer when the window is snapped side to side, which is a very common and useful thing to do on a large monitor. |
This issue has been addressed on the TDWTF forums with the Unresponsive plugin. On your avatar menu you should have a "Desktop Mode" entry that will change the way the site works. Note that this is not compatible with custom skins, however. This doesn't apply to front page comments, to my knowledge. You'd have to ask @BenLubar about that. |
Yeah, the front page comment form isn't "responsive". |
Steps to reproduce:
Expected results:
You get the desktop edit experience, including preview window, ability to multi-quote other posters, etc.
Actual results:
You get the mobile edit experience, which has no preview window, no ability to multiple quote, does not report errors when post fails, does not save drafts, etc. etc. etc.
The text was updated successfully, but these errors were encountered: