• Resolved Bonaldi

    (@bonaldi)


    Hi Chris,

    Happy new year !

    As usual for years now, last version fully translated in French.

    There’s just one problem with how you integrate Google’s font for material symbols:

    @font-face {
    font-family: 'Material Icons';
    font-style: normal;
    font-weight: 400;
    src: url(https://fonts.gstatic.com/s/materialicons/v98/flUhRq6tzZclQEJ-Vdg-IuiaDsNc.woff2?v=4.0.0) format('woff2');
    font-display: block;
    }

    @font-face {
    font-family: 'Material Symbols';
    font-style: normal;
    font-weight: 400;
    src: url(https://fonts.gstatic.com/s/materialsymbols/v37/d6kSkb-sS9m3-i1LgQNcsFOOuLQXvG559b5GLMxCWRtThFK5gn7xw7XblIl2peTfMb7ONaa2_wzcUHR1Ukiw2RYw2vadH3BFk0G4701x-cU0BaNVXEDuQA.woff2) format('woff2');
    font-display: block;
    }

    It is NOT GDPR compliant!

    The font must be embedded in the plugin, not called to Google’s servers, because there is then collection of IP address without prior consent.

    Please fix the problem quickly.

    Regards.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author chrisvrichardson

    (@chrisvrichardson)

    Hi,

    Thank you for the translation!

    The fonts have always been fetched from Google because they are too large to include in the plugin source. Note that the icon editor is used in the backend only. On the frontend, saved icons are displayed on the frontend as local PNG files.

    However, if you’d still like to prevent using the Google files, you can save them locally and just override the ‘url’ values in your styles.css. This should cause them to fetch from your server, even after the plugin is upgraded.

    Thread Starter Bonaldi

    (@bonaldi)

    Hi,

    I know, besides I modified the plugin by integrating the 2 fonts in a repertory fonts and I modified the mappress_admin.css.

    @font-face {
    font-family: 'Material Icons';
    font-style: normal;
    font-weight: 400;
    src: url('../fonts/flUhRq6tzZclQEJ-Vdg-IuiaDsNc.woff2?v=4.0.0') format('woff2');
    font-display: block;
    }

    @font-face {
    font-family: 'Material Symbols';
    font-style: normal;
    font-weight: 400;
    src: url('../fonts/d6kSkb-sS9m3-i1LgQNcsFOOuLQXvG559b5GLMxCWRtThFK5gn7xw7XblIl2peTfMb7ONaa2_wzcUHR1Ukiw2RYw2vadH3BFk0G4701x-cU0BaNVXEDuQA.woff2') format('woff2');
    font-display: block;
    }

    I didn’t notice any problem with the files sizes.

    Failure to do so exposes users to GDPR non-compliance, which is not desirable in my opinion.

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.