In the brief gap between my previous proposal ending, and this one starting, I'd forgotten how quickly the time disappears when working on updates!

Before starting on new features, I thought that I would tidy up as many of the existing issues recorded on GitHub as possible... which led to the implementation of a feature that users have been requesting for a while and that I need the community's help in testing!

First off, the bugs...

🪲 Upvote bar off-screen on mobiles

If you use Steemit on a mobile, you'll have encountered this issue.

If a post / comment's voting buttons appear on the same line as the username (which is normally when the post / comment is by an author with a short username / no community title and hasn't been voted on), then when you click to upvote it, the voting bar is only partially displayed with the remainder appearing off screen - as demonstrated in the screenshot to the right.

This obviously makes voting with different percentages difficult.

Since the voting buttons then appear underneath the username after the vote, I've updated the code to always display the buttons here (underneath the username).

This is only applicable to mobile devices.

🪲 "Hide resteems" logic should not be used for accounts' blogs

When the Hide Resteems logic was introduced last year, a bug was introduced that made some user's blogs unviewable if "Hide Resteems" had been selected on their "Friends Feed".

This has now been fixed so that the "Hide Resteems" filter is only applied on the "Feeds" screen.

🪲 Tags missing when you switch "Subscriptions"

This issue was a design decision taken by the previous developer / solution designer.

The reason for this implementation is due to the hidden community tag (hive-xxxxxx) that doesn't display on the front-end.

When switching communities, the developer reset all of the tags in order to remove this "hidden community" which forces the user to start again.

My updated implementation carries the tags but rather than reset them all, it removes any tags that start with hive- and leaves the rest.

Since you can't manually include another hive- tag alongside the hidden community tag, this implementation makes sense.

🪲 ToS Wording Error

A straightforward fix to update the below wording:

12.2. If you do not maintain a backup of your Account data outside of the Services, you will be may not be able to access STEEM, Steem Dollars and Steem Power associated with any Account maintained in your Account if we discontinue or deprecate the Services.

so that it makes sense:

12.2. If you do not maintain a backup of your Account data outside of the Services, you may not be able to access STEEM, Steem Dollars and Steem Power associated with your Account if we discontinue or deprecate the Services.

🪲 Removed expired references

Removed references to cheetah, steemcleeaners and Utopian.io (which doesn't exist any more) from the FAQs because they're spammy scum bags.

🖼️ Images Opening in a New Tab

Whilst reviewing this bug - The picture is low quality on desktop, I started playing with the image quality within blog posts.

Images are currently optimised to be 640 pixels wide, since this is the width of a blog post and is therefore the optimal size. But... if a user wants to see the detail of an image (i.e. if it contains text that is too small to read), opening the image in a new tab will open the "optimised" 640 pixels version, and therefore display a blurred image.

E.g. If you click the image below, you'll see a blurred image...

The only way around this would be for the author to manually insert a link 'a tag' around the image with a link to the high resolution version.

Whilst this functionality is available, it's an approach that isn't well known and requires some knowledge of coding.

So I've now implemented some functionality that makes images clickable by default and opens the original version in a new tab.

This is indicated by the picture icon that appears on-hover (on desktop and is always visible on mobile), along with a 'title' tag indicating this to the user.

Where a user has already manually added a link around an image, the icon and label used differs:

This is to ensure the user can differentiate external links to standalone images.

---

The implementation of this has been "interesting" due to the different ways that people can include an image in their post.

1. They can just drop an https:// link directly to an image

2. They can use markdown

3. They can use HTML

The code currently caters for scenarios 2 and 3 as it recognises these as images and stores them separately.

Whilst the rendering can display images submitted via method 1, it doesn't store them in this separate image array (something that other developers might have noticed in the rendered code and not known the reason for).

I think I'll save the technical details for my Change Log... it was a pain to implement.

My implementation only applies to images that are 50px or higher. This is so that custom spacers don't have this applied.

Whilst implementing this, I also implemented the acceptance of target="_blank" for links and this is what I use to open the images in a new tab. All external links that aren't on the steemit.com domain will have this target included.

All of the links also use the "noopener" tag to mitigate against phishing attacks as well as replacing any other targets (e.g. _self, _top, etc.) with _blank for the same reason.

Since images URLs are not checked upon submission, somebody could put a dodgy URL in an image link which when clicked, would take the user to their dodgy website.

For this reason, images are still passed through the existing proxifyImageUrl function.

Please Test This

Ukrainian Translation

@o1eh has provided me with a translation file for the Ukrainian language which has also been included in this release.

Although... when testing it to get a screenshot, switching to Ukrainian crashes the site so don't do this yet!

@o1eh - I'll contact you once I've fixed this! All working now, please can you ask the Ukrainian community to test.

PS. The % character is fairly important 😆

There's a lot of text today, I hope that it all makes sense and you approve.

Please spread the word that these changes are available and to let me know what you think.