There are a couple issues with matching addon suggestions in remote settings right now. The keywords in remote settings are full keywords. We do have `addons.minKeywordLength` and the related Nimbus variable, but the keywords added to the suggestions map don't take it into account. This means a suggestion from RS can only be matched by typing a full keyword. I confirmed with Nive what the expected matching behavior should be, and it's now documented in the spec. In summary, an addon suggestion can be triggered by typing the first word in one of its full keywords. After the user clicks "Show less frequently", they must type the first word plus a number of characters equal to the number of times they clicked it.
Bug 1836582 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
There are a couple issues with matching addon suggestions in remote settings right now. The keywords in remote settings are full keywords. We do have `addons.minKeywordLength` and the related Nimbus variable, but the keywords added to the suggestions map don't take it into account. This means a suggestion from RS can only be matched by typing a full keyword. I confirmed with Nive what the expected matching behavior should be, [and it's now documented in the spec](https://docs.google.com/document/d/1XdEfA2Yr7x060hjCFo2dDBHfgBrVwH3on8OvKkRNL24/edit?usp=sharing). In summary, an addon suggestion can be triggered by typing the first word in one of its full keywords. After the user clicks "Show less frequently", they must type the first word plus a number of characters equal to the number of times they clicked it.
There are a couple issues with matching addon suggestions in remote settings right now. The keywords in remote settings are full keywords. We do have `addons.minKeywordLength` and the related Nimbus variable, but the keywords added to the suggestions map don't take it into account. This means a suggestion from RS can only be matched by typing a full keyword. I confirmed with Nive what the expected matching behavior should be, [and it's now documented in the spec](https://docs.google.com/document/d/1XdEfA2Yr7x060hjCFo2dDBHfgBrVwH3on8OvKkRNL24/edit?usp=sharing). In summary, an addon suggestion can be triggered by typing the first word in one of its full keywords. After the user clicks "Show less frequently", they must type the first word plus a number of characters equal to the number of times they clicked it. https://mozilla-hub.atlassian.net/browse/SNT-727