Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Give WebExtensions higher priority on search results #4360

Closed
jvillalobos opened this issue May 17, 2017 · 7 comments · Fixed by mozilla/addons-server#5448
Closed

Give WebExtensions higher priority on search results #4360

jvillalobos opened this issue May 17, 2017 · 7 comments · Fixed by mozilla/addons-server#5448
Assignees
Milestone

Comments

@jvillalobos
Copy link

As part of the transition to Firefox 57, at some point we need to give WebExtensions higher ranking in search results, to encourage users to install WebExtensions over legacy extensions. This behavior should be gated by a waffle flag since the timing to make it live on prod isn't clear yet.

@diox
Copy link
Member

diox commented May 17, 2017

Easy enough, we just need to figure out a boost value that works. We should be able to do this at runtime I think, just adding a should clause with the appropriate boost if the waffle is turned on.

@ValentinaPC
Copy link

Verified this on AMO-dev FF53(Win 7) while enabling the waffle "boost-webextensions-in-search".
Searching after "permissions" search term will boost the webextensions through the first page of search results and leave the legacy add-ons at the end, but not sure if interfering with the "name-match boost"?

Made 2 screenshots with and without the waffle:
untitled

@diox : do you think is ok?

@diox
Copy link
Member

diox commented May 19, 2017

It's ok. We might tweak the boost to give them an even bigger priority, we'll look into that when enabling it.

@ValentinaPC
Copy link

Looking forward :)

@muffinresearch
Copy link
Contributor

@jvillalobos do you know when you want to turn this on?

@jvillalobos
Copy link
Author

I'd say the hard deadline is when 57 hits beta (09-26), but we should probably turn it on a couple of weeks earlier to make sure it's working well. Doing it too early might alienate some legacy add-on devs.

@jvillalobos
Copy link
Author

This is now live in prod.

@KevinMind KevinMind transferred this issue from mozilla/addons-server May 4, 2024
@KevinMind KevinMind added repository:addons-server Issue relating to addons-server migration:2024 labels May 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants