1. When editors need to tag a paragraph more than once, HTML doesn't let editors to highlight the repeated paragraph for the second time as shown in the video without having to "Save and Exit" every time.
2. Even if editors manage to highlight the same paragraph for the second time after clicking "Save and Exit," the side bubble doesn't necessarily appear correctly, which is misleading compared to Analysis List.
I am aware that I've added a lot of unplanned items, so please queue this accordingly as soon as possible.
As shown in the video below, the issue is not fully resolved. It might be because of the HTML on staging that I used (AF/0001/39 - ADF v. United States ADM-CPI - Darsh Test - 31 August 2021 - Croatian), but I am still unable to tag a paragraph that had been previously tagged already.
We believe the original issue has been addressed, but we are still chasing the behaviour you described in your last comment. So far, we have only been able to reproduce it using the document you referred to.
Darsh
is trying to reproduce with other HTML documents.
The plan is as follows:
Next week, we will install the original fix in Production.
Darsh
will attempt to reproduce the latest problem you reported. It might be specific to that one document, in which case we might decide to not pursue further. If Darsh is able to find a pattern using other HTML docs, we will create a new Bug in DevOps and link it back in this thread.
Thanks, -Martin
Notified 6 people
Paul Moon
Thanks,
Martin
.
I will test further once the original fix is implemented next week.
Hopefully, the AF/0001/39 problem I posted is document-specific. If it happens throughout all HTMLs, it will pose an issue, preventing editors from inserting SN entries correctly. Is there a way for the technical review can detect the problem if it depends on the HTML?
Paul
Notified 7 people
Martin Laporte,CTO
Hi
Paul
,
The challenge right now is that we believe it's document-specific, but we are not sure how to catch the issue. That is why Darsh has been testing against multiple HTMLs, trying to reproduce this.
Piyush
and
Darsh
, can you share more details on your latest findings? How confident are we that this is an isolated issue?
Thanks, --Martin
CC:
Harsh
Notified 7 people
Paul Moon
Understood,
Martin
.
Let's see what the team comes back with and decide what to do then.
Thank you.
Notified 7 people
Darsh Shah
Hi
Paul
and
Martin
,
I check this issue on multiple environments (QC and Staging) with multiple documents. And found that this is browser specific issue and I found that in the firefox browser (Version: 92.0).
Please check the attached video for more information.
Paul
, Can you please check and confirm that is working fine in the chrome browser?
Martin
, We will try to solve this issue as soon as possible.
Since this only occurs in Firefox, and only on the Admin app while performing specific steps, we have decided to lower the priority and address this issue after retiring ISLG Legacy.
In the meantime, we recommend the team uses Chrome or Edge when performing Admin functions.
Thanks, --Martin
CC:
Morgan
,
Harsh
,
Piyush
,
Darsh
Notified 7 people
Paul Moon
Thanks for the update,
Martin
.
Paul
Notified 7 people
Paul Moon
Hi
Martin
:
I tested on Firefox staging.islg, and this is my test result so far.
2. Even if editors manage to highlight the same paragraph for the second time after clicking "Save and Exit," the side bubble doesn't necessarily appear correctly, which is misleading compared to Analysis List.
I am aware that I've added a lot of unplanned items, so please queue this accordingly as soon as possible.
I have added a new item to the Product Backlog, and it will be picked up in the next sprint.
https://dev.azure.com/tologix/ISLGRebuild/_workitems/edit/956
Thanks,
--Martin
This issue is resolved on staging.islg. Please check and confirm.
https://dev.azure.com/tologix/ISLGRebuild/_workitems/edit/956
cc:
As shown in the video below, the issue is not fully resolved. It might be because of the HTML on staging that I used (AF/0001/39 - ADF v. United States ADM-CPI - Darsh Test - 31 August 2021 - Croatian), but I am still unable to tag a paragraph that had been previously tagged already.
Thanks,
Paul
We believe the original issue has been addressed, but we are still chasing the behaviour you described in your last comment.
So far, we have only been able to reproduce it using the document you referred to.
The plan is as follows:
-Martin
I will test further once the original fix is implemented next week.
Hopefully, the AF/0001/39 problem I posted is document-specific. If it happens throughout all HTMLs, it will pose an issue, preventing editors from inserting SN entries correctly. Is there a way for the technical review can detect the problem if it depends on the HTML?
Paul
The challenge right now is that we believe it's document-specific, but we are not sure how to catch the issue. That is why Darsh has been testing against multiple HTMLs, trying to reproduce this.
Thanks,
--Martin
CC:
Let's see what the team comes back with and decide what to do then.
Thank you.
I check this issue on multiple environments (QC and Staging) with multiple documents.
And found that this is browser specific issue and I found that in the firefox browser (Version: 92.0).
Please check the attached video for more information.
CC:
Yes, it seems to work on Chrome. It shouldn't matter which browser admin users use, so please ensure it'd work on Firefox as well.
Thanks,
Paul
We should ensure this is compatible with all major browsers (Chrome, Edge, Firefox and Safari).
Thanks,
Morgan
Since this only occurs in Firefox, and only on the Admin app while performing specific steps, we have decided to lower the priority and address this issue after retiring ISLG Legacy.
In the meantime, we recommend the team uses Chrome or Edge when performing Admin functions.
Thanks,
--Martin
CC:
Paul
I tested on Firefox staging.islg, and this is my test result so far.
Thanks,
Paul
Please see Paul's latest video and let us know how you'd like to proceed next.
I can move https://dev.azure.com/tologix/ISLGRebuild/_workitems/edit/1025 into the current sprint if necessary.
Thanks,
--Martin
Can the issue you reported above be also reproduced in Chrome? Or is it specific to Firefox?
Thanks,
--Martin
CC:
This issue is specific to Firefox. It is not an issue on Chrome.
Thanks,
Paul
Just an FYI that I have moved this issue from Sprint 9 to the current sprint, so it is still on our radar.
https://dev.azure.com/tologix/ISLGRebuild/_workitems/edit/1025
Thanks,
--Martin