Difference between revisions of "Status Meetings:2006-12-06:Agenda"
Jump to navigation
Jump to search
(→Specific bugs that need action: putting it first because it's 1.1 targeted) |
|||
Line 10: | Line 10: | ||
==Specific bugs that need action== | ==Specific bugs that need action== | ||
+ | * {{bug|327203}} - First item in pref pane gets focus even when OS pref says not to | ||
+ | ** ''Is my hack OK (since it's highly unlikely there will ever be a prefpane with a single element, and it doesn't do anything catastrophic if there is)? If not, does anybody have a better solution?'' [[User:Froodian|Froodian]] | ||
* {{bug|350733}} - Make cmd/shift modifiers work on items in the back/forward button menus | * {{bug|350733}} - Make cmd/shift modifiers work on items in the back/forward button menus | ||
** ''cl wants to talk about this'' | ** ''cl wants to talk about this'' |
Revision as of 16:27, 1 December 2006
Wed 06 Dec 9am PST (17:00 GMT/UTC) in #camino-mtg
Contents
General Plans
- Camino 1.1
- Camino 1.1 Alpha 2
- tinderboxen
- Bookmark loss
- A user who's been useful in the past (sending info and console logs) hypothesizes that this is related to Camino being in the login items - she saw it twice, and since removing it from login items hasn't seen it again. Is it even remotely possible that they're related?
- Weekly Bugs and Queues update
Specific bugs that need action
- Bug 327203 - First item in pref pane gets focus even when OS pref says not to
- Is my hack OK (since it's highly unlikely there will ever be a prefpane with a single element, and it doesn't do anything catastrophic if there is)? If not, does anybody have a better solution? Froodian
- Bug 350733 - Make cmd/shift modifiers work on items in the back/forward button menus
- cl wants to talk about this
- Bug 361157 - Opening files should open them in a new window
- Should this be tied to a pref, and if so which one?
Queries
Camino 1.1a2
Camino 1.1b1
Camino 1.1
- Bugs targeted at 1.1
- Blocking ?
- Blocking +
- Blocking -
- Bugs without target
- The above list needs to be at least spot-audited for potential 1.1 issues