You searched for the word(s): userid:610573

More Search Options

RSS Available

• Re: ModalPopup Closes on button click

  I had this problem. I'd put an UpdatePanel around the Modal Popup Panel. I removed the UpdatePanel from around the Modal Popup Panel and put it inside the Modal Popup Panel. Then I made sure my button was inside the UpdatePanel. (Leave any OK / Cancel buttons outside the UpdatePanel). That should do the trick!

  Posted to ASP.NET AJAX Control Toolkit (Forum) by renesisx on 8/2/2007

• Re: GridView filtering real time - letter by letter

  As with most ASP.NET Ajax sites, there will be significant changes required for Beta 1. From here Steve Marx's site seems to be off-line. Perhaps he's upgrading his blog (and the filtering textbox control) right now? ;)

  Posted to ASP.NET AJAX UI (Forum) by renesisx on 10/24/2006

• Re: ERe: Atlas Unknown Error Popup on Session Exipry - Requesting fix

  As usual, the deathly sounds of tumbleweed flow through here in the direction of Redmond. Due to the level of support Microsoft is currently (not) offering on these forums, I can't possibly in any way recommend using ASP.NET AJAX. I would recommend anyone thinking of trying it out to look at more mature open source alternatives, or wait until v1.0 of this product when MS have promised proper support. At least then I'd be able to force answers out of Microsoft using my MSDN subscription. Until

  Posted to ASP.NET AJAX UI (Forum) by renesisx on 10/17/2006

• Re: Atlas Unknown Error Popup on Session Exipry - Requesting fix

  I'm guessing you guys are using ASP.NET Forms Auth - and the login cookie is expiring. From what I can tell, ASP.NET Ajax throws an "Unknown Error" when it makes a XmlHttp call and gets a response which isn't what it was expecting. In the case of a session expiry, instead of the page fragment it was expecting it suddenly gets back a "You need to login" page, or a 500 error, or a 404. It doesn't know what to do, and dies with an "Unknown Error". I'm going

  Posted to ASP.NET AJAX UI (Forum) by renesisx on 10/5/2006

• Re: GridView filtering real time - letter by letter

  This LiveTextBox is certainly my favourite Ajax control so far. I have 3 current issues with it though: 1) When a user clicks out of the textbox, it also causes a PostBack (I guess caused by the autopostback="true" on the control). Is there a way of stopping this/cancelling the event? 2) Let's say you have a TextBox, LiveTextBox, Checkbox and an UpdatePanel on the same page. If you type in the TextBox and then click the Checkbox it just works. If you type in the LiveTextBox, then click

  Posted to ASP.NET AJAX UI (Forum) by renesisx on 10/5/2006

• Re: Atlas + Valid XHTML => Solution

  Thank you very much Bertrand. This is exactly the answer this thread needed - some straightforward technical answers, with the design decisions behind those answers. More posts like that one would be highly appreciated around here! Now I can understand your point of view as well and see why you took the decisions you did. I'm no longer bitter and twisted ;) I need to go back and stop serving strict Mime Types to Firefox and then work on fixing the pages when this is removed, but I'll live

  Posted to ASP.NET AJAX Discussion and Suggestions (Forum) by renesisx on 10/3/2006

• Re: Atlas + Valid XHTML => Solution

  Bertrand, As far as I'm aware, IE barfs if you show it CDATA, even on completely valid XHTML, so if you did have to drop CDATA headers you'd have to make it browser-selective. I can solve the CDATA header with the hack we've come up with in this thread which rewrites the HTML on the way down the pipe. What is a bigger issue for me is the fact the Atlas JS files have been coded without using the DOM. There are things like "innerHTML" in there. I don't know why that decision

  Posted to ASP.NET AJAX Discussion and Suggestions (Forum) by renesisx on 10/2/2006

• Re: Atlas + Valid XHTML => Solution

  Guys, What do you think of the feasibility of us forum people creating a patch for the Atlas .js files to fix this missing functionality? Do you think this is possible, or is some of the Javascript hidden in DLL files that we'd need to reverse engineer? I have my doubts that Microsoft will look at this problem before 1.0, which means waiting perhaps another year till the next supported release (Orcas) before we get support for current web standards. We've managed to patch the script block

  Posted to ASP.NET AJAX Discussion and Suggestions (Forum) by renesisx on 9/29/2006

• Re: Atlas + Valid XHTML => Solution

  wolfcw1: I thought we were working on a fix for the xml-script blocks that Atlas renders in your pages? The javascript Atlas uses is in an external js file and should never affect XHTML validation. I think this thread is more of a "Is it possible to make Atlas work with the current web standards (XHTML)?" These are the 2 things stopping it right now: 1) ASP.NET / Atlas need to wrap the script blocks (Javascript/Xml-Script) with CDATA tags on non-IE browsers. We have fixed that with a hack

  Posted to ASP.NET AJAX Discussion and Suggestions (Forum) by renesisx on 9/29/2006

• Re: Atlas + Valid XHTML => Solution

  I could create that, it would be fairly straightforward, but it would only fix ASP.NET, not Atlas. The problem here is that Atlas isn't using the DOM in its Javascript, so it remains completely incompatible with XHTML1.1

  Posted to ASP.NET AJAX Discussion and Suggestions (Forum) by renesisx on 9/27/2006