Cruz, Jaime wrote on 15/12/2014 04:54:
pjdkru...@gmail.com wrote:
Yes, it's an accessibility feature called Type Ahead Find which is
enabled by default in SeaMonkey. In about:config you can disable by
setting these prefs to false:
accessibility.typeaheadfind
pjdkru...@gmail.com wrote:
Yes, it's an accessibility feature called Type Ahead Find which is enabled by
default in SeaMonkey. In about:config you can disable by setting these prefs
to false:
accessibility.typeaheadfind
accessibility.typeaheadfind.autostart
I've changed both to FALSE, as
On 12/15/2014 10:11 AM, Bill Spikowski wrote:
pjdkru...@gmail.com wrote:
Yes, it's an accessibility feature called Type Ahead Find which is
enabled by default in SeaMonkey. In about:config you can disable by
setting these prefs to false:
accessibility.typeaheadfind
On 12/15/2014 10:11 AM, Bill Spikowski wrote:
pjdkru...@gmail.com wrote:
Yes, it's an accessibility feature called Type Ahead Find which is
enabled by default in SeaMonkey. In about:config you can disable by
setting these prefs to false:
accessibility.typeaheadfind
SeaMonkey is periodically freezing for a few seconds. Also, the focus
will randomly change from browser to mail/news to message compose window.
Anyone else seeing this happen? I thought it might be Flash but I
uninstalled it. Still happening. Also happens in Safe Mode.
Mozilla/5.0
Hi,
When there's a browser update, and you restart SM, it will run the
updater and then start the browser with a redirect to the release notes.
This has always worked.
Today, I restarted SM, it ran the updater, but then a SM related dialog
(which I've never seen) appeared saying there had
Bill Spikowski wrote:
Does anyone else have the problem where they're typing something into a
web form in SM and suddenly the find box pops open and the cursor is
entering my text there, instead of in the web form?
This has been happening quite a lot and I kept assuming I was hitting
some odd
hawker wrote on 15/12/2014 18:29:
On 12/15/2014 10:11 AM, Bill Spikowski wrote:
pjdkru...@gmail.com wrote:
Yes, it's an accessibility feature called Type Ahead Find which is
enabled by default in SeaMonkey. In about:config you can disable by
setting these prefs to false:
NoOp wrote:
On 12/14/2014 12:28 AM, Paul B. Gallagher wrote:
WaltS48 wrote:
On 12/13/2014 11:10 PM, Paul B. Gallagher wrote:
WaltS48 wrote:
On 12/13/2014 10:36 PM, Paul B. Gallagher wrote:
WaltS48 wrote:
Have you tried the Allow cookies for the originating site only (no
third-party
NoOp wrote:
Ah, forgot that I had adblock-plus turned on, went back and turned off
adblock-plus reloaded the page - now I get the google NID cookie (and
a billion others).
Huh. ABP blocks the Google cookie but SM doesn't.
Clear cookies, cache et al - set cookies to not accept cookes from
EE wrote:
Paul B. Gallagher wrote:
WaltS48 wrote:
On 12/13/2014 11:10 PM, Paul B. Gallagher wrote:
WaltS48 wrote:
On 12/13/2014 10:36 PM, Paul B. Gallagher wrote:
WaltS48 wrote:
Have you tried the Allow cookies for the originating site only (no
third-party cookies) setting?
I refer you
WaltS48 wrote:
Using my production profile for SeaMonkey.
I just set my *Cookie Acceptance Policy* to Allow cookies for the
original website (no third-party cookies). Left the *Cookie
Retention Policy* set to Accept Cookies Normally.
OK, your policy is the same as mine except for Accept
I did the reformating of my ExFAT 50 GB volume with 4096-cluster size. Exactly
after this SeaMonkey 2.31 starts to crash when I move letters between mailboxes
with AutoCompacting turned on (Preferences-MailStorage-Disk Space). I turned
off this feature and crashes are gone. When I manually
13 matches
Mail list logo
