could you write the bug in the following format?

What steps will reproduce the problem?
(1)
(2)
(3)

What is the expected output?

What do you see instead?

I am working on the new TranslateUI2016Q2 which is going to obsolete the current UI. It make no sense to fix any bug under the current UI but not a problem in the TranslateUI2016Q2 UI since the fix is already in the TranslateUI2016Q2 UI and we just need to switch to TranslateUI2016Q2 to address it.

TranslateUI2016Q2 is not guaranteed to be turned on, we need numbers and user feedback to prove it is good. Before it is launched, I think this bug should be fixed, otherwise it has negative impact to users and translate feature usage.

Also it is unfair to mix bug fix and new UI to prove new UI is better than old UI, the improvement may come from bug fix, and not the UI change. There is no way to tell if these two things are mixed.

Version: Version after 52.0.2729.0
OS: Windows

What steps will reproduce the problem?
(1)Visit a page that triggers translate bubble
(2)Click "Nope"
(3)Visit another page in the same language that triggers translate bubble
(4)Click "Nope"
(5)Visit another page that is the same language as the previous one
(6)Translate bubble does not show up
(7)Click Translate omni icon to translate this page
(8)Visit another page that is the same language as the previous one

What is the expected output?
Translate bubble shows up

What do you see instead?
Translate bubble does not show up.

Well... fixing the current state will surely improve the problem of the current state and therefore reduce the need to launch TranslateUI2016Q2 . So why should I do so to reduce the chance to get the launch of TranslateUI2016Q2 approved?

Notice the core of this issue is the triggering mechanism is so broken in the current UI, and TranslateUI2016Q2 is solution to fix it. It make no sense to figure another fix than TranslateUI2016Q2 for the same problem.

In the current UI, the behavior of turning off after two clicks on "nope" is the desired behavior.

The new UI is indeed the planned fix. If this is a high-priority bug that needs to be fasttracked, let's figure this out.

Julie: Can you please prioritize?

Lower to P3 since the new UI will fix it.

Yana, do we plan to do anything with this bug, or can we close it because "new UI is indeed the planned fix"?

if we do want to do something here, what is the solution?

The new UI will no longer fix this (they won't be launching changes to heuristics as per my latest convos with Barak) so we should be resetting the heuristics after the user triggers the UI from the Omnibar.

Fixed with the launch of Translate Ranker replacing suppression heuristics.