Jason Gray

> This focus thing is a big flaw I experience all the time. Has it been reported somewhere? I mentioned it in a bug report for key binding back in...

They'll just figure out some kind of sideband GLib app only way to work around it. What really needs to happen if it hasn't already is a desktop agnostic mediakeys...

GNOME Shell sucks at keeping track of focused apps. Separate instances of an app are treated as the same app by default. That's why I wrote the AppWrapper class. Otherwise...

> However, [that MR](https://gitlab.freedesktop.org/mpris/mpris-spec/merge_requests/1) has already gotten some pushback. ...From you. Oh. Never mind! It's not that I'm totally opposed to a "focused" prop I just think that it's a...

My bad it's `--disable-features=MediaSessionService` An easy way to play with flags is to go to chrome://flags/ change the flag you want, restart Chrome and then go to chrome://version/ and see...

> It seems that the `#hardware-media-key-handling` flag has been removed on newer Chrome versions. It can still be enabled under expired flags, but it will permanently be removed in the...

> I totally agree with you, Chrome devs should just fix this. Nonetheless, it's unrealistic that it will ever happen. > I definitely understand that some people might want Chrome...

Update: So I've split out all translatable strings to```translations.js``` that is the only file that has translatable strings. Each translatable string has a very detailed description. I've set it up...

I've noticed a bit of a potential issue. Currently in some situations it may not be possible to get the translations in the right grammatical order because of how accessibility...

@saboya That would be awesome. Before you start I need to tweak some of the translatable strings a bit and actually get off my lazy butt and figure out how...