Skip to content
This repository has been archived by the owner on Jul 28, 2024. It is now read-only.

Fix font import #15

Open
malikpiara opened this issue Jul 1, 2019 · 9 comments
Open

Fix font import #15

malikpiara opened this issue Jul 1, 2019 · 9 comments
Assignees
Labels
help wanted Extra attention is needed
Milestone

Comments

@malikpiara
Copy link
Member

Screenshot 2019-07-01 at 20 52 22

Screenshot 2019-07-01 at 20 52 10

@malikpiara malikpiara added this to the Blog Launch milestone Jul 1, 2019
@malikpiara malikpiara self-assigned this Jul 1, 2019
@malikpiara
Copy link
Member Author

@hacdias @fabiofcferreira: For some reason the font displays in a different way. Do you know what's going on? How may I solve this issue?

Here's a blog URL: https://blog.hotscope.io/fail-fast/

@fabiofcferreira
Copy link

@malikpiara

After checking the font-weights in the images I came to the conclusion that maybe Safari is rendering that h1 tag with a different font-weight but I may be mistaken. However, since I'm writing this on a Windows machine I can't really tell for sure.

Therefore, to solve this, I guess you should define that h1 tag to have its font-weight set to 500.

@malikpiara
Copy link
Member Author

Also happening on the phone, android too.

@fabiofcferreira
Copy link

Just check the pages witht the tips I gave you and come back with some feedback. What you said strengthen my doubts about the browser the page is displayed in.

@malikpiara
Copy link
Member Author

@fabiofcferreira I changed the font-weight before commenting. Also ran some other tests.

@malikpiara malikpiara added the help wanted Extra attention is needed label Jul 2, 2019
@hacdias
Copy link

hacdias commented Jul 2, 2019

Answer to that: https://stackoverflow.com/a/30878469.

@fabiofcferreira
Copy link

We know Malik very well and I'm sure he will want a solution for both browsers to render exactly the same. 😆
The second link discusses the -webkit-font-smoothing property, which Hotscope CSS already includes. This is rather strange.

Perhaps it could be Safari?

@hacdias
Copy link

hacdias commented Jul 2, 2019

I really doubt it can be solved. There will always be differences in the way browsers render text. As it is stated in that reply:

If, for some masochistic reason, pixel perfection is more important than sanity and maintainable code, you can try the old standy-bys (text-in-images, image/text replacment) or turning off subpixel rendering via CSS (although not all browser support it, and the text will be less readable).

@fabiofcferreira
Copy link

fabiofcferreira commented Jul 2, 2019 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants