Places/Status Meetings/2009-11-30: Difference between revisions

(Created page with '<small>« previous week | index | next week »</small> '''Places…')
 
 
Line 43: Line 43:
* Bug Triage (1493, -, http://tinyurl.com/a3j9p6)
* Bug Triage (1493, -, http://tinyurl.com/a3j9p6)


===3.7 UI Triage===
===3.7 Projects===


* [https://wiki.mozilla.org/Firefox/UX_index UX priorities list]
* [https://wiki.mozilla.org/Firefox/UX_index UX priorities list]
* Places UI for 3.7 meta bug: {{bug|523519}}
* Places UI for 3.7 meta bug: {{bug|523519}} ([https://bugzilla.mozilla.org/showdependencytree.cgi?id=523519&hide_resolved=1 dependency tree])


 
* {{bug|522572}} new Query API (ddahl)
* {{bug|522572}} new Querying API
** Need to define how much of this is needed for the new awesomebar features
** Need to define how much of this is needed for the new awesomebar features
** https://wiki.mozilla.org/Firefox/Projects/PlacesQueryAPISketches
** https://wiki.mozilla.org/Firefox/Projects/PlacesQueryAPISketches


* {{bug|523523}} folders in the awesomebar
* {{bug|523523}} folders in the awesomebar (marco)
** mockup: [http://people.mozilla.com/~faaborg/files/20091012-personalWeb/navigateBookmarkFolder.png]
** mockup: [http://people.mozilla.com/~faaborg/files/20091012-personalWeb/navigateBookmarkFolder.png]
** we need to show containers in the awesomebar
** we need to show containers in the awesomebar
Line 61: Line 60:
** do we want a common Home breadcrumb wrapping history and bookmarks?
** do we want a common Home breadcrumb wrapping history and bookmarks?


* {{bug|523524}} awesomebar results in a content page
* {{bug|523524}} awesomebar results in a content page (drew)
** mockup: [http://people.mozilla.com/~faaborg/files/20091012-personalWeb/bookmarksInContent.png]
** mockup: [http://people.mozilla.com/~faaborg/files/20091012-personalWeb/bookmarksInContent.png]
** security policy: places api in a content page
** security policy: places api in a content page
Line 71: Line 70:
** Can split into 2 steps: first step static view with no user interaction, second step allow D&D, edit, etc. For first part we can use the same ideas Curtis is evaluating for RSS, we call content, but not viceversa.
** Can split into 2 steps: first step static view with no user interaction, second step allow D&D, edit, etc. For first part we can use the same ideas Curtis is evaluating for RSS, we call content, but not viceversa.


* {{bug|523526}} content area pages show up in session history
* {{bug|524050}} breadcrumb trail in awesomebar (mano)
** mockup: [http://people.mozilla.com/~faaborg/files/20091012-personalWeb/backForwardHistory.png]
** what protocol
** places should add
** session history should add
 
* {{bug|524049}} history ranges in awesome bar results
** mockup: [http://people.mozilla.com/~faaborg/files/20091012-personalWeb/navigateHistoryRange.png]
** language parser (ubiquity one looks too much)
** or stored/dynamic entries
** need to be localizable at runtime
 
* {{bug|524050}} breadcrumb trail in awesomebar
** show ancestor trail instead of uri
** show ancestor trail instead of uri
** optionally click on crumbs to navigate to them
** optionally click on crumbs to navigate to them
** see locationbar2 for impl ideas
** see locationbar2 for impl ideas


* {{bug|524060}} home tab should be able to link to content pages
* {{bug|524071}} detachable and resizable bookmark dialog (marco)
** queries as links (protocol handler again)
 
* {{bug|524068}} select folder in sidebar, toolbar, menu navigates to it's contents
** how for menus?
** mostly updating click handlers in the views
 
* {{bug|524071}} detachable and resizable bookmark dialog
 
* {{bug|526678}} Add "View all History" command to sessionhistory menu
** Optional for 3.7?


== QA Issues ==
== QA Issues ==
Confirmed users, Bureaucrats and Sysops emeriti
2,088

edits