Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix weird bug with svg images on /index #304

Merged
merged 1 commit into from
Nov 28, 2019

Conversation

m52go
Copy link
Contributor

@m52go m52go commented Nov 28, 2019

To address #295.

Issue seems to be OS-related, as it was introduced with #278, and only seems to occur on macOS (which explains why I never saw the issue when reviewing).

I don't deem it worthwhile to debug, so I've just switched all screenshots back to PNG. SVG files remain in the repository as "source" files in case the PNGs need to be updated later.

Please review this PR on macOS or Windows, as the issue never occurred on Linux.

https://deploy-preview-304--bisq-website.netlify.com/

It seems the SVGs used for screenshots on the front
page did not behave consistently across OSes. Testing
indicated no issues on multiple browsers on Ubuntu,
but testing on macOS indicated SVG font properties
were not being applied correctly.

Images were PNGs before, and there was no particular need
to switch to SVG, so this commit switches them back to PNG.

The switch was initially made in bisq-network#278 to produce
translated screenshots. SVG files remain in the repository
as "source" for the PNG files.
Copy link
Contributor

@cbeams cbeams left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK. LGTM on macOS 10.14.6 + Firefox 70.0.1.

@m52go m52go merged commit 8839646 into bisq-network:master Nov 28, 2019
@m52go m52go deleted the fix-index-images branch November 28, 2019 17:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants