I'm guessing a similar problem I'm having related to text fields is
also a result of these actions then as well…
I use TypeItForMe and any time now using the recent nightlies when
I've used it, it renders any text entry into fields impossible unless
I cut and paste text.
Am I correct in assuming this?
Brian
On Jun 13, 2005, at 10:01 AM, Stuart Morgan wrote:
On Jun 13, 2005, at 2:36 AM, David Fedoruk wrote:
The problem with lagging response in TextAreas has been an on going
one. The issue is complicated and has something to do with Camino's
mixed heritage. Its Frontened is cocoas but its rendering engine is
mozilla's.
The current issue isn't fundamentally that complicated, and has
nothing to do with the Cocoa/Carbon mix. It's simply that the way
textfields are drawn is currently extremely inefficient. 30
seconds with Quartz debug makes it clear that the issue is
excessive drawing.
Yes, I believe that the developers (I'm not one of them) would
like to
use cocoa here because it would also give camino access to OS X 's
spell checker.
No they wouldn't. If you read the bug about it you'll see Mike
Pinkerton saying that they do not want to move to true Cocoa
widgets because of potential speed issues.
I'm not sure where we stand with running Quartz instead of
QuickDraw.
Only images are currently drawn with Quartz.
There is a suspicsion also that running animations anywhere (even
ones hidden behind another window or in a hidden tab) are causing
part of this problem.
It's not a suspicion; again it's easy to see that redraws currently
become inefficient with multiple animated sections of the screen,
and focused textfields are animated elements. It's definitely not
related to animations that aren't visible though, since they
contribute nothing to drawing speed. There could conceivably be a
marginal CPU hit from keeping track of hidden animations, but
that's unrelated to textfield drawing.
I have noticed another thing. The problem is definitely worse the
longer the browser has been open.
You may be seeing more issues with windows that remain open for
long periods; there's an old bug that causes form controls to leave
permanent areas in windows that require redrawing for no good reason.
How do you file a bug for something like this?
There are already bugs tracking the several known redraw
inefficiencies that are causing the very poor text field
performance, and the circumstances causing them are well known.
-Stuart
_______________________________________________
Camino mailing list
[email protected]
http://mozdev.org/mailman/listinfo/camino
_______________________________________________
Camino mailing list
[email protected]
http://mozdev.org/mailman/listinfo/camino
