Hmm, my perception was that this was a somewhat-recent issue, but it looks like this issue actually predates Firefox Suggest; I can reproduce the same issue in Nightly 2018-01-01, using our AwesomeBar suggestions in that version. (Maybe my misperception was based on my increasing usage of Google Docs; or maybe Google Docs only recently started using fragment identifiers for header-text? *shrug*)
Bug 1753747 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Hmm, my perception was that this was a somewhat-recent issue, but it looks like this issue actually predates Firefox Suggest; I can reproduce the same issue in Nightly 2018-01-01, using our AwesomeBar suggestions in that version. (many duplicate history suggestions, no switch-to-tab suggestion) (Maybe my misperception was based on my increasing usage of Google Docs; or maybe Google Docs only recently started using fragment identifiers for header-text? *shrug*)
Hmm, my perception was that this was a somewhat-recent issue, but it looks like this issue actually predates Firefox Suggest; I can reproduce the same issue in Nightly 2018-01-01, using our AwesomeBar suggestions in that version. (many duplicate history suggestions, no switch-to-tab suggestion) (Maybe my misperception about this issue being newly-introduced was based on my increasing usage of Google Docs; or maybe Google Docs only recently started using fragment identifiers for header-text? *shrug*)
Hmm, my perception was that this was a somewhat-recent issue, but it looks like this issue actually predates Firefox Suggest; I can reproduce the same issue in Nightly 2018-01-01, using our AwesomeBar suggestions in that version. (many duplicate history suggestions, no switch-to-tab suggestion) (Maybe my misperception about this issue being newly-introduced was based on my increasing usage of Google Docs; or maybe Google Docs only recently started using fragment identifiers for header-text? `*shrug*`)