Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Content
Content
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 299
    • Issues 299
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • Better
  • ContentContent
  • Issues
  • #410

Closed
Open
Opened Jun 08, 2016 by Aral Balkan@aralOwner0 of 2 tasks completed0/2 tasks
  • Report abuse
  • New issue
Report abuse New issue

Google fonts breakage

Google’s gstatic domain is also used to serve fonts (example call http://fonts.gstatic.com/s/lato/v11/qIIYRU-oROkIk8vfvxw6QvesZW2xOQ-xsNqO47m55DA.woff)

Given that Google has permeated the web like a cancer, we are going to have to be more precise in our blocking of the gstatic domain so as not to break the web.

  • Review gstatic calls and add precise rules for tracking resources
  • For assets such as fonts.gstatic.com, only block cookies so that the asset itself still works.
Assignee
Assign to
9 June, 2016
Milestone
9 June, 2016 (Past due)
Assign milestone
Time tracking
None
Due date
None
2
Labels
Bug trackers
Assign labels
  • View project labels
Reference: better/content#410

Like this? Fund us! Your patronage helps keep us independent and going.