Forceful conversion to numbered lists in messages causes messages to change in meaning
See original GitHub issueSteps to reproduce
- Someone asks me a question:
We have three choices here:
1. Pizza with pineapple
2. Sushi
3. Ramen
What do you want to eat?
- I answer:
2. sounds good
- I’m brought pizza with pineapple because Element Android changed my
2.
to1.
due to its internal conversion to numbered list (with a single item)
This is incredibly awful.
Outcome
What did you expect?
That my message is displayed how it was sent.
What happened instead?
The meaning of my message was changed.
Operating system version
Android 10
Application version and app store
1.3.9
Homeserver
matrix.org
Issue Analytics
- State:
- Created 2 years ago
- Reactions:9
- Comments:12 (8 by maintainers)
Top Results From Across the Web
Fix text-formatted numbers by applying a number format
Technique 1: Convert text-formatted numbers by using Error Checking ; A large range of cells. Click the first cell in the range, and...
Read more >Understanding Success Criterion 4.1.3: Status Messages
The scope of this Success Criterion is specific to changes in content that involve status messages. A status message is a defined term...
Read more >Error Messages: Examples, Best Practices & Common Mistakes
Useful error messages can keep users on your site and increase conversions. See examples and learn the best practices.
Read more >RFC 2822: Internet Message Format
RFC 2822 Internet Message Format April 2001 to handle an arbitrarily large number of characters in a line (certainly at least up to...
Read more >Warning Options (Using the GNU Compiler Collection (GCC))
Limits the maximum number of error messages to n , at which point GCC bails out ... This option causes the compiler to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
it is really horrible when you try to make an appointment and e.g. suggest “4. April” and depending whether the other person(s) use(s) element web, android, or iOS, they see “1. April”. Then suddenly on 1. April you get a call why you’re late.
How is this only a minor issue? This makes element unusable on Android.