On 11/06/2010 09:00 PM, Jay Garcia wrote: > On 06.11.2010 19:49, Oliver Naumann wrote: > > --- Original Message --- > >> NoOp wrote: >> >>> On 11/05/2010 02:45 AM, Arne wrote: >>>> Oliver Naumann wrote: >>>>> >>>>> [1]<https://support.mozilla.com/en-US/questions/762688> >>>> >>>> Don't work for me. I have DOM storage enabled (was never disabled). >>> >>> Ditto. dom.storage.enabled on a clean FF install is 'true'. Same for SM >>> 2.1b2pre, and I tested turning off on SM 2.0.1.10 w/no change. >> >> That's interesting. With dom.storage.enabled set to true, the site >> works for me as expected, with no errors anywhere. Do you get anything >> in the Error Console at all? >> >> Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.1.15) >> Gecko/20101027 Lightning/1.0b2 SeaMonkey/2.0.10 > > Yes, very interesting as when mine is set to false (default) I notice > the same problems and the search button doesn't work either. Set to > "true" everything there works.
Mea culpa. I found that if I set dom.storage.enabled set to true *and* turn on 'cookies' all works. By default I have 'cookies' disabled & therefore it didn't matter if I turned dom.storage.enabled to true or not - without cookies turned on it didn't work. With *both* cookies and dom.storage.enabled set true it works. The odd part is that I tested on what I thought was a new Firefox (FF) install on a different machine (using WinXP as a guest VM on a linux host) and didn't get it to work. Going back an examining the FF and SM on that VM (Virtual Machine) I see that, by habit, I'd set both to not accept cookies. Maybe I should just go back to Pine and Mosaic... Thanks to all for the feedback & testing. Gary _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
