I think Memo should consider small mobile devices as first class supported devices.
- No modals.
- A single scrollbar.
- Don't rely on hover effects.
Agree with all but "No Modals". An ajax request is sometimes beneficial to reloading the whole page.
One more for a truly mobile device friendly interface:
- Open links in the existing browser window.
Icon on external links, like Wikipedia. Desktop users know how to Ctrl+Click.
Great idea! Thanks for the suggestion.
Agree. I should have written ‘avoid modals’. The current design should be lightweight enough to just load new pages, and I consider that a superb feature of this site.
paper-thin apps featuring functionality: the future.
Wut ? There's no need for Ajax to unhide a hidden Form element ? The HTML is there, and it works fine when I tell Chrome to use desktop view.
I don't expect that all replies to a post are loaded when the post is first shown (on "New Posts"). The AJAX requests loads additional replies without the need to reload the BG feed.
Where talking different Views here...
I was refering to the reply button not working on Mobile.
As much as I hate it, Mobile should be the main focus.
When developing the site I try to use mobile view. Mobile first is definitely philosophy here. What issue do you have with the reply button on mobile?
Yes, agreed. Definitely a misunderstanding. @memo - Reply was broke on Desktop for a while today as well...don't think it was mobile-specific.
Thanks for letting us know. Yes we resolved it :) There was an issue where the icon in the button would ignore the event depending on how you clicked it.
BTW, just noticed "New Posts" is no longer linked anywhere... /post/new It's the landing page now, but the menu links to /posts/ranked....
New posts link is same place it was before. Can you give more info here?
The sub-nav buttons: Ranked, Polls, Threads, New, where gone for some time...
Getting the feeling I was testing in the midst of an update 😅
Hmm, not sure what happened. The update should have only taken a few seconds. Thanks for reporting. I'm glad it's resolved now.
