Skip to content
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

Vector is all sorts of broken on mobile web #205

Closed
5 of 11 tasks
ara4n opened this issue Oct 11, 2015 · 5 comments
Closed
5 of 11 tasks

Vector is all sorts of broken on mobile web #205

ara4n opened this issue Oct 11, 2015 · 5 comments
Labels
P2 X-Needs-Info This issue is blocked awaiting information from the reporter

Comments

@ara4n
Copy link
Member

ara4n commented Oct 11, 2015

In no particular order:

  • Incredibly slow and unreliable at changing rooms
  • Lets you scroll off the bottom of the screen
  • Doesn't resize when keyboard is visible
  • Need to change the zoom to be more legible in general
  • Autofocuses the input box too often, rezooming everything
  • Hoverovers get stuck on
  • Doesn't default to hiding membership list (on 6+ at least)
  • Flexbox bug on iOS 9.2 means invite box overlaps the membership list
  • Scrolling to bottom of the timeline doesn't make it all the way
  • Avatars overlap (general Safari layout bug potentially)
  • doesn't progressively load (bundle.js is enormous #126 aka bundle.js is way too big and should progressively load to speed up initial launch #2498)

I fixed most of these for angular already; it's just a matter of porting over similar fixes.

New screenshot:
ima_52e1219

@ara4n ara4n modified the milestone: Ragnarok Nov 29, 2015
@ara4n ara4n removed this from the Ragnarok milestone Apr 13, 2016
@lampholder
Copy link
Member

Do we still want this?

@lampholder lampholder added the X-Needs-Info This issue is blocked awaiting information from the reporter label Jul 20, 2018
@turt2live
Copy link
Member

@lampholder I'm pretty sure we can close this because of the mobile landing page...

@lampholder
Copy link
Member

Works for me. There's an app for this, I've heard :P

@ara4n
Copy link
Member Author

ara4n commented Feb 14, 2019

i’m not entirely sure we should close this one tbh; we need to make Riot more of a PWA, and a good indicator if whether we have is if it runs on mobile. At least, this was my motivation...

@jryans
Copy link
Collaborator

jryans commented Feb 15, 2019

I think we would need to very consciously choose to support mobile web and invest in making it work for there to be any chance of it working well as each new feature lands over time. (To be clear, I think it would be great to support this! I just want to call out the level of investment required.)

If we're not in a position to support mobile web now, maybe we leave this closed until we are. (After all, I would likely also close issues that only happen in ancient desktop browsers we don't support, since they are outside our supported set.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 X-Needs-Info This issue is blocked awaiting information from the reporter
Projects
None yet
Development

No branches or pull requests

4 participants