I've started collecting bugs/issues for the June CTP, and updating the status of the previous ones.

hello guys,

btw, i've obtained an answer regarding the proxy generation change introduced in this last ctp:

http://forums.asp.net/thread/1342493.aspx

To reproduce it:

<atlas:UpdatePanel ID="UpdatePanel1" runat="server" Mode="Always">

<ContentTemplate>

<table id="Table1" style="width: 375px">

<tr>

<td style="width: 400px">

<asp:TextBox ID="TextBox1Atlas" AutoPostBack="true" runat="server" MaxLength="5" Width="75px" OnTextChanged="TextBox1Atlas_TextChanged" ></asp:TextBox>

<asp:Label ID="Label1" runat="server" Text=""></asp:Label></td>

</

tr>

</

table>

</

ContentTemplate>

</atlas:UpdatePanel>

<

atlas:AutoCompleteExtender ID="AutoCompleteExtender1" ServicePath="Atlas.asmx" ServiceMethod="GetSuggestions" MinimumPrefixLength="1" runat="server">

<atlas:AutoCompleteProperties TargetControlID="TextBox1Atlas" Enabled="true" />

</

atlas:AutoCompleteExtender>

The drop down will stay in the screen after the panel updates.

Here is the post about the bug:

http://alpascual.com/blog/al/archive/2006/07/23/235.aspx

Cheers

Al

 

Hello guys.

i'd like to add another bug/suggestion to the list (it really depends on how you see it). I've just started looking at the javascript client source atlas.js file and i've noticed that there still isn't a way to  let us influence the type of request that is being (that decision is automatically made by you based on the bode value). yep, it's true that most of the times this is the correct decision, but i'd like a little more power here and i'd like to be able to decide on how to do this.

thanks.

Hi guys,

The problem is that the atlas script manager includes UpdatePanel name in xml script even if this panel is marked as Visible="False" (panel code doesn't exist in final HTML sent to browser). This causes a JavaScript error (Object Not Found).

below is the code to reproduce bug:
<atlas:ScriptManager ID="ScriptManager1" runat="server" EnablePartialRendering="true" />
<atlas:UpdatePanel ID="panel1" Mode="Always" runat="server" >
<ContentTemplate>
    <asp:Label runat="server"  ID="label" />                   
</ContentTemplate>
<Triggers>
    <atlas:ControlEventTrigger ControlID="button" EventName="Click" />
</Triggers>
</atlas:UpdatePanel>

<asp:Button ID="button" runat="server" OnClick="ButtonOnclick" Text="First" /> 
        
<atlas:UpdatePanel ID="panel2" Mode="Always" runat="server" Visible="false">
<ContentTemplate>                       
    <asp:CheckBox runat="server" ID="checkBox1" Checked="true" Visible="true" />              
</ContentTemplate>
</atlas:UpdatePanel>  

more in thread: http://forums.asp.net/thread/1278373.aspx

Hello.

one more bug that exists for a while and i've seen it today again: scriptmanager class uses the _updatepanels field during the renderformcallback withouth checking if there are any panels. this results in an exception, as you might see by this thread:

http://forums.asp.net/thread/1350737.aspx

btw, i had already mentioned this on the thread that announced the june ctp. 

Let's not forget that ATLAS doesnt work *AT ALL* with Opera.

Also, please add the bug found here http://forums.asp.net/thread/1335049.aspx to the list.

So I'm confused here. Is bug #12 back with the June CTP?

Basically I had WebParts and ATLAS living in harmony before I downloaded the June CTP, and now I'm back to the situation in which Firefox drag and drop doesn't work. Well, thats not quite fair: it works once per session. You can open up a page in Firefox, do one drag, and when the page does a partial reload you cannot drag and drop anymore. If you do a full page reload, you can do another d-n-d.

Works great in IE, like always. I am still using the tag mapping trick, and I have a single UpdatePanel surrounding all WebPartZones.

Any ideas? Let me know if this issue is already documented, but I didn't see it in any of the ATLAS forums. Thanks guys!

AHA! I found this issue, it was reported as an toolkit/extension issue here. I'll post there to point out that it is a WebParts issue too.

howdy.

two more nasting bugs...

http://forums.asp.net/1355881/ShowThread.aspx#1355881
http://forums.asp.net/thread/1355860.aspx

i'm starting to think that maybe it's better to go try something else...

 

I don't know if this is the correct place to post an issue, but i have a problem with firefox, the OnApplicationLoad event isn't fired, and the code that initialize the page don't work with firefox. 

¿where is the official bug tracker?

hello.

well, currently this is it!

Why there are so many bugs on Atlas? How after that long cannot get it right? There are other people like telerik.com or componentsart that got a working version of AJAX controls without problems. It just does not make any sense.

My 2 cents again

Al

The reason you are seeing bugs is that Atlas has not been released. It is still a community technology preview that allows folks to use Atlas and provide feedback to the product team.

tholewis:

The reason you are seeing bugs is that Atlas has not been released. It is still a community technology preview that allows folks to use Atlas and provide feedback to the product team.

what about the go live license? i don't have any atlas product out yet and if you ask me, i'll probably say that currently i'll only build toy apps with it. btw, most of the bugs presented here have at least 4 months...this is really bad because there are several guys here that have identified several bugs (and even lost their time trying to suggest a fix). the minimum the atlas team could do is to give feedback on the status of the problems detected here...

btw, just another suggestion, i really think the team should pass the message that atlas is more than updatepanels surrounding server controls...after using it (and these forums) for several months, it still looks like the wrong message is being passed from the team (ie, you can build ajax apps from the server side - to me this is simply wrong, wrong and wrong again).

just one more thing: to me, it makes more sense to solve all the bugs that have been identified and then extend the platform with more components (as you know, there's been several releases of extra components - atlas toolkit - but the main problems haven't been solved yet).

thanks.