Hello All,

I am using the latest RC1 version of the ASP.NET AJAX and the latest version of the Control Toolkit.  I have a ModalPopup that contains an UpdatePanel which contains some buttons and some drop down lists.  I need this window to act like a little wizard, posting back as the users click the drop downs etc - your basic multi-step process.  Once the user process is completed, clicking on a complete button in the ModalPopup will end the process and close the ModalPopup window using the .Hide() method.  The first issue I had to work through was that the ModalPopup would close during the postback but I solved this by issuing a .Show() in the Postback button click event handler (throwing that in just in case in makes a difference).  Now the issue I have is that in Firefox, if the postbacks happen, and I close the window programatically or otherwise, the ModalPopup disappears like expected, but the window remains modal, meaning that the elements on the page cannot be clicked, almost as if the browser is frozen.  This is working fine in IE7, it's only in firefox where I get this issue. 

 
Any help on this issue would be greatly appreciated as the this is a show stopper for the client.

 

 Here is the little ModalPopup panel

1    <asp:Panel ID="pnlBuyBox" runat="server" CssClass="buyBox" Style="display: none;">
2                <asp:UpdatePanel runat="server" ID="pnlUpdateBuyBox">
3                    <ContentTemplate>
4                        <div>
5                            <asp:Label runat="server" ID="lblPFName"></asp:Label>
6                            -
7                            <asp:Label runat="server" ID="lblEntryID"></asp:Label>
8                        </div>
9                        <asp:Repeater runat="server" ID="rptChoices">
10                           <ItemTemplate>
11                               <div>
12                                   Select Options:
13                               </div>
14                               <div>
15                                   <%#Eval("Prompt")%>
16                                   :
17                                   <asp:DropDownList runat="server" ID="ddlChoices">
18                                       <asp:ListItem Text="choice1" Value="choice1"></asp:ListItem>
19                                       <asp:ListItem Text="choice2" Value="choice2"></asp:ListItem>
20                                       <asp:ListItem Text="choice3" Value="choice3"></asp:ListItem>
21                                       <asp:ListItem Text="choice4" Value="choice4"></asp:ListItem>
22                                   </asp:DropDownList>
23                               </div>
24                           </ItemTemplate>
25                       </asp:Repeater>
26                       <asp:Button runat="server" ID="btnTest" Text="Can I Post Back" OnClick="btnTest_Click"></asp:Button><br />
27                       <asp:Button runat="server" ID="btnDone" Text="Can I Quit this" OnClick="btnDone_Click"></asp:Button><br />
28                       <asp:Button runat="server" ID="btnOK" Text="OK" />
29                       <asp:Button runat="server" ID="btnCancel" Text="Cancel" />
30                   </ContentTemplate>
31               </asp:UpdatePanel>
32           </asp:Panel>

 

the ModalPopup Control

 <ajaxToolkit:ModalPopupExtender ID="mpeBuyBox" runat="server"
                                        TargetControlID="lnkDetails"
                                        PopupControlID="pnlBuyBox"
                                        DropShadow="true"
                                        OkControlID="btnOK"
                                        OnOkScript="onOK()"
                                        CancelControlID="btnCancel" />

  

Some of the Event Handling Code Stubs 

1    Sub btnTest_Click(ByVal sender As Object, ByVal e As EventArgs)
2            lblEntryID.Text = "I Changed this " & DateTime.Now.ToString()
3            mpeBuyBox.Show()
4        End Sub
5    
6    
7        Sub btnDone_Click(ByVal sender As Object, ByVal e As EventArgs)
8    
9            mpeBuyBox.Hide()
10       End Sub

  

I'm guessing from the 0 replies that cross browser support isn't an overwhelming concern with this product.

I'm having the same issue...  IE7 works fine but the new firefox does not...

 

I have only been using the toolkit for a few days now, under the assumption that it was complaint with browsers other then IE (accounting for ~60% of my userbase). I ran though each of the samples and they all seemed to function on Firefox. A response from a developer would be appreciated on this. If it is not cross-browser complaint (or at least of that is not the intention of the development team... ) I shall cease using it immediately and switch to JSP / GWT . -Steve

It's good when it works...

 Being a realitivly new library things are going to break.

