Confirmed users
341
edits
SeaMonkey/StatusMeetings/2014-05-13: Difference between revisions
Jump to navigation
Jump to search
→Feature List, Planning
(→2.Next) |
|||
| Line 153: | Line 153: | ||
* See [[SeaMonkey/StatusMeetings/FeatureList|Feature List]] page for major wanted/needed features. | * See [[SeaMonkey/StatusMeetings/FeatureList|Feature List]] page for major wanted/needed features. | ||
* SeaMonkey needs a debugger for its chrome code. Jez couldn't continue work on {{bug|613974}} because he couldn't figure out a way to debug Seamonkey's JS. He suggest Firebug be modified to allow remote debugging of Seamonkey ({{bug|1006466}}). Bare minimum, have a good tutorial about how to debug Seamonkey chrome from Firefox (couldn't get that to work either) and link it from various Seamonkey developer pages. | * SeaMonkey needs a debugger for its chrome code. Jez couldn't continue work on {{bug|613974}} because he couldn't figure out a way to debug Seamonkey's JS. He suggest Firebug be modified to allow remote debugging of Seamonkey ({{bug|1006466}}). Bare minimum, have a good tutorial about how to debug Seamonkey chrome from Firefox (couldn't get that to work either) and link it from various Seamonkey developer pages. | ||
** We had some discussion in the meeting if we should look at porting/including the Firefox devtools or rather look into bundling Firebug 2.0 | |||
*'''TODO:''' We will need to update our Sync UI code due to the new Sync API. Also we need to check if we are allowed to create FX accounts from our UI Since the new Sync accounts are FX accounts.[IanN] I'm sure I saw a question about FX accounts and branding. | *'''TODO:''' We will need to update our Sync UI code due to the new Sync API. Also we need to check if we are allowed to create FX accounts from our UI Since the new Sync accounts are FX accounts.[IanN] I'm sure I saw a question about FX accounts and branding. | ||