Karl Stuart Reporter
	Description • 20 years ago

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a2) Gecko/20040714
Build Identifier: Mozilla 1.8a2

When tabbing between the different fields the cursor does'nt reappear. It moves
but you must count the number of times you press tab to know which field it is
in. Also if you click on a field after the tab has been used then the cursor
does not appear untill you begin typing again.

Reproducible: Always
Steps to Reproduce:
1.open address book 
2.type in field and press tab to move to next field
3.also cilck on any field after the tab has been used and you will find no
blinking cursor untill you type

Actual Results:  
cursor dissappeared untill typing resumed

Expected Results:  
blinking cursor to tell you which field you have tabbed to or clicked on

	R.K.Aa.
	Comment 1 • 20 years ago

Perhaps related:
Testing tabbing in AB on a current CVS build, Linux, i crash. Top of stack:

#0  0x00f0b808 in js_PCToLineNumber () from ./libmozjs.so
#1  0x00ec3524 in js_ReportErrorNumberVA () from ./libmozjs.so
#2  0x00ebdb10 in JS_ReportErrorNumber () from ./libmozjs.so
#3  0x00ed72a8 in js_ReportUncaughtException () from ./libmozjs.so
#4  0x00ebd57d in JS_CallFunctionValue () from ./libmozjs.so
#5  0x00c2ff59 in nsXPCWrappedJSClass::CallQueryInterfaceOnJSObject ()
   from /home/dark/MOZ/TREE1/mozilla/dist/bin/components/libxpconnect.so
#6  0x00c30905 in nsXPCWrappedJSClass::DelegatedQueryInterface ()
   from /home/dark/MOZ/TREE1/mozilla/dist/bin/components/libxpconnect.so
#7  0x00c2d033 in nsXPCWrappedJS::AggregatedQueryInterface ()
   from /home/dark/MOZ/TREE1/mozilla/dist/bin/components/libxpconnect.so
#8  0x045d31ad in nsBindingManager::GetBindingImplementation ()

	R.K.Aa.
	Comment 2 • 20 years ago

the crash may be bug 252032

	R.K.Aa.
	Comment 3 • 20 years ago

original bug reported here may be caused by checkin for bug 175893?

	timeless
	Comment 4 • 20 years ago

*** This bug has been marked as a duplicate of 252032 ***

	R.K.Aa.
	Comment 5 • 20 years ago

Reporter's build is from the 14th - two days before the checkin that likely
cause bug 252032. (changes to jsapi.c on the 16th, for bug 243869)
Still suspecting the checkin for bug 175893 to be the origin for what reporter
here see - at least the date matches.

Reopening.

	timeless
	Comment 6 • 20 years ago

sorry, the original bug report is not about my crash, it's just that because of
my crash you can't play w/ the original bug report.

	R.K.Aa.
	Comment 7 • 20 years ago

Testing a build WITH the fix for bug 252032: WFM.
Focus or selection is indicated when tabbing, caret blinks when in forms.

Windows only, or fixed sometime in the last week?

	Gervase Markham [:gerv]
	Comment 8 • 19 years ago

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

	Gervase Markham [:gerv]
	Comment 9 • 19 years ago

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.