Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
Exchange
2000.active.directory
2000.admin
2000.announcements
2000.app.conversion
2000.applications
2000.clients
2000.clustering
2000.connectivity
2000.development
2000.documentation
2000.general
2000.information.store
2000.interop
2000.kms
2000.misc
2000.protocols
2000.realtime.collabo.
2000.setup
2000.transport
2000.win2000
admin
application.conversion
applications
clients
clustering
connectivity
design
development
misc
mobility
setup
tools
  
 
date: Wed, 23 Apr 2008 06:50:38 -0700 (PDT),    group: microsoft.public.exchange.clients        back       


OWA: Find Names Dialog box comes up when pressing space bar   
Exchange 2003, Windows XPsp2, IE6.

I wish to refer to these two threads:
http://groups.google.be/group/microsoft.public.exchange.clients/browse_thread/thread/714565a0494bb8cb/77e8f2f0fe5b8e19
http://groups.google.be/group/microsoft.public.exchange.admin/browse_thread/thread/4155d29f2adc9099/11915f561a24e9cc

I have some more info to successfully duplicate the issue.

In OWA, reply to an email.
Press "find names".
Add a name to the TO, CC or BCC.
Close the Find names window.
You will notice that the cursor is blinking in the message compose
control (where you type the message body). However if you look very
carefully, you will see that the focus is still on the CC button.
When you start typing, and press space, the find names window will pop
up. This is because the CC button was still under focus.

Workaround: when you come out the find names window, click inside the
message compose control to explicitly set the focus.

Observation: when you compose a new message, not a reply, and use find
names, the cursor is not blinking in the message compose control,
thereby not giving a misleading impression to the user that the
message body has focus. He will instinctively click inside the message
before starting to type.

It is my impression that this issue is related to the "click to
activate" issue that Microsoft had to introduce because of license
reasons with ActiveX controls.

My questions:
* Can anyone confirm the issue?
* Except for writing an FAQ to inform our users, what else can be done
to remedy the problem?

TIA,

Amedee
date: Wed, 23 Apr 2008 06:50:38 -0700 (PDT)   author:   Amedee Van Gasse

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us