I see that this issue is not reproducible in the extension when run from source. But it is reproducible in the latest version of the extension that is installed from addons.mozilla.org.
Was this issue fixed with some later commit after releasing a version to addons.mozilla.org? If yes, then this issue can be safely marked as resolved, right? Personally, in my humble opinion, it would be difficult to keep track of releases on external platforms as means to close issues. Rather, in my humble opinion, we should close issues after committing code that fixes it with a back-reference to the issue in the commit message.
I see that this issue is not reproducible in the extension when run from source. But it is reproducible in the latest version of the extension that is installed from addons.mozilla.org.
Was this issue fixed with some later commit after releasing a version to addons.mozilla.org? If yes, then this issue can be safely marked as resolved, right? Personally, in my humble opinion, it would be difficult to keep track of releases on external platforms as means to close issues. Rather, in my humble opinion, we should close issues after committing code that fixes it with a back-reference to the issue in the commit message.
It was fixed 4 months ago when I worked on the code last time.
Issues are closed when the fix is published to Mozilla Addons because the development code is irrelevant to most users.
It was fixed 4 months ago when I worked on the code last time.
Issues are closed when the fix is published to Mozilla Addons because the development code is irrelevant to most users.
Niklas Poslovski
As soon as I click on "TOML" only the copy textarea is displayed but nothing's copied to the clipboard.
The same bug appears for me,too. I'll have a look at this and fix it with the next release.
I see that this issue is not reproducible in the extension when run from source. But it is reproducible in the latest version of the extension that is installed from addons.mozilla.org.
Was this issue fixed with some later commit after releasing a version to addons.mozilla.org? If yes, then this issue can be safely marked as resolved, right? Personally, in my humble opinion, it would be difficult to keep track of releases on external platforms as means to close issues. Rather, in my humble opinion, we should close issues after committing code that fixes it with a back-reference to the issue in the commit message.
It was fixed 4 months ago when I worked on the code last time. Issues are closed when the fix is published to Mozilla Addons because the development code is irrelevant to most users.