Confirmed users
507
edits
Search: Difference between revisions
m
→Sign-offs
No edit summary |
m (→Sign-offs) |
||
| (6 intermediate revisions by 4 users not shown) | |||
| Line 16: | Line 16: | ||
* '''P2) Extend Glow:''' anecdotal evidence suggests that the blue glow effect notification for Search Engines is not providing sufficient guidance to users. Many users are opening the menu but are confused by what the glow means as it isn't tied to any item within the menu. We would like to see the glow applied to the "Add..." item, either to the full item or just to the favicon. | * '''P2) Extend Glow:''' anecdotal evidence suggests that the blue glow effect notification for Search Engines is not providing sufficient guidance to users. Many users are opening the menu but are confused by what the glow means as it isn't tied to any item within the menu. We would like to see the glow applied to the "Add..." item, either to the full item or just to the favicon. | ||
* '''P2) Rich Results:''' Myk has developed a quick example of a search that returns rich results when available - his example search for ''firefox tinderbox'' returns a "balloon help" like bubble with an abbreviated version of the Tinderbox page for Firefox. | * '''P2) Rich Results:''' Myk has developed a quick example of a search that returns rich results when available - his example search for ''firefox tinderbox'' returns a "balloon help" like bubble with an abbreviated version of the Tinderbox page for Firefox. A more detailed proposal for incorporating this functionality is available at [[Search/Rich Results]]. | ||
== Rejected Concepts == | == Rejected Concepts == | ||
| Line 113: | Line 113: | ||
'-------------------------' | '-------------------------' | ||
1) Rich results are returned in the submenu, so opening this item will actually show a container for the "Weather in Mountain..." results. | 1) Rich results are returned in the submenu, so opening this item will actually show a container for the "Weather in Mountain..." results. The container should be able to display HTML content, since rich results will generally be HTML pages loaded from a server or constructed on the fly by a rich result provider. For more information, see the proposal at [[Search/Rich Results]]. | ||
2) '''Team: thoughts on what this does? It looks like, from our mockup, we intended for the Suggestions and History sections to execute the search and pull back the results, interpreted and displayed in the submenu. Is that right?''' | 2) '''Team: thoughts on what this does? It looks like, from our mockup, we intended for the Suggestions and History sections to execute the search and pull back the results, interpreted and displayed in the submenu. Is that right?''' | ||
| Line 140: | Line 140: | ||
| [M] Use MSN Search /M | | | [M] Use MSN Search /M | | ||
'-------------------------' | '-------------------------' | ||
== Questions == | == Questions == | ||
There were a few unanswered questions from our session: | There were a few unanswered questions from our session: | ||
* '''Keyword Shortcuts''': the concept of enabling users to enter a keyword shortcut for different Search Engines was proposed in m.d.a, but not discussed in our conversation. We could extend our proposed design to allow users to enter "/x" in the Location or Search Bars to search using that engine. For example: | |||
/W mozilla | /W mozilla | ||
| Line 150: | Line 150: | ||
in either Bar would do a Wikipedia search based on the mockups above. | in either Bar would do a Wikipedia search based on the mockups above. | ||
* '''Site Search''': the concept of using the Search Bar to do a search on the current site (using the site's own search) or a find on the current page was also raised in m.d.a. Sites already have the ability to integrate their site search by writing an OpenSearch plugin, but Find on the page could be added as an 'engine': | |||
.......................... | .......................... | ||
| Line 174: | Line 174: | ||
which could then bring up the Find bar at the bottom of the window, pre-populate the Search Term, and find the first instance. | which could then bring up the Find bar at the bottom of the window, pre-populate the Search Term, and find the first instance. | ||
* '''Setting/Changing default engine''': If we believe that the common case is a single, long-term, default search with a lot of "one-off" searches, then we could consider removing the search engine default switching menu in favor of a "manage search engines" at the bottom of the search popup, or other alternative methods. | |||
* '''Multiple suggests''': Should we expose suggests for more than one engine if available? I think we said no, but bringing it up just in case. | |||
* '''Search Options''': Myk has suggested that we rename the History/Suggestions box to Search Options, which is more inclusive of the new content. I (Jay) think that makes a lot of sense. Thoughts? | |||
= Search field to the new tab page in Firefox 31 = | |||
== Intro == | |||
A search field is added on the top of the new tab page to make users search experience more fluid. Same as the search field from the awesome bar, the search engines can be modified, removed or managed. | |||
== Testing approach == | |||
The new search field will be tested on all platforms to check that the Search Engine can be changed using the button, the Search field can be resized and the searches are working properly. | |||
== MozTrap tests == | |||
The manual test cases for this feature can be seen [https://moztrap.mozilla.org/manage/cases/?filter-suite=601 here] | |||
== Bug work == | |||
* Metabug: [https://bugzilla.mozilla.org/show_bug.cgi?id=962490 962490] | |||
* top level metabug: [https://bugzilla.mozilla.org/show_bug.cgi?id=1006203 1006203] | |||
* Important bugs: | |||
**[https://bugzilla.mozilla.org/show_bug.cgi?id=959576 959576] | |||
**[https://bugzilla.mozilla.org/show_bug.cgi?id=959571 959571] | |||
**[https://bugzilla.mozilla.org/show_bug.cgi?id=959579 959579] | |||
**[https://bugzilla.mozilla.org/show_bug.cgi?id=959558 959558] | |||
== Sign-offs == | |||
* Merge-to-Nightly Sign-off - [https://wiki.mozilla.org/SearchProviderSuggestions/Test_Plan#Firefox_31.0a2_Aurora_-_20140502004003_.28aurora_merge_sign_off.29_-_02.2F05.2F2014 here] | |||
* Merge-to-Aurora Sign-off - [https://wiki.mozilla.org/SearchProviderSuggestions/Test_Plan#Firefox_31.0a2_Aurora_-_20140605004002_.28pre-beta_sign_off.29_-_06.2F06.2F2014 here] | |||
* Merge-to-Beta Sign-off - [https://wiki.mozilla.org/SearchProviderSuggestions/Test_Plan#Firefox_31_beta_8_-_20140707160635_.28beta_sign_off.29_-_09.2F07.2F2014 here] | |||
= Search Suggestions in Start and New Tab Page in Firefox 33 = | |||
== Intro == | |||
Search Suggestions will be shown in the search field of the New Tab Page (about:newtab) for all search engines that support this. </br> | |||
Search Suggestions will be shown in the search field of the Home Page (about:home) for all search engines that support this. | |||
== Testing approach == | |||
Starting with Firefox 33, search suggestions will be shown in the search field of the Home Page (about:home) and New Tab Page (about:newtab) for all search engines that support this. For en-US builds there are no search suggestions for Twitter. | |||
== One and Done tasks == | |||
One and Done tasks contains the Moztrap testcases for verifying search suggestions: | |||
https://oneanddone.mozilla.org/tasks/61/ | |||
https://oneanddone.mozilla.org/tasks/62/ | |||
== MozTrap tests == | |||
The manual test cases for this feature can be seen [https://moztrap.mozilla.org/manage/cases/?filter-suite=759 here] | |||
== Bug work == | |||
* Metabug: [https://bugzilla.mozilla.org/show_bug.cgi?id=1028985 1028985] | |||
* Metabug: [https://bugzilla.mozilla.org/show_bug.cgi?id=612453 612453] | |||
* top level bug: [https://bugzilla.mozilla.org/show_bug.cgi?id=1054516 1054516] | |||
* Important bugs: | |||
**[https://bugzilla.mozilla.org/show_bug.cgi?id=1007979 1007979] | |||
**[https://bugzilla.mozilla.org/show_bug.cgi?id=1048198 1048198] | |||
<div class="toccolours mw-collapsible mw-collapsed" style="width:auto"> | |||
* All bugs: | |||
<div class="mw-collapsible-content"> | |||
<bugzilla> | |||
{ | |||
"product":"Firefox", | |||
"component":"Search" | |||
} | |||
</bugzilla></div> | |||
</div> | |||
<div class="toccolours mw-collapsible mw-collapsed" style="width:auto"> | |||
* Fixed; may need verification:. | |||
<div class="mw-collapsible-content"> | |||
<bugzilla> | |||
{ | |||
"include_fields":"id,summary,qa_contact,status,resolution,cf_qa_whiteboard", | |||
"product":"Firefox", | |||
"component":"Search", | |||
"status":"RESOLVED", | |||
"resolution":"FIXED" | |||
} | |||
</bugzilla></div> | |||
</div> | |||
<div class="toccolours mw-collapsible mw-collapsed" style="width:auto"> | |||
* Unconfirmed bugs: | |||
<div class="mw-collapsible-content"> | |||
<bugzilla> | |||
{ | |||
"include_fields":"id,summary,qa_contact,status,resolution,cf_qa_whiteboard", | |||
"product":"Firefox", | |||
"component":"Search", | |||
"status":"UNCONFIRMED" | |||
} | |||
</bugzilla></div> | |||
</div> | |||
== Sign-offs == | |||
* Merge-to-Aurora Sign-off [https://wiki.mozilla.org/SearchProviderSuggestions/Test_Plan#Firefox_33.0a2_Aurora_-_20140828004002_.28aurora_merge_sign_off.29_-_2014.2F08.2F29 here] | |||
* Pre-release Sign-off [https://wiki.mozilla.org/SearchProviderSuggestions/Test_Plan#Firefox_33_Beta_.28pre-release_sign_off.29_-_2014.2F10.2F06 here] | |||