epriestley dba1b10720 Deactivate the remarkup autosuggest once text can't match "[[" or "((" rules ... Summary: See PHI1185, which reports a performance issue with "(" in remarkup in certain contexts. I can't reproduce the performance issue, but I can reproduce the autosuggester incorrectly remaining active and swallowing return characters. When the user types `(` or `[`, we wait for a prefix for the `((` (Phurl) or `[[` (Phriction) rules. We currently continue looking for that prefix until a character is entered that explicitly interrupts the search. For example, typing `(xxx<return>` does not insert a return character, because we're stuck on matching the prefix. Instead, as soon as the user has entered text that we know won't ever match the prefix, deactivate the autocomplete. We can slightly cheat through this by just looking for at least one character of text, since all prefixes are exactly one character long. If we eventually have some kind of `~~@(xyz)` rule we might need to add a more complicated piece of rejection logic. Test Plan: Typed `(xxx<return>`, got a return. Used `((` and `[[` autosuggest rules normally. Used `JX.log()` to sanity check that nothing too crazy seems to be happening. Reviewers: amckinley Reviewed By: amckinley Differential Revision: https://secure.phabricator.com/D20365		2019-04-01 15:40:38 -07:00
..
rsrc	Deactivate the remarkup autosuggest once text can't match "[[" or "((" rules	2019-04-01 15:40:38 -07:00
index.php	Let the top-level exception handler dump a stack trace if we reach debug mode before things go sideways	2019-02-11 15:36:19 -08:00