Confirmed users
2,595
edits
SeaMonkey/StatusMeetings/2014-05-13: Difference between revisions
Jump to navigation
Jump to search
→2.Next
Philip Chee (talk | contribs) (→Ratty) |
Philip Chee (talk | contribs) (→2.Next) |
||
| Line 94: | Line 94: | ||
** {{Bug|995737}} adapt seamonkey for the ab remote content policy change; use permission manager instead of address book property. | ** {{Bug|995737}} adapt seamonkey for the ab remote content policy change; use permission manager instead of address book property. | ||
** {{Bug|1008596}} No SeaMonkey 2.28a2 nightly aurora builds, likely due to wrong relbranches in client.py configuration. ''(resumed after bustage fix)'' | ** {{Bug|1008596}} No SeaMonkey 2.28a2 nightly aurora builds, likely due to wrong relbranches in client.py configuration. ''(resumed after bustage fix)'' | ||
** {{Bug|998724} Feed preview is broken on SeaMonkey nightly [ASSIGNED]. | |||
<!-- ** — -> | <!-- ** — -> | ||
<!--Please update--> | <!--Please update--> | ||
* Mozilla-central bugs that affect us: | * Mozilla-central bugs that affect us: | ||
** '''Note:''' Please file bugs if you notice any landing on mozilla-central that might break us. Please don't depend on Ratty noticing such landings. | ** '''Note:''' Please file bugs if you notice any landing on mozilla-central that might break us. Please don't depend on Ratty noticing such landings. | ||
** Our front end Sync UI needs to be updated as the old backend is going away in Gecko/Firefox 31. See: [http://blog.swarnava.in/2014/02/new-firefox-sync-has-landed-in-firefox.html New Firefox Sync has landed in Firefox Nightly]. | ** Our front end Sync UI needs to be updated as the old backend is going away in Gecko/Firefox 31. See: [http://blog.swarnava.in/2014/02/new-firefox-sync-has-landed-in-firefox.html New Firefox Sync has landed in Firefox Nightly]. Tracked in: | ||
*** {Bug|998807}} Sync account creation or device pairing fails with exception in BrowserIDManager. | |||
*** {Bug|1003434}} Add support for about:sync-progress. | |||
** A lot of these bugs are due to mozilla-central switching from synchronous APIs to Asynchronous APIs. | ** A lot of these bugs are due to mozilla-central switching from synchronous APIs to Asynchronous APIs. | ||
** {{Bug|566746}} (asyncFormHistory) Form history should use asynchronous storage API. Tracked in: | ** {{Bug|566746}} (asyncFormHistory) Form history should use asynchronous storage API. Tracked in: | ||