Siddharth VP

@nasch92 Looks good, but you appear to be using morebits, which is based on jquery.ui. So it's not "jQuery-less" :)

> In terms of GUI, features, etc, how identical or different is twinkle-core compared to this Twinkle repository? Also, is it stable and reasonably bug-free? It is identical, or at...

https://github.com/wikimedia-gadgets/twinkle/blob/e53521a9e731/morebits.js#L5247 Calling `.update(..., 'info')` or `.info(...)` on the status element will make it green.

This is a no-op now since the MediaWiki changes have been merged. So this is just code simplification - doesn't require testing per se (other than to check Morebits.date is...

I think polling the API every 5 seconds or so is a reasonably good approach.

@Amorymeltzer you use modern but have never felt a need for this?

I see the code is at [MediaWiki:Gadget-dropdown-menus-nonvector.js](https://en.wikipedia.org/wiki/MediaWiki:Gadget-dropdown-menus-nonvector.js). I plan to get to it over the weekend.

Also originally requested by Liz at https://en.wikipedia.org/w/index.php?title=Wikipedia_talk:Twinkle&oldid=1021836648#Twinkle_glitch :)

Twinkle should be able to detect tags for removal even if they are not in its dictionary. This relies upon the fact that ambox templates carry a `box-$NAME` class on...

https://github.com/wikimedia-gadgets/twinkle-enwiki/tree/master/tests/integration Yes, why not. But I'd more prefer if we could migrate to use twinkle-enwiki itself :)