Last post Feb 23, 2007 05:45 PM by yendi
Oct 30, 2006 01:48 PM|iclements|LINK
There is a bug with ASP.NET Ajax Beta 1.0 when an AutoCompleteExtender control is used within a page which inherits from a master page. I havnt included an example because its dead easy to recreate the error using a basic web service.
have seen many people raise this issue and they are just being told to include [ScriptService] at the start of their web service class, however this does not resolve the issue. My web service includes this attribute yet it still does not work but in a normal
web form with no master pages involved it works like a dream. Any help or advice would be greatly appreciated.
Oct 31, 2006 04:08 PM|joshlrogers|LINK
In your web.config file have you changed the prefix back to atlas where it says asp?
<add tagPrefix="atlas" namespace="Microsoft.Web.UI" assembly="Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<add tagPrefix="atlas" namespace="Microsoft.Web.UI.Controls" assembly="Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<add tagPrefix="atlas" namespace="Microsoft.Web.Preview.UI" assembly="Microsoft.Web.Preview"/>
<add tagPrefix="atlas" namespace="Microsoft.Web.Preview.UI.Controls" assembly="Microsoft.Web.Preview"/>
Nov 01, 2006 08:36 AM|iclements|LINK
Hi Josh, I tried your suggestions but no joy unfortunatly.
Web service is not the issue although because the extender works fine in a normal page.
Nov 01, 2006 12:50 PM|joshlrogers|LINK
I do not know if this helps or not, but I was having the exact same situation under a master page (which is all I use and I have the autocompleteextender working) as well. If you are using a panel as your Completion List Element then you need to make sure
that it is actually visible. I have read another post on here and a few blogs that say it is supposed to be set to not visible by default....but this only caused js errors. It seems that once you set the CompletionListElementID to the panel the js will handle
making it not visible....hope this helps..
Nov 02, 2006 08:17 AM|iclements|LINK
No problem Josh, I double checked the visibiltiy of the panels and stuff but still broke :-(. Are you using the latest ATLAS Beta 1 release because I have seen a number of posting from people with the same problem as me and no fixes anywhere so I am pretty
confident this is a bug that has been introduced in the Beta.
Thanks anyway for the suggestions.
Jan 03, 2007 10:01 PM|surrealis|LINK
I am getting this very same issue. I have tried it in a none master page senario and it works fine. I have the lastest downloads as of today...
Did you ever find a solution.
Thanks ahead of time,
Feb 23, 2007 05:44 PM|yendi|LINK
Same issue here... it seems the previous release was more reliable than this one! MS guys... please help us... I'm getting: Error: [Exception... "'Sys.ArgumentNullException: Sys.ArgumentNullException: Value cannot be null.
Parameter name: element' when calling method: [nsIOnReadyStateChangeHandler::handleEvent]" nsresult: "0x8057001c (NS_ERROR_XPC_JS_THREW_JS_OBJECT)" location: "<unknown>" data: no] with autocomplete and ValidatorCallout and PopupControlExtender, so far...
Thanks in advance for ANY help... it will be highly appreciated.
ajax control Toolkit beta2
Feb 23, 2007 05:45 PM|yendi|LINK