[zanata-bugs] [Bug 875973] New: [WebTrans] filter by content state with unsaved change will cause two save event

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=875973

            Bug ID: 875973
        QA Contact: dchen at redhat.com
          Severity: unspecified
           Version: development
          Priority: unspecified
                CC: zanata-bugs at redhat.com
          Assignee: runab at redhat.com
           Summary: [WebTrans] filter by content state with unsaved change
                    will cause two save event
        Regression: ---
      Story Points: ---
    Classification: Community
                OS: Unspecified
          Reporter: pahuang at redhat.com
              Type: Bug
     Documentation: ---
          Hardware: Unspecified
        Mount Type: ---
            Status: NEW
         Component: Component-Logic
           Product: Zanata

Description of problem:
When user has unsaved change in editor and check the filter by state checkbox,
a pop up will be displayed and asking user to save or discard current change
before continue the filtering. Depending on the timing, the filtering load may
happen in the middle of the saving and cause another pending save. See below
for more information.

Version-Release number of selected component (if applicable):
2.0-

How reproducible:
Depending on the event timing and ordering

Steps to Reproduce:
1. Go to translation editor and type something in one row with approved
translation (row indicates unsaved)
2. Click on Message filters option on editor options panel and select
Translated 
3. In the filter confirmation pop up, select save as fuzzy
4. If you are in slow network, the saving indicator will appear quite a while
and during "saving", the filter may finish earlier than the save and therefore
override current saving row with old value.

Actual results:
After filter reload, before reload current page it will try to re-select
current row and sees that current row has unsaved change, it will trigger
another pending save event and push into saving queue. Then reload the page and
override value to old value. So what you see from translation history is:
one fuzzy save(triggered by filter confirmation pop up)
one approved save(triggered by implicit pending change save)
unsaved change(after reload page editor value gets set back to original)

Expected results:
The active row should be saved as fuzzy only.

Additional info:

-- 
You are receiving this mail because:
You are on the CC list for the bug.