Skip to content

Add robust support for mobile #27

Description

@terrill

How should Able Player behave on mobile devices? Need to consider what's practical and possible on various platforms then implement an appropriate custom/responsive design.

Activity

  1. vierkantemeter commented on Aug 25, 2015

    @vierkantemeter
    Contributor

    Hi Terrill, I just discovered the Able Player today and I love it! Accessibility is very important for my clients and this is the only player I could find that supports sign language! Thank you very much :)
    I was wondering if there is any progress for this issue. I'm trying to make the player responsive (I have not worried about the features for now, just the way it's displayed) but I'm finding it quite difficult to get it to look good on smaller screens. I've removed a lot of 'hard coded' widths already and added css 100% widths, but it's not really consistent. Would be great if there was an update on this subject!

    • Michèlle
  2. self-assigned this
    on Apr 25, 2016
  3. terrill commented on May 7, 2016

    @terrill
    MemberAuthor

    Player is now responsive as of f7dec0f

    There's a lot more to be done though to make the experience usable on mobile devices...

  4. 3 remaining items

  5. joedolson commented on Jun 16, 2025

    @joedolson
    Member

    Practically speaking, this may never be 100% resolvable; there will probably always be some issues. But I'm going to aim to improve this as much as I can.

  6. joedolson commented on Jul 24, 2025

    @joedolson
    Member

    A significant amount of the work is done here in the process of updating the base CSS. More probably still to polish, but this is well on its way to being closable.

  7. joedolson commented on Aug 10, 2025

    @joedolson
    Member

    I'm leaving this open. I've done a lot of work on it, but I'm going to leave it open through beta to address any additional issues.

  8. joedolson commented on Sep 18, 2025

    @joedolson
    Member

    In a certain way, this is a never ending issue. I'm going to leave it open and move it to 4.8. It's significantly progressed, but I hesitate to call it done.

    #680 is an important one to improve this, I think - it should allow removing a number of misc. script-based recalculations.

  9. modified the milestones: 4.7, 4.8 on Sep 18, 2025
  10. joedolson commented on Jan 7, 2026

    @joedolson
    Member

    I've made another round of improvements on mobile that hit this issue. I'm still going to leave it open and move to 4.9, as I'm not 100% satisfied yet.

  11. modified the milestones: 4.8, on Jan 7, 2026
  12. modified the milestones: , 5.1 on Mar 22, 2026
  13. joedolson commented on Sep 18, 2026

    @joedolson
    Member

    The orientation changing committed for #737 is also relevant here.

  14. modified the milestones: 5.1, 5.2 on Oct 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions