Skip to content
Snippets Groups Projects
Select Git revision
  • rebase/glitch-soc default protected
  • features/local_only
  • pleroma
  • master
  • features/attachments-enhance
  • glitch-soc/fixes/scrolling
  • rebase/tootsuite-2.5.0 protected
  • rebase/tootsuite-2.4.3 protected
  • rebase/tootsuite-2.4.2 protected
  • pleroma-old protected
  • unread
  • authors
  • procfix
  • fix-privacy-policy
  • feature-bio-fields
  • button
  • feature-paranoia
  • bundle-2020-05-14 protected
  • bundle-2020-02-27 protected
  • bundle-2020-05-20 protected
  • bundle-2020-01-22 protected
  • bundle-2020-01-20 protected
  • bundle-2019-06-26 protected
  • bundle-2019-04-11 protected
  • bundle-2019-03-07 protected
  • bundle-2019-02-10 protected
  • bundle-2019-10-01 protected
  • v2.6.0 protected
  • v2.6.0rc4 protected
  • v2.6.0rc3 protected
  • v2.6.0rc2 protected
  • v2.6.0rc1 protected
  • v2.5.2 protected
  • v2.5.1 protected
  • v2.5.0 protected
  • v2.5.0rc2 protected
  • v2.5.0rc1 protected
37 results
Search by author
  • Any Author
  • Duponin Duponin Duponin
  • HJ HJ hj
  • Haelwenn Haelwenn lanodan
  • Sean King Sean King seanking
  • feld feld feld
  • href href href
  • lain lain lambadalambda
  • mkljczk mkljczk
  • renovate-bot renovate-bot
  • tusooa tusooa tusooa
  • weblate bot weblate-bot
11 authors
  1. Dec 23, 2019
  3. Dec 22, 2019
  5. Dec 19, 2019
    • Sasha Sorokin's avatar
      Use different strings on exports page (#12569) · 902c6bed
      Sasha Sorokin authored 
      Currently the page re-uses strings from other contexts which doesn't fit
very well - strings incorrectly lowercase-d and pluralized, when they
don't need to be, because it's a table.

This commit changes page to re-use accounts.posts_tab_heading for toots,
and admin.accounts for "Following" and "Follows". This all should look
more aesthetically pleasing.
      902c6bed
    • ThibG's avatar
      Fix manual scrolling issue on Firefox/Windows (#12648) · dc0750ab
      ThibG authored 
      Fixes #12607

`will-change: transform` apparently makes manual scrolling impossible on
Firefox/Windows. While this should probably be considered a Firefox bug,
`will-change: transform` seem like a very aggressive performance hint that
may possibly make the browser consume more resources than needed, especially
in multiple-column mode.

This was originally added to improve scrolling performances on mobile, but
I think this isn't necessary anymore, because of the two following reasons:
- `contain: paint` (which is implied by `contain: strict`, which we apply
  whenever the browser supports grids) should have similar effects
- in single-column mode, the scrolling container is the root element, which
  I believe is optimized in at least Chromium

Keep in mind that I have not been able to make in-depth benchmarks, and
especially not been able to try on mobile, so performances should probably
be investigated further…
      dc0750ab
  7. Dec 18, 2019
  9. Dec 17, 2019
  11. Dec 16, 2019
    • Alice Gaudon's avatar
      Admin setting to disable default follows (#12566) · 668f6980
      Alice Gaudon authored
      668f6980
    • Thomas Citharel's avatar
      Add Event activity-type support (#12637) · 80949554
      Thomas Citharel authored 
      This adds support for Event AP type in Mastodon. Events are converted
into toots by taking their title (AS name) and their URL (AP ID). Event
picture is also brought in if available.

Testable by fetching event content from https://test.mobilizon.org



Signed-off-by: default avatarThomas Citharel <tcit@tcit.fr>
      80949554
    • Sasha Sorokin's avatar
      Improve report page structure (#12615) · 34aa5c7c
      Sasha Sorokin authored 
      * Move resolved button to the heading

This is one of the commits on improving overall reports page structure.
It changes where resolved button is located, moving it to the heading,
right next to the "Report #n" header, so-called "hot-place" to look at.

To accomplish this we have to declare one more content variable, change
admin dashboard template to respect it and CSS files for minor styling,
so buttons are inlined and centrally aligned according to the heading.

* Move actions buttons below the report table

I believe that actions to react on report should not be located at the
top of the page, instead they should be either after the table or
reporter's comment. This is just a logical sign that you should not
react to the report without reading all the details first.
      34aa5c7c