On 15/12/2014 01:39, A Williams wrote: > David H. Durgee wrote: >> Is this a one-time fixes-it-forever work-around or one that needs to be >> repeated every time you restart SeaMonkey? Is the restart necessary or >> just cleaner? >> >> I am assuming now that it is identified it will be fixed in the next >> release, correct? I doubt that Chase is the only site impacted by it. >> >> Dave > > I'm assuming it is an each-time-you-restart-seamonkey job. > What it really means is that the developers care *and* know what the > problem is. I'd expect the next version of Seamonkey to be fixed.
I had a hypothesis on what was causing the problem. https://bugzilla.mozilla.org/show_bug.cgi?id=1094714#c17 I wrote a few steps that a non-technical user could do to test this hypothesis. Results confirm that we were right. We now have a quick fix and we need to get this in the hands of our users as soon as possible. https://bugzilla.mozilla.org/attachment.cgi?id=8527843&action=edit A longer term fix would be: https://bugzilla.mozilla.org/show_bug.cgi?id=1094714#c12 but that would require the involvement of a Gecko developer. And nothing stops us from landing the quick fix. Phil -- Philip Chee <phi...@aleytys.pc.my>, <philip.c...@gmail.com> http://flashblock.mozdev.org/ http://xsidebar.mozdev.org Guard us from the she-wolf and the wolf, and guard us from the thief, oh Night, and so be good for us to pass. _______________________________________________ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
