Given the fact that the reproduction STR for this bug on an affected build (69.0a1 20190613095633) were intermittent, I've reused a modified profile that has very long URL browsing history (check here the details: https://bugzilla.mozilla.org/show_bug.cgi?id=1540861#c13) and with that profile, I can reproduce this report reliably with the following STR without any timing prerequisite, which I further used to verify the fixes: #### [Steps:] 1. Start Fx with the attached profile. 2. (baseline)In address bar type "freakinghugeurl". 3. (baseline)Using down-arrow key to navigate throughout the results. 4. Open a new tab and type "freaking": the 1st suggestion should be freaking 5. Down-arrow key and select it, afterwhich continue writing hugeurl (now the addressbar will be: freakinghugeurl) 6. Down-arrow key to navigate through the results. #### [Actual Result:] 70.0a1 20190716211651, all good: step 3 and 6 navigate through all results. 69.0b5 20190715173502, still reproducible (the last results are skipped) 68.0 2019-07-05, still reproducible (the last results are skipped) 68.0esr 2019-07-05, still reproducible (the last results are skipped) I'm guessing, the attached profile is catching also bug 1563812? That would explain why 70 works properly and <70 still exhibit the issue. I'm uncertain how to proceed with marking the flags for this issue, since IMO, if the above testing approach is correct bug 1523602 seems to be necessary to fully verify this. Drew, can you take a look over the above and advise?
Bug 1559179 Comment 22 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Given the fact that the reproduction STR for this bug on an affected build (69.0a1 20190613095633) were intermittent, I've reused a modified profile that has very long URL browsing history (check here the details: https://bugzilla.mozilla.org/show_bug.cgi?id=1540861#c13) and with that profile, I can reproduce this report reliably with the following STR without any timing prerequisite, which I further used to verify the fixes: #### [Steps:] 1. Start Fx with the attached profile. 2. (baseline)In address bar type "freakinghugeurl". 3. (baseline)Using down-arrow key to navigate throughout the results. 4. Open a new tab and type "freaking": the 1st suggestion should be freaking 5. Down-arrow key and select it, afterwhich continue writing hugeurl (now the addressbar will be: freakinghugeurl) 6. Down-arrow key to navigate through the results. #### [Actual Result:] 70.0a1 20190716211651, all good: step 3 and 6 navigate through all results. 69.0b5 20190715173502, still reproducible (the last results are skipped) 68.0 2019-07-05, still reproducible (the last results are skipped) 68.0esr 2019-07-05, still reproducible (the last results are skipped) Environments: Ubuntu 16.04 and Mac 10.14. (didn't test on Win10 since that OS was covered already and I don't think this is OS dependent) I'm guessing, the attached profile is catching also bug 1563812? That would explain why 70 works properly and <70 still exhibit the issue. I'm uncertain how to proceed with marking the flags for this issue, since IMO, if the above testing approach is correct bug 1523602 seems to be necessary to fully verify this. Drew, can you take a look over the above and advise?
Given the fact that the reproduction STR for this bug on an affected build (69.0a1 20190613095633) were intermittent, I've reused a modified profile that has very long URL browsing history (check here the details: https://bugzilla.mozilla.org/show_bug.cgi?id=1540861#c13) and with that profile, I can reproduce this report reliably with the following STR without any timing prerequisite, which I further used to verify the fixes: #### [Steps:] 1. Start Fx with the attached profile. 2. (baseline)In address bar type "freakinghugeurl". 3. (baseline)Using down-arrow key to navigate throughout the results. 4. Open a new tab and type "freaking": the 1st suggestion should be freaking 5. Down-arrow key and select it, afterwhich continue writing hugeurl (now the addressbar will be: freakinghugeurl) 6. Down-arrow key to navigate through the results. #### [Actual Result:] 70.0a1 20190716211651, all good: step 3 and 6 navigate through all results. 69.0b5 20190715173502, still reproducible (the last results are skipped) 68.0 2019-07-05, still reproducible (the last results are skipped) 68.0esr 2019-07-05, still reproducible (the last results are skipped) Environments: Ubuntu 16.04 and Mac 10.14. (didn't test on Win10 since that OS was covered already and I don't think this is OS dependent) I'm guessing, the attached profile is catching also bug 1563812? That would explain why 70 works properly and <70 still exhibit the issue. I'm uncertain how to proceed with marking the flags for this issue, since IMO, if the above testing approach is correct bug 1563812,seems to be necessary to fully verify this. Drew, can you take a look over the above and advise?
Given the fact that the reproduction STR for this bug on an affected build (69.0a1 20190613095633) were intermittent, I've reused a modified profile that has very long URL browsing history (check here the details: https://bugzilla.mozilla.org/show_bug.cgi?id=1540861#c13) and with that profile, I can reproduce this report reliably with the following STR without any timing prerequisite, which I further used to verify the fixes: #### [Steps:] 1. Start Fx with the attached profile. 2. (baseline)In address bar type "freakinghugeurl". 3. (baseline)Using down-arrow key to navigate throughout the results. 4. Open a new tab and type "freaking": the 1st suggestion should be freaking 5. Down-arrow key and select it, afterwhich continue writing hugeurl (now the addressbar will be: freakinghugeurl) 6. Down-arrow key to navigate through the results. #### [Actual Result:] 70.0a1 20190716211651, all good: step 3 and 6 navigate through all results. 69.0b5 20190715173502, still reproducible (the last results are skipped) 68.0 2019-07-05, still reproducible (the last results are skipped) 68.0esr 2019-07-05, still reproducible (the last results are skipped) Environments: Ubuntu 16.04 and Mac 10.14. (didn't test on Win10 since that OS was covered already and I don't think this is OS dependent) I'm guessing, the attached profile is catching also bug 1563812? That would explain why 70 works properly and <70 still exhibit the issue. I'm uncertain how to proceed with marking the flags for this issue, since IMO, if the above testing approach is correct bug 1563812 seems to be necessary to fully verify this. Drew, can you take a look over the above and advise?