Thomas Greiner

I really appreciate your help and it's indeed quite difficult to convince creators to receive free money. I've also forwarded your idea about setting up a landing page to the...

We've agreed on appending such a toggle to the options page. I've updated the issue description to reflect that and would like to point out that we'd probably still want...

Just FYI: Now that I've started working on this, I found that there's more to it than meets the eye. For instance, we also need to make sure that the...

I was also thinking about some simple radio buttons (see [current design](https://drive.google.com/file/d/13dQkMY8ltBlSl_3Ofquy0Li01T7Dh7F_/view?usp=sharing)) to keep the implementation simple. Two things to note: - I'll leave the texts to our Content &...

It's a work-in-progress so the design is still expected to change, especially since we don't have the final strings yet.

Changed icon state: https://github.com/flattr/flattr-extension/commit/c99b3af6361bc65438a9bf782a4d59d8f99da2d5

I was able to reproduce this using: - Flattr (development) 0.5.0.5 - Firefox 58.0.2 - Ubuntu 16.04 It's also worth noting that this doesn't occur for me on Chrome.

I found that the issue is that Firefox assigns the tab a new ID when it's moved to a different window whereas on Chrome the tab's ID remains the same....

Looking into it a bit further, both `browser.tabs.onAttached` and `browser.tabs.onDetached` turn out to be working as expected (i.e. provides the old tab ID). Only `browser.tabs.onUpdated` appears to be affected by...

Marked as "not ready" because it sounds like we need to wait for node-sqlite3 for that.