Janne Löfhjelm

Force-push to rebase branch since upstream had changes.

Nah, the problem is with tick rate. LCD screens of SteelSeries when used with API don't care about other settings if API sends a message, API seems to always get...

Multimedia keys are natively supported since Chrome 73, play/pause works out-of-the-box. Not completely sure if next/previous buttons could be supported as well after those changes. More information on this: https://developers.google.com/web/updates/2019/02/chrome-73-media-updates...

Implemented in my PR above.

It should work with Mozilla also if it's implemented according to standard defined by w3c (https://w3c.github.io/mediasession/) As for Safari, I haven't digged enough to know why it works, could be...

I disagree. If there are overlapping segments, in my opinion the only behaviour that makes sense is to skip longer segment. If it worked any other way, we would be...

Same problem. Some symptoms: - End result of match is now listed "None" instead of W/L - Timers are not shown. If forcingly refreshed ("Hide timers -> Show timers" from...

Backing up and trying to rename above mentioned config_corrupted.xml while changing version number to match new version might be worth a try. Didn't test myself yet > Lethalmikey ***@***.***> kirjoitti...

I can confirm it to be most likely BMBF issue. I'm not certain about what triggers this but I had similar issue today after updating from 1.17 to 1.17.1 with...

This issue is also present in Google Chrome (up-to-date version "Version 114.0.5735.134 (Official Build) (64-bit)") Nothing's breaking but 8 error logs load up on every refresh. Cleanest way could be...