Places/Status Meetings/2009-11-16
From MozillaWiki
« previous week | index | next week »
Places Team Meeting Details
- Mondays at 9:00am Pacific
- irc.mozilla.org #places
Work Priorities
- TSnap bugs (72, -, http://is.gd/1isPz)
- TSnap fixed (33, -, http://is.gd/2mIBl)
- Requiring tests (in-testsuite?) (90, -, http://is.gd/2mIK6)
- Blocking 3.5.x (0, -, http://is.gd/2mLhE)
- Blocking 3.5.x Noms (0, -, http://is.gd/2mLmy)
- Wanted 3.5.x (0, -, http://is.gd/1ivdV)
- Wanted 3.5.x Noms (0, -, http://is.gd/1ivcd)
- Needs 3.5.x approval (0, -, http://is.gd/2mMp4)
- Blocking 3.6.x (0, -, http://is.gd/2PUQv)
- Blocking 3.6.x Noms (3, -, http://is.gd/2mJMz)
- Wanted 3.6.x (38, -, http://is.gd/2mJUi)
- Wanted 3.6.x Noms (39, -, http://is.gd/2mJSi)
- Needs 3.6.x approval (10, -, http://is.gd/2mK7n)
- Blocking 3.7.x (0, -, http://is.gd/2PVbs)
- Blocking 3.7.x Noms (0, -, http://is.gd/2PVj6)
- Wanted 3.7.x (0, -, http://is.gd/2PVt6)
- Wanted 3.7.x Noms (0, -, http://is.gd/2PVwQ)
- Needs 3.7.x approval (0, -, http://is.gd/2PVAp)
- Needs 1.9.1.x landing (0, -, http://is.gd/2mL9D)
- Needs 1.9.2.x landing (0, -, http://is.gd/3MzfJ)
- Trunk delta from 1.9.1 branch (159, -, http://tinyurl.com/oxno27)
- Trunk delta from 1.9.2 branch (43, -, http://is.gd/3fURh)
- Possible Wontfix (67, -, http://tinyurl.com/ajqgm7)
- Bug Triage (1493, -, http://tinyurl.com/a3j9p6)
3.7 UI Triage
- UX priorities list
- Places UI for 3.7 meta bug: bug 523519
- bug 522572 new Querying API
- Need to define how much of this is needed for the new awesomebar features
- https://wiki.mozilla.org/Firefox/Projects/PlacesQueryAPISketches
- bug 523523 folders in the awesomebar
- mockup: [1]
- we need to show containers in the awesomebar
- impl?: expose place: protocol handler
- show ancestors of a container for display (“restaurants > japanese > sushi”)
- need to create frecency algo for containers/queries (“visits” to a folder)
- do we want a common Home breadcrumb wrapping history and bookmarks?
- bug 523524 awesomebar results in a content page
- mockup: [2]
- security policy: places api in a content page
- thumbnail service
- static or liveupdate (static fine for 3.7)
- no editing, context menu
- click to open, that is all
- We want async containers to avoid locking up everything
- 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
- mockup: [3]
- what protocol
- places should add
- session history should add
- bug 524049 history ranges in awesome bar results
- mockup: [4]
- 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
- optionally click on crumbs to navigate to them
- see locationbar2 for impl ideas
- bug 524060 home tab should be able to link to content pages
- 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
From last week, the following things had open action items:
Status updates
From last week, the following things had open action items: