Javascript translation issue on modal buttons when removing items from product compare page

[mfickers]

Preconditions

1. Magento 2.3.0 Open Source
2. At least one product available in store
3. A translation file for the luma theme and storefront locale containing the phrase "Cancel","Test"
4. Static Content is deployed for the right locale and the translation cache is cleaned

Steps to reproduce

1. Add an item to product compare list
2. Go to product compare page
3. Click on the remove item icon

Expected result

1. A modal pops up asking to confirm the removal
2. The left button of this modal should have the text "Test" on it

Actual result

1. The text of the left modal button is "Cancel"

Additional information

The very first item in my js-translation.json is "Cancel":"Test", so this is not the issue.

When mage/translate.js is called from modal/confirm.js the _data[] array is empty:

During the same page load, it will be loaded containing all phrases from the js-translation.json including the right phrase:

[magento-engcom-team]

Hi @mfickers. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento-engcom-team give me $VERSION instance

where $VERSION is version tags (starting from 2.2.0+) or develop branches (for example: 2.3-develop).
For more details, please, review the Magento Contributor Assistant documentation.

@mfickers do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

[magento-engcom-team]

Hi @engcom-backlog-nazar. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 6. Add label Issue: Confirmed once verification is complete.

• 7. Make sure that automatic system confirms that report has been added to the backlog.

[magento-engcom-team]

@engcom-backlog-nazar Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-97061 were created

[mfickers]

There is already this pull request which fixed the same issue in 2.2, the fix was ported to 2.3, but does not seem to work anymore.

[mfickers]

@magento-engcom-team give me 2.3.0 instance