tom [Tue, 31 Jan 2017 18:06:03 +0000 (13:06 -0500)]
Fix text overlapping image in Edge and on mobile (#582)
Changing the way the background image is positioned and the box is sized should fix problems with the text overlapping the image on mobile browsers and Edge.
Eugen Rochko [Mon, 30 Jan 2017 20:40:55 +0000 (21:40 +0100)]
Make profile header scroll along with contents. AccountTimeline, Followers and Following are no longer
nested inside a common parent (<Account>), instead they all embed <HeaderContainer />
Billie Thompson [Sat, 28 Jan 2017 23:49:42 +0000 (23:49 +0000)]
Add missing back button to "Follow Requests"
Currently we have the problem where the follow request button is missing
from the Follow request tab. This means that when you visit that tab you
either have to press the back button in the browser or re-enter the home
page, which breaks the app flow.
This will resolve that issue by adding a new back button to that tab,
in the same way that the public timeline, and favourites have.
Eugen Rochko [Fri, 27 Jan 2017 19:34:22 +0000 (20:34 +0100)]
Do not automatically login after password reset, as it would circumvent two-factor auth (if enabled)
Do not require e-mail address changes to be re-confirmed, it's only trouble for no real benefit
Eugen Rochko [Fri, 27 Jan 2017 15:55:06 +0000 (16:55 +0100)]
Do not run FetchLinkCardService on local URLs, increase file size limit to 8MB,
fix ProcessFeedService pushing status into distribution if called a second time
while the first is still running (i.e. when a PuSH comes after a Salmon slap),
fix not running escape on spoiler text before emojify
Billie Thompson [Thu, 26 Jan 2017 14:06:40 +0000 (14:06 +0000)]
Move the fonts from Google Fonts to local assets
Currently we have two problems that are resolved by this change.
The first is that we have a dependency on Google Fonts, which means
that should it ever go down, or it have issues we would also have
issues. This will resolve this by moving the dependencies we load from
there to the local server.
The second issue is that Google Fonts is currently returning the
`local()` css font source. This causes a problem where the users browser
fails to fallback to a missing glyph, resulting in many unusual
characters displaying the failure glyph. This will resolve this by
creating a font-family definition that does not use the `local()`
source.
I did not update the error pages with local fonts, they still use the
remote google fonts api, so they're a self contained page that does not
use the asset pipeline.
This resolves tootsuite/mastodon#531 and tootsuite/mastodon#12
shel [Thu, 26 Jan 2017 01:19:37 +0000 (20:19 -0500)]
Increase color contrast on getting started text
Currently, the getting started text fails WCAG standards for color contrast by a lot. Especially on the part overlapping with the elephant graphic which is nearly unreadable even for users with 20|20 vision. This change doesn't fix the elephant overlap but at least makes the text meet AAA WCAG Small Text color contrast standards, making it easier to read.
Eugen Rochko [Tue, 24 Jan 2017 23:49:08 +0000 (00:49 +0100)]
Instead of using spoiler boolean and spoiler_text, simply check for non-blank spoiler_text
Federate spoiler_text using warning attribute on <content /> instead of a <category term="spoiler" />
Clean up schema file from accidental development migrations
Eugen Rochko [Tue, 24 Jan 2017 20:40:41 +0000 (21:40 +0100)]
Make blocks create entries and unfollows instantly, but do the clean up
in the background instead. Should fix delay where blocked person
can interact with blocker for a short time before background job
gets processed
Eugen Rochko [Tue, 24 Jan 2017 16:05:44 +0000 (17:05 +0100)]
Fix #204, fix #515 - URL truncating is now a style so copypasting is not
affected, replaced onClick handler with onMouseUp/Down to detect text
selection not trigger onClick handler then
cat aescling's git repositories / mastodon.git / log