There may also be no Application in contexts where we want to render a global search menu, notably the 404 page:

I think I missed one case here: the global preference will currently show custom personal queries for the viewing user, but selecting these queries won't work (at least, not completely) for other users. Instead, the control should offer only hard-coded options and global queries.

I'm going to roll this forward into T13069, which discusses remaining work for "mail stamps".

Worth noting that the desirability of self-notifs is highly contextual. We use gmail, I was shocked to find there is no way to get gmail to let me see my own posts. But then I'm one of the few people using a local mail client, and it is actually kind of annoying when I have to slog thru the copies of the self-notifs on my phone to try and get to the one comment in the midst of potentially dozens of self-notifs.

It's discoverable in settings just fine.

oh dear, what did I get myself into.

derp this is done.

Yeah, that directly helps with this. I think I have a pretty good plan for the actual mail part that isn't too crazy complicated, but the cutover/migration bit will be much simpler/smoother if we get things swapped over -- at least, most of the way -- ahead of this.

Just to clarify, it is good to be moving all the apps to modular transactions? This task is my primary motivator to cleaning that up.

I have a rough cut of this one.

One spanner in the works here is that not all applications with mail preferences are on Modular Transactions yet. I think these are missing:

The most important aspect in flexibility is the ability to support all locales. MediaWiki uses a system largely based on PHP's date() for historical reasons, see Language::sprintfDate().

Thanks! Yeah, this was just some editing/testing slop on my part. Your suggested fix is correct.

• Try to come up with a way that - can do something dangerous when injected into a CSS rule.
  • See D7274#47131 for a template of how to attack this.
  • If you can come up with any attacks, don't implement this.
• Adjust the regular expression in PhabricatorMonospacedFontSetting::filterMonospacedCSSRule() to include -.
• Adjust the error text in PhabricatorMonospacedFontSetting->validateTransactionValue() to say "..., hyphens, ..." or similar.

Thanks @chad, but it seems not good enough.

Full screen disables live previews in any remarkup box.