IE Only Suggest Issue

We are using the spry 1.6 pre release suggest widget. Its
great, but in IE you can't click on the drop down list, although
the arrow keys and the enter key work fine.



Does anyone know what might cause this or how to fix it?



Thanks for any suggestions :-)IE Only Suggest Issue
The samples work in IE so there must be something wrong with
your coding, do u have a URL or code snip?IE Only Suggest Issue
Here is the code:

%26lt;!DOCTYPE html PUBLIC ''-//W3C//DTD XHTML 1.0
Transitional//EN'' ''
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd''%26gt;

%26lt;html xmlns=''
http://www.w3.org/1999/xhtml''
xmlns:spry=''
http://ns.adobe.com/spry''%26gt;

%26lt;head%26gt;

%26lt;meta http-equiv=''Content-Type'' content=''text/html;
charset=utf-8'' /%26gt;



%26lt;script language=''JavaScript'' type=''text/javascript''
src=''/js/includes/xpath.js''%26gt;%26lt;/script%26gt;

%26lt;script language=''JavaScript'' type=''text/javascript''
src=''/js/includes/SpryData.js''%26gt;%26lt;/script%26gt;

%26lt;script language=''JavaScript'' type=''text/javascript''
src=''/js/includes/SpryAutoSuggest.js''%26gt;%26lt;/script%26gt;

%26lt;!--- add style sheets ---%26gt;

%26lt;link href=''/css/SpryAutoSuggest.css'' rel=''stylesheet''
type=''text/css'' /%26gt;

%26lt;!--- Create the spry data sets for the suggest widget
---%26gt;

%26lt;script type=''text/javascript''%26gt;

var ds1 = new
Spry.Data.XMLDataSet(''/services/Provider/ddr/Admin/sites.cfm'',''sites/site'',
{ sortOnLoad: ''name''});

%26lt;/script%26gt;



%26lt;/head%26gt;

%26lt;body%26gt;

%26lt;form name=''frmAddEdit'' action=''/services/index.cfm''
method=''post'' id=''form1''%26gt;

%26lt;div id=''mySuggest'' class=''container''%26gt;

%26lt;b%26gt;Begin typing the organization name%26lt;/b%26gt;

%26lt;input type=''text'' name=''site'' size=''50''/%26gt;

%26lt;div id=''resultsDIV'' spry:region=''ds1''%26gt;

%26lt;div spry:repeat=''ds1''
spry:suggest=''{name}''%26gt;{name}%26lt;/div%26gt;



%26lt;/div%26gt;

%26lt;/div%26gt;

%26lt;div id=''dd_action''%26gt;

%26lt;input type=''hidden'' name=''page''
value=''ddrAdminNewReportingSitePost''%26gt;

%26lt;input type=''Submit'' value=''Add Reporting Site''%26gt;

%26lt;input type=''reset'' value=''Reset''%26gt;

%26lt;/div%26gt;

%26lt;/form%26gt;

%26lt;script type=''text/javascript''%26gt;

%26lt;!--

var theSuggest = new
Spry.Widget.AutoSuggest(''mySuggest'',''resultsDIV'',
''ds1'',''name'',{minCharsType:3,maxListItems:100,containsString:true,loadFromServe r:true,urlParam:'s'});



//--%26gt;

%26lt;/script%26gt;



%26lt;/body%26gt;

%26lt;/html%26gt;
I posted the code, does anyone have any ideas?



Thanks.


Any ideas? The code iis pretty straight forward, seems like
it should work.....
None of the suggest examples work correctly in IE on our
server. We just placed the Spry_P1_6_10-01 directory in out web
root, hit the suggest samples, and you can't click on any of the
drop down lists in IE. They all work fine in Firefox. This is a
Windows 2000 server running Apache 2.
Any ideas? Has anyone else seen this?
This sounds just like an issue I had - it had to do with not
properly adding an observer. Check this thread to see if it helps.




http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?catid=602%26amp;threadid= 1308451


phuntyme: thanks for the reply, but its hard to see how this
could be the problem since it affects every suggest widget on our
server, including all the Spry suggest samples. The samples work in
IE on Adobe's servers, but not on mine (at least as far as clicking
on the drop down lists is concerned.)
hey,

Does your version of
http://labs.adobe.com/technologies/spry/samples/data_region/DataSetMasterDetailS ample.html

work from your server? Are other data pages working? Is it
just AutoSugest that is failing?

Check your mime types and content type. Make sure the XML is
being served as text/xml or application/xml.

And as always, a real URL is infinitely helpful.

Thanks,

Don
Donald:



Thank you very much for the reply.



%26gt;Does your version of
http://labs.adobe.com/technologies/spry/samples/data_region/DataSetMasterDetailS ample.html

work from your server?



Yes, it works fine and you can click on those drop lists in
IE just fine.



%26gt;Is it just AutoSugest that is failing?



Yes, as far as I can tell. And just in IE, it works fine in
FIreFox. And only clicking on the drop down lists, the data loads
fine, the suggest widgets work, you just can't click on the drop
down lists in IE.



%26gt;And as always, a real URL is infinitely helpful.



I have put it on a production server on a temporary basis so
you can see for your self:




http://www.tcbdata.com/Spry_P1_6_10-01/sitemap.html



Hit any of the pages that use the suggest widget in IE.
Please let me know when you have had a look as I don't want to
leave the samples open on a production server for long.






Ok...thanks. I am seeing it on Labs as well. It is IE6 only.

We will look into it shortly and report back.

Don
I am having the same problem. I am unable to click on the
drop down list in IE6.
It looks like this broke when the use of an iframe was added
to make sure the menu appeared over any form elements on the page
in IE6. If you don't need to worry about that situation, you can do
the following to work around the situation. If you are using the
version of SpryAutoSuggest.js from the 1.6 release. Go to line 586
and you should see this:



Spry.Widget.AutoSuggest.prototype.createIframeLayer =
function(element)

{

...



simply add a return after the open brace:



Spry.Widget.AutoSuggest.prototype.createIframeLayer =
function(element)

{

return;

...



And that will prevent the iframe from ever being created.
This is an IE6 only bug.



--== Kin ==--
kinblas:



Thanks very much for the reply. My SpryAutoSuggest.js now
reads:



// createIframeLayer for Tooltip

// creates an IFRAME underneath a tooltip element so that it
will show above form controls and ActiveX

Spry.Widget.AutoSuggest.prototype.createIframeLayer =
function(element)

{

return;



I still cannot click on the dropdown lists in IE, however.
Just to be sure its not a caching issue, I cleared the browser
cache and the server template cache before testing. The change seem
not to have had any effect.