chore: discard old font file formats #673
No reviewers
Labels
No Label
area/internal-code
changes requested
confirmed
dependencies
duplicate
good first issue
help wanted
hosting
invalid
kind/bug
kind/feature
question
wontfix
No Milestone
No project
No Assignees
2 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/frontend#673
Loading…
Reference in New Issue
No description provided.
Delete Branch "dpschen/frontend:feature/only-woff2-fonts"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
browser support for woff2 is 96%; see: https://caniuse.com/woff2
Does this really make a difference? AFAIU browsers will only load the formats they understand so if a browser knows how to use woff2 it will ignore the other formats.
Maybe it's a good idea to keep at least woff?
See: https://stackoverflow.com/questions/11002820/why-should-we-include-ttf-eot-woff-svg-in-a-font-face
So woff makes just sense if you support IE11?
But it makes sense to also remove the
local
includes: https://stackoverflow.com/a/36110385/15522256I will change the pull request accordingly.
22791ee9f2
toefecfb1e26
Yeah I think that makes sense. We don't support IE since it is officially discontinued by Microsoft.
I was more worried about older version of Firefox and co, but then the question is how much Vikunja works in those and if a broken font would be the biggest issue (I don't think so). Maybe we can just remove woff and add it back in when someone complains?
That makes sense! :)
I wouldn't assume it will be a problem. Firefox doesn't have many user and it's evergreen, so I wouldn't assume problems there =)
I have used only woff2 in larger projects and nobody complained :D
Thanks again!