Advanced search

On other websites (6037)

• Evolution #4768 (Nouveau): Sus aux préfixes navigateurs

  5 May 2021

  Dans les CSS du privé on commence à utiliser largement des propriétés qui peuvent requérir des préfixes navigateur : flex, grid, etc.
  Pour ma part je ne les ai pas encore préfixées, en général je fais ça sur la fin une fois que tout est stabilisé (mais j’ai vu que j’étais pas le seul à pas préfixer, ouf).
  Mais ces préfixes sont vraiment une plaie intégrale : c’est chronophage à ajouter et encore plus à modifier, ça alourdit le code et le rend moins lisible, ça fait du bruit de fond dans les commits quand il faut les mettre à jour lorsque le support évolue, et j’en passe.

  Mais s’occuper des préfixes navigateurs, c’est pas notre boulot :)
  On ne devrait plus avoir à faire ça manuellement.
  À défaut de préprocesseur ou d’outil qui permettrait de faire ça semi-automatiquement (en général ils buttent sur les balises Spip de nos squelettes css), il existe une autre solution : les autoprefixeurs JS.
  Ils ajoutent les préfixes à la volée, mais uniquement ceux nécessaires au navigateur, produisant une css plus légère qu’avec les autres solutions.

  Celui-ci est très léger, 2Kb gzippé, il suffit d’inclure le script dans la page et c’est tout : https://projects.verou.me/prefixfree/
  Je propose de l’intégrer et d’oublier les préfixes à tout jamais.

  Dans le privé il serait chargé tout le temps.
  Pour le public, je ne sais pas, 2 possibilités :

  • se contenter de dire qu’il est disponible dans la doc technique, charge aux gens de l’intégrer eux-mêmes dans leur squelettes s’ils en ont l’utilité.
  • ou bien faire un mini plugin-dist sur le même modèle que l’ancien iepatch, avec une option de config « charger le script bla bla ».

• New cookie behaviour in browsers may cause regressions

  24 February 2020, by Matomo Core Team — Community, Development

  Last year the Chromium browser team announced they would change their default behaviour for cookies. In particular about a property called samesite. Over the last few months, we have made various changes to our cookie handling to get Matomo ready for this. Depending on your setup and the features you use, some things may not work anymore.

  You can avoid most of the issues by using HTTPS on your Matomo, and ideally also use HTTPS on your website(s).

  If you are not running the latest version of Matomo yet (3.13.3 at the time of writing), then we highly recommend that you upgrade as soon as possible. Previous versions are not compatible with these cookie browser changes.

  Opt out screen

  If you embed the opt out screen on your website running on HTTP, there is a chance the Matomo opt out no longer works. In these cases it may still work over http:

  • when the privacy policy page that embeds the opt out screen (via iframe) also has the Matomo JavaScript tracker embedded,
  • and when both the opt out and the JS tracker point to the same Matomo installation.

  In other cases when HTTP is used, the opt out feature will likely be broken.

  We recommend you test whether the opt out on your site still works by opening your privacy policy page in an incognito browser window. Then test to opt out of tracking, and then reload the page. If the checkbox “You are not opted out. Uncheck this box to opt out.” is still ticked, then your opt out is not working.

  If the opt out is not working anymore, it is most likely due to HTTP being used. In that case you should change the opt out URL to HTTPS. For example change from &lt;iframe src=”<strong>http://</strong>…” to &lt;iframe src=”<strong>https://</strong>...” . If your Matomo doesn’t support HTTPS yet, you will need to contact your webhoster or system administrator to get SSL enabled on your Matomo domain.

  JavaScript tracker

  In most cases, everything related to the JavaScript Tracker will still work as expected.

  But there is an edge case: when you are also reading Matomo’s cookie server side. You may be affected by this edge case issue when:

  • you track part of the user behaviour in the browser (using Matomo JS Tracker),
  • and also track user behavior in your server (for example using one of Matomo SDKs in PHP, Java, Python, C#, etc.).

  In that case, for you to still be able to read the so-called visitorId on your server, we recommend you add this line to your JS tracking code:

  _paq.push([‘setSecureCookie’, location.protocol === 'https:']);

  The cookie can be only retrieved if your website is loaded through HTTPS.

  Should you have any questions, or notice anything isn’t working as expected, please visit our forum.

  Third party cookies

  If you are using third party cookies, using HTTPS on your Matomo is now a requirement to make them work across different domains. Otherwise Chrome and in the near future other browsers would not accept the cookie. If you don’t know if you are using third party cookies or first party cookies, you’re likely using first party cookies and this does not affect you.

• New Piwik 2.0 public beta for testers

  16 October 2013, by matt

  Dear Piwik community,

  We are excited to announce the release of the first public beta version of Piwik 2.0.

  This is software still in development and we really don’t recommend that you run it on a production site — set up a test database just to play with the new version.

  Piwik 2.0 is a major update from Piwik 1.12 and is the result of 5 months of work on the platform!

  What’s changed?

  We focused on upgrading Piwik source code quality and maintainability: upgraded to PHP 5.3 using namespaces, changed templating library to Twig, started using composer, using Less as well as css, improved QA tests, introduced new Screenshots tests, refactored translations to nice JSON format, refactored LOTS of code, added documentation….

  There also performance improvements, in particular the “All Websites Dashboard” is now usable with 20,000+ websites!

  Several bugs were fixed and we added some very-special-and-exciting new features.

  See the list of closed tickets in Piwik 2.0, or learn more about our recent developments in the Development update blog post.

  Piwik 2 is the open platform for your analytics data!

  How to update to Piwik 2.0 beta?

  1. You can tell Piwik to use the latest beta from within the user interface. See this FAQ: [piwik.org]
  2. or alternatively you may download the latest beta from the build server, upload these files on top of your existing piwik files, and visit Piwik to upgrade.

  Beta cycle
  The more you test the beta, the more stable our release candidates and our final release will be. If you think you’ve found a bug, you can post it in this forum post. Or, if you’re comfortable writing a reproducible bug report, file one. The stable Piwik 2.0 release is planned for mid-November!

  Happy testing,

  PS: if you are interested in professional support for Piwik, or custom feature development, contact the Piwik experts.