SeaMonkey/StatusMeetings/2015-03-17: Difference between revisions

 
(4 intermediate revisions by one other user not shown)
Line 98: Line 98:
*** [http://forums.mozillazine.org/viewtopic.php?p=13767725#p13767725 Workaround 2:]
*** [http://forums.mozillazine.org/viewtopic.php?p=13767725#p13767725 Workaround 2:]
* There is some confusion about the SSL 3.0 disabling [https://blog.mozilla.org/security/2014/10/14/the-poodle-attack-and-the-end-of-ssl-3-0/ The POODLE Attack and the End of SSL 3.0]. Also see {{Bug|1107103}} https://wcis.ceiwc.com does not work in Firefox 34 and later.
* There is some confusion about the SSL 3.0 disabling [https://blog.mozilla.org/security/2014/10/14/the-poodle-attack-and-the-end-of-ssl-3-0/ The POODLE Attack and the End of SSL 3.0]. Also see {{Bug|1107103}} https://wcis.ceiwc.com does not work in Firefox 34 and later.
** SSL 3.0 support has been dropped entirely from 2.36, see {{bug|1106470}} and [https://tools.ietf.org/html/draft-ietf-tls-sslv3-diediedie-00 IETF Draft].
** We've picked up he default for <tt>security.tls.version.min</tt> from Mozilla Core, but <tt>security.tls.version.fallback-limit</tt> is new. So we need to add the latter to our preferences UI.
** We've picked up he default for <tt>security.tls.version.min</tt> from Mozilla Core, but <tt>security.tls.version.fallback-limit</tt> is new. So we need to add the latter to our preferences UI.
** Anybody having an opinion on this please comment on the bug to track this issue ({{Bug|1123673}} Consider exposing security.tls.version.fallback-limit in SSL prefpane to accommodate SSL 3.0 legacy sites).
** Anybody having an opinion on this please comment on the bug to track this issue ({{Bug|1123673}} Consider exposing security.tls.version.fallback-limit in SSL prefpane to accommodate SSL 3.0 legacy sites).
** SSL 3.0 support '''will''' be deprecated effective with 2.36, see {{bug|1106470}} and [https://tools.ietf.org/html/draft-ietf-tls-sslv3-diediedie-00 IETF Draft].
** {{Bug|1137991}} covers removal of the SSL 3.0 checkbox from SSL preferences
** {{Bug|1137991}} covers removal of the SSL 3.0 checkbox from SSL preferences
* {{Bug|1114285}} Autoscroll problem general.autoScroll does not work in 2.32 beta
* {{Bug|1114285}} Autoscroll problem general.autoScroll does not work in 2.32 beta
Line 123: Line 123:
*** {{Bug|998807}} Sync account creation or device pairing fails with exception in BrowserIDManager.
*** {{Bug|998807}} Sync account creation or device pairing fails with exception in BrowserIDManager.
*** {{Bug|1003434}} Add support for about:sync-progress.
*** {{Bug|1003434}} Add support for about:sync-progress.
*** '''Update''' SeaMonkey won't be allowed to use the Firefox Sync 1.5 servers. Need to look into the possibility of hosting our own servers on a community machine or VPS.
*** '''Update''' SeaMonkey won't be allowed to use the Firefox Sync 1.5 servers. Ewong is looking into hosting our own FxAccount server on a community machine or VPS.
** 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:
Line 146: Line 146:


* See [[SeaMonkey/StatusMeetings/FeatureList|Feature List]] page for major wanted/needed features.
* See [[SeaMonkey/StatusMeetings/FeatureList|Feature List]] page for major wanted/needed features.
*'''TODO:''' We will need to update our Sync UI code due to the new Sync API.
*'''TODO:'''
** MoCo will not allow us to use FxAccounts (the new Sync API). We might want to update our code anyway just in case. One possibility is to set up our own Sync 1.5 server on a Community machine.
**  We will need to update our Sync UI code due to the new Sync API. MoCo will not allow us to use FxAccounts (the new Sync API). We might want to update our code anyway just in case. One possibility is to set up our own Sync 1.5 server on a Community machine.
** Bug 1127784 proposes to add a preference and UI to enable/disable playback of Encrypted Media Extensions.


=== Roundtable - Personal Status Updates ===
=== Roundtable - Personal Status Updates ===
Line 215: Line 216:
==== Mnyromyr ====
==== Mnyromyr ====
==== Neil ====
==== Neil ====
Checked in to comm-central, needs comm-aurora uplift:
* {{Bug|1140640}} Make From: header editable per-message.
* {{Bug|1133582}} Warning box in about:config doesn't display properly in Modern any more.
* {{Bug|1133380}} about:privatebrowsing doesn't display properly in Classic any more.
Working on:
* {{Bug|1140105}} Wrong font displayed in font menu when selection is collapsed.
* {{Bug|1141017}} Wrong font is sometimes displayed in font menulist.
Still waiting for review:
* {{Bug|1098350}} Need to refactor SeaMonkey Preferences and UI because {{Bug|530209}} replaced the browser.urlbar.default.behavior preference with a more flexible scheme.
* {{Bug|970993}} Aero Peek rendering issues.
==== Px ====
==== Px ====
==== Ratty ====
==== Ratty ====
Line 267: Line 279:
=== Any other business?  ===
=== Any other business?  ===
* New review policy for packaging fixes (package-manifest.in). Due to the general unavailability of the team members who usually review these changes (mcsmurf, Callek), Ratty will be available for reviewing packaging fixes or do them himself with a rs=packaging fix..
* New review policy for packaging fixes (package-manifest.in). Due to the general unavailability of the team members who usually review these changes (mcsmurf, Callek), Ratty will be available for reviewing packaging fixes or do them himself with a rs=packaging fix..
* North American Daylight Saving Time began on March 8, meeting time remains 13:00 UTC until Europe switches.
* European Summer Time begins on the 29th March, thus, moving from 13:00 to 12:00 UTC already on 31st March.
Confirmed users
269

edits