Javascript – How do I find out what is causing Edge Developer Tools to be BLANK on the company ASP.NET WebForms website?

As a general rule, when using a update panel, you have to open the developer tools (f12) in the browser BEFORE the page loads!

If not, and you jump to some page, then open developer tools, and hit refresh on the browser, and THEN click on buttons etc.

I recently learned how to use a timer to update Page 1 when dialog on Page 2 calls a 3rd dialog on Page 3. Page 3 sets a Session variable, and Page 1 listens for it.

Apparently not!

Really, I don’t suggest such a hack design be attempted at all. What happens if the user opens up more then one tab? Really, but really really, this is not going to produce a stable nor robust enviorment.

Since popup blockers are LONG gone from the web land, then I suggest you simply replace the popups with a NICE popup utility. I at one time used the AjaxToolKit dialog, but far better is to build a REALLY nice dialog control (ascx). That way, for any page, you can simple drag + drop in this dialog control, and you are off to the races.

As for what (of many choices) dialog popup to use? Well, there is the bootstrap ones, but they are kind of jinkey in terms of how they are launched. Best choice is thus to adopt the jQuery.UI one, and it REALLY works nice.

How do these dialog utilities get past the popup blocker? Why of course they "fake" the popup, and use a div that is created, and with css, they look like a popup, behave like a popup, but are standard HTML markup, and thus no popup block will care, touch, or prevent as such, since then the browser would have to stop working and stop allowing standard HTML markup to work!!

So, say we have say some delete button, (server side code), and we want to popup a prompt to confirm the button click. So, if user hits no, then we do nothing, but if user hits yes, then we want the given button code to run.

So, say this markup:

        <asp:Button ID="cmdDelete" runat="server" Text="Delete"
            OnClientClick="return mydelete(this);"
            OnClick="cmdDelete_Click"
            CssClass="btn myshadow"
            />
        <br />
        <br />
        <br />
        <asp:Label ID="lblMsg" runat="server" Text=""></asp:Label>

        <div id="mypopdiv" style="display:none">
            <h3>Delete this record</h3>
            <h4><i>(this can't be undone)</i></h4>
        </div>


    <script>
        var mydeleteok = false
        function mydelete(btn) {

            if (mydeleteok) {
                mydeleteok = false
                return true
            }
            myDialog = $("#mypopdiv")
            myDialog.dialog({
                title: "Delete ?",
                modal: true,
                sizable: true,
                width: '300',
                appendTo: "form",
                closeText: "",
                dialogClass: "dialogWithDropShadow",
                position: { my: 'left top', at: 'right bottom', of: btn },
                buttons: [
                    {
                        id: "mydel",
                        text: "Delete",
                        class: "btn myshadow",
                        click: function () {
                            myDialog.dialog('close')
                            mydeleteok = true
                            $(btn).click()
                            return
                        }
                    },
                    {
                        id: "Cancel",
                        text: "Cancel",
                        class: "btn myshadow",
                        click: function () {
                            myDialog.dialog('close')
                        }
                    }
                ]
            })
            return false
        }
    </script>

And code behind is thus this:

Protected Sub cmdDelete_Click(sender As Object, e As EventArgs)

    lblMsg.Text = "Server code delete will run"


End Sub

Hence, the result is if user hits "delete", then code behind runs. If user hits cancel, then the server side code does not run.

So, the above gives a nice dialog, and also gives a nice (easy) way to conditional run a button click.

And the above jQuery.UI dialog also works well for display of any "div" content.

So say for editing, then we can use the dialog like this:

So, in place of attempting to use some loop with session() (which is going to be difficult at best), I suggest you replace the window() pops with a jQuery.UI dialog control. Obviously you want to build a nice re-useable library for this purpose, and have some kind of "my pop" routine that you can call with some parameters. Either way, adopting some kind of dialog system for your code will not only allow far easier refactoring by replacing the window() popup with a call to some JavaScript library, but you dialog code can follow a rather "similar" design pattern to what you have now. This would be far better then attempting to poll some other page via session().