User:GijsKruitbosch/OutreachyWinter2016: Difference between revisions
Jump to navigation
Jump to search
(Created page with "== Improve the first-run experience of Firefox's location bar == Mentor: [https://mozillians.org/u/gijs/ Gijs Kruitbosch] (Gijs on IRC) Background: Firefox's location bar cur...") |
m (→Improve the first-run experience of Firefox's location bar: fix list formatting) |
||
| Line 13: | Line 13: | ||
What you can do to get involved: | What you can do to get involved: | ||
* read through [https://bugzilla.mozilla.org/show_bug.cgi?id=1211726 the bug] and ask me any questions you have | |||
* set up the [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Simple_Firefox_build source tree] and create an [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Artifact_builds "artifact build"] of Firefox so you can quickly change JS, test it and submit patches; | |||
* try and understand how [https://dxr.mozilla.org/mozilla-central/source/toolkit/components/places/UnifiedComplete.js UnifiedComplete.js] deals with different engines and how you'd go about adding another one | |||
Revision as of 12:05, 28 September 2016
Improve the first-run experience of Firefox's location bar
Mentor: Gijs Kruitbosch (Gijs on IRC)
Background: Firefox's location bar currently uses your bookmarks, history and search engine to provide you with useful search results. When you're a new Firefox user, your bookmarks and history are empty, and so the initial experience can feel disorienting and unhelpful.
Project: We'd like to provide users with an initial set of "autocompletion" results that provide domains that they are likely to navigate to. So that even when you're a new user, if you type in "face", we autocomplete to "facebook.com", and so on.
Previous experience: You should be familiar with JavaScript. Previous experience with sqlite and mercurial or git would be helpful.
What you can do to get involved:
- read through the bug and ask me any questions you have
- set up the source tree and create an "artifact build" of Firefox so you can quickly change JS, test it and submit patches;
- try and understand how UnifiedComplete.js deals with different engines and how you'd go about adding another one