On 7/18/2012 8:51 PM PT, Ant typed:
... for v2.10.1 (and soon v2.11+) due to JavaScript/JS speed problems on
some web sites and pages in older Gecko engines. :(
One good thing about the newer versions, I have not had any SM web
browser crashes yet from my memory and about:crashes on two
On 7/22/2012 3:00 PM PT, Ant typed:
On 7/18/2012 8:51 PM PT, Ant typed:
... for v2.10.1 (and soon v2.11+) due to JavaScript/JS speed problems on
some web sites and pages in older Gecko engines. :(
One good thing about the newer versions, I have not had any SM web
browser crashes yet from my
Justin Wood (Callek) wrote:
Ant wrote:
Now if Mozilla can fix the minor and sometimes annoying issues that I
mentioned recently. :P
We're working on improving many issues, without also regressing many things.
Stay Tuned. (Let this be a lesson to people here that its much better to
Ant wrote:
On 7/17/2012 7:51 AM PT, Ed Mullen typed:
Don't know about BugMeNot but you don't really need NoSquint - the
capability is built into SM.
about:config
browser.zoom.siteSpecific
is set True by default.
Ah. What about showing the status of text and whole web page sizes in
On 7/18/2012 10:21 AM PT, Ed Mullen typed:
Don't know about BugMeNot but you don't really need NoSquint - the
capability is built into SM.
about:config
browser.zoom.siteSpecific
is set True by default.
Ah. What about showing the status of text and whole web page sizes in
percentage that
On 7/14/2012 5:56 PM PT, Ant typed:
... for v2.10.1 (and soon v2.11+) due to JavaScript/JS speed problems on
some web sites and pages in older Gecko engines. :(
One good thing about the newer versions, I have not had any SM web
browser crashes yet from my memory and about:crashes on two
Ant wrote:
Now if Mozilla can fix the minor and sometimes annoying issues that I
mentioned recently. :P
We're working on improving many issues, without also regressing many things.
Stay Tuned. (Let this be a lesson to people here that its much better to
upgrade than stick with old versions)
On 7/18/2012 8:53 PM PT, Justin Wood (Callek) typed:
Now if Mozilla can fix the minor and sometimes annoying issues that I
mentioned recently. :P
We're working on improving many issues, without also regressing many things.
Stay Tuned. (Let this be a lesson to people here that its much better
WLS wrote:
On 07/16/2012 11:30 AM, Daniel wrote:
WLS wrote:
Daniel wrote:
Ant wrote:
On 7/15/2012 10:50 AM PT, Justin Wood (Callek) typed:
Hard to say, *but* unlike in 2.0.14 we do have a new way to (try) and
find out what is using up the memory!
Try loading about:memory in a new tab, and
Ant wrote:
On 7/15/2012 9:13 AM PT, Ant typed:
...
Don't know about BugMeNot but you don't really need NoSquint - the
capability is built into SM.
about:config
browser.zoom.siteSpecific
is set True by default.
Ah. What about showing the status of text and whole web page sizes in
percentage
Ed Mullen a écrit :
Ant wrote:
On 7/15/2012 9:13 AM PT, Ant typed:
...
Don't know about BugMeNot but you don't really need NoSquint - the
capability is built into SM.
about:config
browser.zoom.siteSpecific
is set True by default.
Ah. What about showing the status of text and whole web
cyberzen wrote:
it's a pity this can't be more handy ...
(No squint solved the problem)
Isn't the functionality you need exposed at Edit / Preferences /
Appearance / Content / Zoom only text instead of full pages ?
Philip Taylor
___
Philip TAYLOR a écrit :
cyberzen wrote:
it's a pity this can't be more handy ...
(No squint solved the problem)
Isn't the functionality you need exposed at Edit / Preferences /
Appearance / Content / Zoom only text instead of full pages ?
Philip Taylor
yes it does exists
but in 2
Ed Mullen wrote:
Ant wrote:
On 7/15/2012 9:13 AM PT, Ant typed:
...
Don't know about BugMeNot but you don't really need NoSquint - the
capability is built into SM.
about:config
browser.zoom.siteSpecific
is set True by default.
Ah. What about showing the status of text and whole web page
Philip TAYLOR wrote:
cyberzen wrote:
it's a pity this can't be more handy ...
(No squint solved the problem)
Isn't the functionality you need exposed at Edit / Preferences /
Appearance / Content / Zoom only text instead of full pages ?
Philip Taylor
NO! SM built in Features don't hold a
On 7/17/2012 7:51 AM PT, Ed Mullen typed:
Don't know about BugMeNot but you don't really need NoSquint - the
capability is built into SM.
about:config
browser.zoom.siteSpecific
is set True by default.
Ah. What about showing the status of text and whole web page sizes in
percentage that
On 7/17/2012 10:52 AM PT, PhillipJones typed:
it's a pity this can't be more handy ...
(No squint solved the problem)
Isn't the functionality you need exposed at Edit / Preferences /
Appearance / Content / Zoom only text instead of full pages ?
NO! SM built in Features don't hold a candle
Ant wrote:
On 7/15/2012 10:50 AM PT, Justin Wood (Callek) typed:
Hard to say, *but* unlike in 2.0.14 we do have a new way to (try) and
find out what is using up the memory!
Try loading about:memory in a new tab, and you should see a breakdown.
Part of it could be new memory cache stuff, part
On 7/16/2012 7:20 AM PT, Daniel typed:
Hard to say, *but* unlike in 2.0.14 we do have a new way to (try) and
find out what is using up the memory!
Try loading about:memory in a new tab, and you should see a breakdown.
Part of it could be new memory cache stuff, part of it could be related
to
Daniel wrote:
Ant wrote:
On 7/15/2012 10:50 AM PT, Justin Wood (Callek) typed:
Hard to say, *but* unlike in 2.0.14 we do have a new way to (try) and
find out what is using up the memory!
Try loading about:memory in a new tab, and you should see a breakdown.
Part of it could be new memory
WLS wrote:
Daniel wrote:
Ant wrote:
On 7/15/2012 10:50 AM PT, Justin Wood (Callek) typed:
Hard to say, *but* unlike in 2.0.14 we do have a new way to (try) and
find out what is using up the memory!
Try loading about:memory in a new tab, and you should see a breakdown.
Part of it could be
On 07/15/2012 02:55 PM, Ant wrote:
On 7/15/2012 10:50 AM PT, Justin Wood (Callek) typed:
Hard to say, *but* unlike in 2.0.14 we do have a new way to (try) and
find out what is using up the memory!
Try loading about:memory in a new tab, and you should see a breakdown.
Part of it could be
On 07/16/2012 11:30 AM, Daniel wrote:
WLS wrote:
Daniel wrote:
Ant wrote:
On 7/15/2012 10:50 AM PT, Justin Wood (Callek) typed:
Hard to say, *but* unlike in 2.0.14 we do have a new way to (try) and
find out what is using up the memory!
Try loading about:memory in a new tab, and you should
Ant wrote:
... for v2.10.1 (and soon v2.11+) due to JavaScript/JS speed problems on
some web sites and pages in older Gecko engines. :(
Does anyone if there is a SM compatible extensions for these?
1. NoSquint, to memorize sizes on specific web pages/sites, from
https://urandom.ca/nosquint/
2.
On 7/15/2012 7:22 AM PT, Ed Mullen typed:
... for v2.10.1 (and soon v2.11+) due to JavaScript/JS speed problems on
some web sites and pages in older Gecko engines. :(
Does anyone if there is a SM compatible extensions for these?
1. NoSquint, to memorize sizes on specific web pages/sites, from
On 7/15/2012 9:13 AM PT, Ant typed:
...
Don't know about BugMeNot but you don't really need NoSquint - the
capability is built into SM.
about:config
browser.zoom.siteSpecific
is set True by default.
Ah. What about showing the status of text and whole web page sizes in
percentage that
Hi again!
Is anyone else noticing v2.10.1 uses a lot more memory than v2.0.14 and
earlier? I saw my new SM installation and profile went high as 1.5-1.6
(peak) GB in my old, updated 32-bit Windows XP Pro. SP3 machine (2.5 GB
of RAM). This was I surfing, watching videos, using tabs, etc. a
Ant wrote:
Hi again!
Is anyone else noticing v2.10.1 uses a lot more memory than v2.0.14 and
earlier? I saw my new SM installation and profile went high as 1.5-1.6
(peak) GB in my old, updated 32-bit Windows XP Pro. SP3 machine (2.5 GB
of RAM). This was I surfing, watching videos, using
On 7/15/2012 10:09 AM PT, Ant typed:
Don't know about BugMeNot but you don't really need NoSquint - the
capability is built into SM.
about:config
browser.zoom.siteSpecific
is set True by default.
Ah. What about showing the status of text and whole web page sizes in
percentage that NoSquint
Ant wrote:
I closed a bunch to avoid the sensitive ones and memory usages went down
a bit. Must be too many tabs/web pages I guess? ;)
Yes, my skim of that memory dump doesn't turn anything too extravagant
up other than just a large number of pages/windows/tabs open.
The largest noteworthy
On 7/15/2012 3:05 PM PT, Justin Wood (Callek) typed:
I closed a bunch to avoid the sensitive ones and memory usages went down
a bit. Must be too many tabs/web pages I guess? ;)
Yes, my skim of that memory dump doesn't turn anything too extravagant
up other than just a large number of
... for v2.10.1 (and soon v2.11+) due to JavaScript/JS speed problems on
some web sites and pages in older Gecko engines. :(
Does anyone if there is a SM compatible extensions for these?
1. NoSquint, to memorize sizes on specific web pages/sites, from
https://urandom.ca/nosquint/
2. BugMeNot
32 matches
Mail list logo