It's up to you, go with a safe(er) solution -or- grin and bear it when things don't work (because they will break).  You have multiple browsers and none of them work exactly the same way.  When browsers versions change (like with firefox) any certenty of reliability is non existent.  Now, this is not to say in the future it will not be made to function browser xyz, but in the here and now, while you are waiting for the new AjaxToolkit.dll, you WILL catch hell from your boss/client because your solution does not appear to work.  They will not care about the reason why, just that they want what the paied for, a working solution.

 

I completely agree with you Matthew,   All software has bugs.. this is a given..

This is the beauty of open source software.. If there is a critical bug that breaks my app. I have the code to fix it myself.

However I was concerned with the previous post of:

    "I'm guessing from the 0 replies that cross browser support isn't an overwhelming concern with this product."

 And the fact that this was not given a reply.

If the development team do not even intend for the Library to work on anything but IE.. then I would have to stop using it immediately. Which I do not wish todo as it seems like an excellent toolkit.

However if cross browser support is a one of the objectives of the project (which I has assumed as a given until I read this post) confirmation of this, and which browsers it is intended to work with would be nice.

-Steve 

 

 

It is suppose to be cross browser.

Currently "Atlas" is planning to support IE, Firefox, and Safari.

From the FAQ, http://forums.asp.net/thread/1293293.aspx

 

 

If there's anyone reading this thread who's actually still having trouble with a ModalPopup, an UpdatePanel, and Firefox, could you please post your code so I can check it out?

I tried the code at the top of this thread (filling in the missing pieces like a data source, an onOK function, and the buyBox style), and I didn't have any trouble in IE7 or Firefox 2.0.0.1.

Here is some code that fails with FF 2.0.0.1 but works in IE7. 

    <form id="form1" runat="server">
        <asp:ScriptManager ID="ScriptManager1" runat="server" />
        <asp:UpdatePanel ID="ModalUpdate" runat="server" UpdateMode="Always">
        <ContentTemplate>
            <asp:Button ID="ModalButton" runat="server" Text="Click Me" OnClick="ModalButton_Click" />
            <asp:LinkButton id="FakeControl" runat="server"/>
            <asp:Panel ID="ModalPanel" runat="server" height="100px" Width="200px" style="display: none">
                <div style="text-align: center">Modal Test Panel</div>
                <br />
                <asp:LinkButton ID="ModalClose" runat="server" Text="Close Window"/>
            </asp:Panel>
             <cc1:ModalPopupExtender ID="ModalPopupExtender1" CancelControlID="ModalClose" PopupControlID="ModalPanel" TargetControlID="FakeControl" runat="server"/>
         </ContentTemplate>
         </asp:UpdatePanel>
    </form>

 
If you take out the update panel it works in FF as well.

 Here is the code behind

    protected void ModalButton_Click(object sender, EventArgs e)
    {
        ModalPopupExtender1.Show();
    }

  

Between my previous post and looking at the code Matthew just posted, I upgraded to Firefox 2.0.0.2 (I was on 2.0.0.1), and now neither code sample (the original poster's or Matthew's) work correctly.

Matthew, are you on 2.0.0.2 also?

Actually, the original poster's code still works like it used to... it was a slightly modified version (with the ModalPopupExtender inside the UpdatePanel) that used to work and now doesn't.

Still investigating...

Yes, I'm 2.0.0.1...

 
The sample I made used to work on FF before I upgraded.

 

I'm confused.  I asked "Are you on 2.0.0.2?" and you answered, "Yes, I'm 2.0.0.1."  Which is it? :-)

If you're still on 2.0.0.1, then I don't believe we're seeing the same issue.  I've now tried my tests on both 2.0.0.1 and 2.0.0.2, and I only see the failure on 2.0.0.2.

Just to update the thread, I think I've tracked this down to a change between 2.0.0.1 and 2.0.0.2 in the way Firefox handles dynamically added script tags.  I've pinged some people internal to Microsoft to help me investigate.  Someone will update this thread as soon as we know more.

The issue I'm following is specific to Firefox 2.0.0.2, so if you're having trouble on an earlier version, this is likely unrelated.

I can confirm that the example code given in the most recent post in the thread, fails on Firefox v2.0.0.2 and passes on v2.0.0.1 on three of my systems.

 -Steve