Merge pull request #11375 from vector-im/travis/fix-chrome-favicon

Perform favicon updates twice in Chrome
This commit is contained in:
Travis Ralston 2019-11-12 15:20:43 -07:00 committed by GitHub
commit 2e642310b8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 23 additions and 3 deletions

View File

@ -85,9 +85,29 @@ export default class VectorBasePlatform extends BasePlatform {
bgColor = "#f00"; bgColor = "#f00";
} }
const doUpdate = () => {
this.favicon.badge(notif, { this.favicon.badge(notif, {
bgColor: bgColor, bgColor: bgColor,
}); });
};
doUpdate();
// HACK: Workaround for Chrome 78+ and dependency incompatibility.
// The library we use doesn't appear to work in Chrome 78, likely due to their
// changes surrounding tab behaviour. Tabs went through a bit of a redesign and
// restructuring in Chrome 78, so it's not terribly surprising that the library
// doesn't work correctly. The library we use hasn't been updated in years and
// does not look easy to fix/fork ourselves - we might as well write our own that
// doesn't include animation/webcam/etc support. However, that's a bit difficult
// so for now we'll just trigger the update twice.
//
// Note that trying to reproduce the problem in isolation doesn't seem to work:
// see https://gist.github.com/turt2live/5ab87919918adbfd7cfb8f1ad10f2409 for
// an example (you'll need your own web server to host that).
if (window.chrome) {
doUpdate();
}
} catch (e) { } catch (e) {
console.warn(`Failed to set badge count: ${e.message}`); console.warn(`Failed to set badge count: ${e.message}`);
} }