Firefox3/StatusMeetings/2006-08-23: Difference between revisions
< Firefox3 | StatusMeetings
		
		
		
		Jump to navigation
		Jump to search
		| Line 31: | Line 31: | ||
** web services as content handlers  | ** web services as content handlers  | ||
*** need to work with Hixie's spec (URI protocol and mime types)  | *** need to work with Hixie's spec (URI protocol and mime types)  | ||
*** can we do microformats in this same framework?  | |||
** tab drag and drop between windows  | ** tab drag and drop between windows  | ||
*** detach/reattach views?  | *** detach/reattach views?  | ||
*** docshell code sucks; need to talk to bz  | |||
= Firefox 3 =  | = Firefox 3 =  | ||
Revision as of 18:19, 23 August 2006
<< previous week | index | next week>>
Meeting Details
- 11:00am PDT (18:00 UTC)
 - Mozilla HQ, 1st floor conference table
 - +1 866 216 2181 (or +1 303 228 0514)
 - join irc.mozilla.org #granparadiso for backchannel
 
Agenda
- Gecko 1.9 Roundtable
 - Firefox 3
 - Any other business
 
Gecko 1.9 Roundtable
- XBL2
 
- Performance testing meeting following this meeting
 
- Things not on our current feature lists, that may be needed for Firefox 3
- full-text indexing for sqlite/mozStorage
- Do we expose this to DOM Storage?
 
 - microformat detection services
- myk/dmose to look into it
 
 - XUL prettyfication
- gradients with CSS using cairo
 - transparency effects
 - simple animation elements
 - single-direction percentage-based layout (same direction as your parent box)
 - need actual use cases for all of these
 
 - web services as content handlers
- need to work with Hixie's spec (URI protocol and mime types)
 - can we do microformats in this same framework?
 
 - tab drag and drop between windows
- detach/reattach views?
 - docshell code sucks; need to talk to bz
 
 
 - full-text indexing for sqlite/mozStorage
 
Firefox 3
- I posted to dev.apps.firefox about gathering user problems, but it might get ratholey :(
 - I also proposed a new format for describing themes for data collection which sherman is moving over to a wiki
- we need to start moving on these data collection activities *now* in order to help us generate and prioritize requirements for Firefox 3 and beyond
 
 - I'm trying to come up with ways of driving out requirements (both front end and gecko) which are based on actual user needs and problems; will have something shortly to share.