I'm also wondering about this. I've moved the fields around in that config setting, but I can't get Maniphest Tasks: to appear in the template when running arc diff. Is this still the place to make the change or has it moved since you comment?

The first one's always free...

Seeing as how you don't need to select a result for the mention to work, the inability to get the typeahead results back after dismissing them isn't that big of a deal either way, imo.

Ok, here's what just happened on my initial test run:

I expect compensation for being the catalyst to ideas.

Boom. Firewall. I'll stop spamming you now.

Well, it still says disconnected in my notification panel even though I see the notifications being added to the log and I don't have an unresolved setup issue, but at least it installed correctly. I'll keep debugging around and see if I can figure out why. Thanks for the help.

Ok, so I just removed node, and then added a symlink from nodejs to node and it installed correctly. Not entirely sure what node was or why it was there. Perhaps in your script you might look to use nodejs first and then node if not there? Or maybe I just have a screwed up system.

Hmmmm, is there a difference between node and nodejs? I can't seem to get a version from node.

Can we style a real <select /> like that, or would we have to implement an element in JS? (I don't think we can colorize options in a <select />.) I'm a bit hesitant about replacing a <select /> with a JS element here because it's used heavily and we'll either lose functionality (tab focus, keyboard navigation) or need to spend a significant amount of time rewriting it in JS.

ARIA has standards to enable the understanding of these drop-downs with screen readers. You can give your link aria-haspopup="true" and aria-expanded="false". Then, when the popup opens, you should set focus within it and return focus to the link when the popup closes. Ideally you should also trap focus within the popup while it is open and give your link a role="button".

Although this works, you might find with this implementation that you're going to be duplicating a lot of things just to get text readable to a screen reader. Instead you might consider just labeling the existing elements better so they seem less confusing to a blind user. For instance, instead of just hiding your alerts, give them labels so that they have meaning.