Confirmed users
2,595
edits
SeaMonkey/StatusMeetings/2015-09-01: Difference between revisions
SeaMonkey/StatusMeetings/2015-09-01 (view source)
Revision as of 08:09, 29 September 2015
, 29 September 2015My cat is sad because he has just spotted a Keep Calm & Carry On poster in the distance.
m (Header missing) |
Philip Chee (talk | contribs) m (My cat is sad because he has just spotted a Keep Calm & Carry On poster in the distance.) |
||
| Line 126: | Line 126: | ||
==== 2.Next ==== | ==== 2.Next ==== | ||
* We need someone to work on porting sync 2.0 over to replace legacy sync code. The finer details of how are so far unknown, but we should have a usable solution before legacy sync is turned off. 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. | |||
<!-- *** '''We have official permission to use the Firefox FxA 2.0 sync servers!''' --> | |||
* Stalled. Needs a kick. | * Stalled. Needs a kick. | ||
** {{Bug|815954}} Click-to-Play: Port {{Bug|812562}} (click-to-play blocklisted plugins: reshow urlbar notification as with normal click-to-play). | ** {{Bug|815954}} Click-to-Play: Port {{Bug|812562}} (click-to-play blocklisted plugins: reshow urlbar notification as with normal click-to-play). | ||
| Line 144: | Line 148: | ||
*** further work to separate function from style in CSS for about:privatebrowsing in {{bug|1178008}} ''(3rd-party themes)'' | *** further work to separate function from style in CSS for about:privatebrowsing in {{bug|1178008}} ''(3rd-party themes)'' | ||
*** '''Ratty''' restored about:privatebrowsing UI to before it was messed up by Project Chameleon styles [{{Bug|1192276}}] | *** '''Ratty''' restored about:privatebrowsing UI to before it was messed up by Project Chameleon styles [{{Bug|1192276}}] | ||
** 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: | ||