Philip Chee wrote:
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 fi
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 t
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
THANK YOU! This was driving me N
> On Wednesday, December 10, 2014 5:41:25 PM UTC-5, David E. Ross wrote:
> I have the PrefBar extension. I created my own button to toggle the
> HTML5 preference, which is media.autoplay.enabled. That way, HTML5 is
> not tied to Flash.
>
AFAIK, this preference stopped working some time ago an
Mozilla's plugin-check page is updated manually and is *never* up-to-date. In
fact, it generally considers many ancient versions of plugins to be current and
occasionally it will even say that brand new versions are out-of-date. The
plan was to convince the various plugins developers to adopt
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
___
support-seamon
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
key combination that
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 to my orig
Paul B. Gallagher wrote:
EE wrote:
Paul B. Gallagher wrote:
This evening, I cleared all private data (including cache and cookies),
and then visited nhl.com.
Immediately after aborting their troublesome javascript,* I inspected my
cookies and discovered that google.com had set a cookie.
Now,
On 12/14/2014 12:59 PM, NoOp wrote:
On 12/14/2014 09:51 AM, NoOp wrote:
On 12/14/2014 12:28 AM, Paul B. Gallagher wrote:
...
(I don't understand what clearing history has to do with cookies, but be
that as it may...)
I do get precisely one Google cookie by visiting nhl.com, and since
Google i
On 12/14/2014 09:35 AM, Ed Mullen wrote:
> Paul B. Gallagher wrote on 12/14/2014 12:28 PM:
>> Ed Mullen wrote:
>>> Paul B. Gallagher wrote on 12/13/2014 7:36 PM:
Ed Mullen wrote:
> Paul B. Gallagher wrote on 12/13/2014 2:19 PM:
>> Ed Mullen wrote:
>>> Paul B. Gallagher wrote on 12/
On 12/14/2014 09:51 AM, NoOp wrote:
> On 12/14/2014 12:28 AM, Paul B. Gallagher wrote:
...
>> (I don't understand what clearing history has to do with cookies, but be
>> that as it may...)
>>
>> I do get precisely one Google cookie by visiting nhl.com, and since
>> Google isn't the originating s
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
>>
Paul B. Gallagher wrote on 12/14/2014 12:28 PM:
Ed Mullen wrote:
Paul B. Gallagher wrote on 12/13/2014 7:36 PM:
Ed Mullen wrote:
Paul B. Gallagher wrote on 12/13/2014 2:19 PM:
Ed Mullen wrote:
Paul B. Gallagher wrote on 12/13/2014 1:18 AM:
Miles Fidelman wrote:
Hi Folks,
So it looks like
David H. Durgee wrote:
A Williams wrote:
David H. Durgee wrote:
Marisa Ciceran wrote:
Same problem here as of the start of this weekend. I've been on the
phone several times with Chase support about this and this time the
agent I spoke to said he sent a note to their compatibility developers.
Ed Mullen wrote:
Paul B. Gallagher wrote on 12/13/2014 7:36 PM:
Ed Mullen wrote:
Paul B. Gallagher wrote on 12/13/2014 2:19 PM:
Ed Mullen wrote:
Paul B. Gallagher wrote on 12/13/2014 1:18 AM:
Miles Fidelman wrote:
Hi Folks,
So it looks like Seamonkey automatically disables the Flash
plug-
David H. Durgee wrote on 12/14/2014 10:02 AM:
A Williams wrote:
David H. Durgee wrote:
Marisa Ciceran wrote:
Same problem here as of the start of this weekend. I've been on the
phone several times with Chase support about this and this time the
agent I spoke to said he sent a note to their com
Paul B. Gallagher wrote on 12/13/2014 7:36 PM:
Ed Mullen wrote:
Paul B. Gallagher wrote on 12/13/2014 2:19 PM:
Ed Mullen wrote:
Paul B. Gallagher wrote on 12/13/2014 1:18 AM:
Miles Fidelman wrote:
Hi Folks,
So it looks like Seamonkey automatically disables the Flash
plug-in if
it's older t
On 12/14/14, 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-par
On 12/14/2014 10:02 AM, David H. Durgee wrote:
A Williams wrote:
David H. Durgee wrote:
Marisa Ciceran wrote:
Same problem here as of the start of this weekend. I've been on the
phone several times with Chase support about this and this time the
agent I spoke to said he sent a note to their co
A Williams wrote:
David H. Durgee wrote:
Marisa Ciceran wrote:
Same problem here as of the start of this weekend. I've been on the
phone several times with Chase support about this and this time the
agent I spoke to said he sent a note to their compatibility developers.
I am on 64-bit Windows
On 12/14/2014 03: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 cookies)" setting?
GerardJan wrote:
johndesmond.busin...@gmail.com wrote:
I'm running SeaMonkey 2.30 under Windows 7 Home Premium (Service Pack 1) on a
Toshiba Satellite L455 laptop with 4G of memory.
When I load a new web page - either by clicking hyperlink or bookmark or
typing in URL, only the 'top screen' o
johndesmond.busin...@gmail.com wrote:
I'm running SeaMonkey 2.30 under Windows 7 Home Premium (Service Pack 1) on a
Toshiba Satellite L455 laptop with 4G of memory.
When I load a new web page - either by clicking hyperlink or bookmark or typing
in URL, only the 'top screen' of the page can be
David H. Durgee wrote:
Marisa Ciceran wrote:
Same problem here as of the start of this weekend. I've been on the
phone several times with Chase support about this and this time the
agent I spoke to said he sent a note to their compatibility developers.
I am on 64-bit Windows 7 Pro on on ASUSI7
On 14/12/14 14:39, Paul B. Gallagher wrote:
Daniel wrote:
On 14/12/14 06:22, Paul B. Gallagher wrote
That's problematic for me because I do have a gmail account and
sometimes use it to login to other sites (as soon as I'm done, I clear
the cookies and resume living privately). nhl.com is not
I'm running SeaMonkey 2.30 under Windows 7 Home Premium (Service Pack 1) on a
Toshiba Satellite L455 laptop with 4G of memory.
When I load a new web page - either by clicking hyperlink or bookmark or typing
in URL, only the 'top screen' of the page can be read, and I have to click the
'reload
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 to my original query, which you appa
28 matches
Mail list logo
