Board Thread:General Discussion/@comment-45534093-20200420135043/@comment-9605025-20200424185504

Yes, it is unfortunately difficult to do anything about this issue. The best you can do is limit yourself to using functions available in older specs (but that are still in the current specs). Having a JS solution is still better than no solution. I just thought you should be aware of this potential issue.

Another issue with your particular use case is that the edit would have to be made from the current user's account. Like any other edit, this would be recorded as something that they did. Users may not like that since the JS runs without their knowledge and doesn't offer them a choice to opt-out. This is particularly true for anons who may not like their IP address being posted.

Unfortunately, Fandom does not tell the viewer that the wiki uses custom JS. So someone who has JS disabled will either not notice or will see a broken feature. User-facing scripts sometimes use their placeholder elements to place a warning. For example, let's say you have this on a page (script documentation). This page uses JS to insert the timestamp of Andrewds1021's latest action on this wiki. If you are seeing this message, then something is preventing the JS from running. If the user's JS works, then they will see the timestamp of my most recent logged action. If not, they will see the message inside the span tag.