rugk

> If you're not careful, someone might sneak in JavaScript into that HTML code. Of course, but you should trust & review your JSON files. Also even Markdown needs to...

> but humans make flawed, so it can't hurt to add some security layers. Well… devs should check the stuff they have in their repo. If there is rogue stuff...

> How would you solve these complex views like help pages if not by using markdown or similar? HTML. Or, generally in your case you may split it into smaller...

I think you could always try to get users to this view in GitHub, should not you: https://github.com/rugk/offline-qr-code/edit/master/src/_locales/de/messages.json Using your "stuff copied to clipboard" trick, users then can just paste...

First time I clicked on the link GitHub was like "Wanna fork this?". So I got back the way I usually would and clicked on the edit button manually, and...

That "guide" you mean was the popup I've mentioned. Yes, just say them to "You may need to click on a green button to fork the project." (something like this)...

I guess this is actually maybe an interesting idea. As then you may be able to add a "Translated into by \" line to the add-on. Thinking about the details,...

> I would rather write up a recommended things to do, so that extension authors can choose the naming of the message key themselves. 👍 > since it's always shown...

Maybe @yfdyh000 means if you have the ID multiple times in the original file. IMHO, however, that's bad practice and probably causes bad/unexpected browser behavior.

Hmm, don't get what you talk about IDs. IDs should (and usually even have to) be unique. However, what I could guess this issue is about - and a feature...