discourse/app
David Battersby 249f4296bf
FIX: fast-edit should fall back to composer for non-ascii characters (#21453)
The problem
The fast edit feature doesn't work well with non standard characters (non-ascii). If the user selects a string of text that contains non-ascii characters, then the edit won't save.

The solution
The best solution is to catch those non-ascii characters before the user clicks the edit button to bring up the fast edit dialog. Then we can fallback to the full composer to edit their text, which has much better support for non-ascii characters.

What does this regex do?
The regex used to catch this is [^\x00-\x7F], which matches any character that is not within the ASCII range of 0x00 to 0x7F, which includes all control characters and non-ASCII characters.

This regex pattern can be used to match any character that is not a standard ASCII character, such as accented characters, non-Latin characters, and special symbols.
2023-05-09 19:18:35 +08:00
..
assets FIX: fast-edit should fall back to composer for non-ascii characters (#21453) 2023-05-09 19:18:35 +08:00
controllers DEV: move sidebar community section to database (#21166) 2023-05-04 12:14:09 +10:00
helpers UX: Improve login required page (#20847) 2023-03-28 07:09:44 -05:00
jobs FEATURE: Add new notification for admin problems (#21287) 2023-05-03 19:35:22 +03:00
mailers DEV: Replace #pluck_first freedom patch with AR #pick in core (#19893) 2023-02-13 12:39:45 +08:00
models FIX: Change the limit on badges description 2023-05-09 11:41:40 +02:00
serializers DEV: move sidebar community section to database (#21166) 2023-05-04 12:14:09 +10:00
services PERF: Don't serialize value for theme_fields unnecessarily (#21201) 2023-04-24 09:30:51 -05:00
views UX: Include subcategories in crawler view (#21227) 2023-04-25 10:51:45 -04:00