Skip to content
Snippets Groups Projects

New user option: Always show floating New Post button

Merged eris requested to merge (removed):showMobileNewPost into develop
All threads resolved!

The issue: Currently on the desktop site, if you're scrolled down the sidebar reading your notifications and want to post a new status, you have to leave your position to scroll back up. This seems like an unneccessary restriction given that the mobile post button and the modal for it exist and these work perfectly fine on the desktop version when not hidden by pleroma-fe.

The code: What this does is add a new option called "Always show floating New Post button" in the Compose section of the General settings tab. When enabled, pleroma-fe will no longer hide the New Post button. To prevent overlap with the Shoutbox, when this option enabled the Shoutbox will be moved to the left side instead of the right using a class and some CSS.

Issues with this: None known, this isn't adding a new component or anything but merely letting users access a feature they already have but was previously only accessible in the mobile nav.

Changelog and contributors file updated as well, and tested with npm run dev as well as on my instance (screens are from my instance)

Screens: postbutton postbutton2

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • HJ
  • HJ
  • HJ
  • HJ
  • eris added 1 commit

    added 1 commit

    • 4639e30c - Fix config naming for consistency

    Compare with previous version

    • Maintainer
      Resolved by Shpuld Shpludson

      There have been issues on mobile where you go to reply to someone and the post reply box opens up but the New Post floating button is still there too obscuring things and easy to hit causing some very amusing chaos

    • Author Contributor
      Resolved by eris

      See description, I clarified when I submitted this MR about why there's shoutbox code in it. It's not unrelated as these two elements normally use the same bottom-right corner at different times. This seemed the cleanest way to address it, by just switching the shoutbox side to the left only if this option is enabled.

      For reference, both of the user option merge requests are fully compatible with each other.

      "To prevent overlap with the Shoutbox, when this option enabled the Shoutbox will be moved to the left side instead of the right using a class and some CSS."

  • eris added 9 commits

    added 9 commits

    Compare with previous version

  • eris added 3 commits

    added 3 commits

    Compare with previous version

  • Shpuld Shpludson resolved all threads

    resolved all threads

  • eris added 13 commits

    added 13 commits

    Compare with previous version

  • HJ merged

    merged

  • HJ mentioned in commit a8a82ad1

    mentioned in commit a8a82ad1

  • Please register or sign in to reply
    Loading