[Bug] User Experience (UX) Tragedy: Flawed UI Design Resulting in Data Loss

[JuryA]

As an accomplished open-source project developer, I find it my obligation to address a pressing concern pertaining to the User Experience (UX) encountered within the environment. The essence of this issue is intrinsically tied to a fragile User Interface (UI), manifesting in the form of an operational window. A poignant drawback emerges as this window, devoid of forewarning, abruptly terminates upon the user's interaction with any region lying external to its confines. This includes seemingly innocuous actions such as clicking anywhere outside the window, even within the browser bookmarks. This lamentable occurrence engenders the untimely forfeiture of valuable data, rendering the user's efforts and inputs naught.

Steps to Reproduce:

1. Launch the application or designated interface.
2. Initiate a sequence of prompts or actions within the UI.
3. Progress to a point where user inputs or data are solicited.
4. Attempt to interact with any region outside the operational window.
5. Observe the window's unexpected and unannounced closure.
6. Realize that the data, painstakingly inputted thus far, has been irrevocably lost.

Expected Behavior:

The UI should ideally incorporate a more robust design, wherein the operational window remains impervious to inadvertent closure triggered by interactions external to its boundaries. This is essential to preserve user data and ensure a seamless and uninterrupted workflow.

Proposed Solution:

To address this concerning deficiency in UX, a couple of potential solutions are worth considering:

1. Enhanced Window Behavior: Modify the UI to ensure that the operational window remains open despite interactions outside its confines. This will prevent inadvertent closure and data loss.

2. Background Operation Persistence: Implement a mechanism whereby the extension continues its operation in the background, allowing users to interact with other elements without risk of losing data. Upon returning to the operational window, users can seamlessly resume their tasks.

Additional Notes:

While it is noteworthy that the issue has been observed on a private, corporate, self-hosted GitLab instance, the focus here is on the broader concept of User Experience design and its implications. The mentioned GitLab instance serves merely as a reference for context.

I look forward to collaborative efforts to resolve this UX predicament, thus contributing to the enhancement of our product's overall usability and appeal. Your consideration and attention to this matter are greatly appreciated.

[JuryA]

Update:

After several attempts, I encountered issues generating a Code Review for a Merge Request (MR). Here's a concise summary of the problems faced:

1. Issue: Attempts were interrupted due to inadvertent clicks outside the extension window.

   • Resolution: Enhance the UI to prevent accidental closures and ensure a smooth user experience.

2. Issue: A TypeError error disrupted a Code Review generation attempt.

   • Resolution: Investigate and address the root cause of the TypeError error to enable uninterrupted progress.

3. Issue: A token limit resulted in a failed attempt.

   • Resolution: Review the token limit policy, considering adjustments or informative prompts. Also, don't waste money and reuse already obtained and processed data.

My Token Expenditure:

Approximately 281,498 tokens in total, costing $0.56, were expended literally for nothing.

Screenshot (last attempt):

Hope it will help to improve this awesome extension to a higher level... 😉