sillsdev / sillsdev/languageforge-lexbox
Poor UX when "Try FW Lite" button fails with C# stacktrace
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 9
- Forks
- 8
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 49
Description
Describe the bug
If the "Try FW Lite" button fails because of a C# error, the stacktrace is currently impossible for users to read. Here's what it looks like:
It would be good to add some CSS to the dialog to put an overflow scrollbar on the error message, rather than the current CSS that trims it and makes it impossible to select. (Unless you know how to open the dev tools and copy the HTML, which 99.8% of users won't know how to do).
To Reproduce
Steps to reproduce the behavior:
- Ensure that the initial sync of a project will throw a C# exception, perhaps by deliberately adding a
throw new Exception("Oops");line somewhere in the sync code - Click on "Try FieldWorks Lite" button in sena-3 project
- Wait for sync to fail
- See error message in dialog
Expected behavior
Error message would be scrollable and selectable, so that users can copy and paste it into an email.
For bonus points, the mailto link could automatically include the error message (and associated stacktrace) in the body=blahblah query string, so that most email programs will populate the email and save the user some copy-and-paste work. This will likely end up giving us more info if/when users run into error messages and click that link.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the "Try FieldWorks Lite" dialog and the CSS or component responsible for displaying the C# error message. Reproduce a failed sync in the sena-3 project, then verify that the complete error and stacktrace can be scrolled, selected, and copied; the mailto enhancement is optional bonus scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, css
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100