AjaxControlToolkit TabContainer 准备好时的 Javascript 吗？

发布于 2024-11-16 15:35:45 字数 731 浏览 4 评论 0原文

我有一个带有 TabContainer 控件（来自 Ajax Control Toolkit）的页面，我根据当前选择的选项卡切换页面上某些元素的可见性。我一直在 OnClientActiveTabChanged 的事件处理程序中执行此操作（效果很好），但我发现它在回发后使页面处于错误状态。我尝试向 document.ready 事件处理程序添加一些代码来获取索引，但是当我执行以下操作时：

$(document).ready(function () {
    var index = $('#<%= TabContainer1.ClientID %>').[0].control.get_activeTabIndex();
    // Do some stuff with the index
});

...我在 .control 财产。有没有办法为 TabContainer 挂钩客户端“就绪”事件？

我不熟悉普通 DOM 元素的事件生命周期（似乎应该有一个通用的 onload 事件，但我没有看到）。如果没有可以轻松处理的事件，似乎可以添加一个带有 UpdateMode=Conditional 的 UpdatePanel 和一个指向带有 onclick 事件处理程序的隐藏按钮的 AsyncPostBackTrigger获取活动选项卡索引——但这对于我期望 DOM 已经公开的东西来说似乎有很多移动部分。

原文

I have a page with a TabContainer control (from the Ajax Control Toolkit), and I toggle the visibility of some elements on the page depending on the currently-selected tab. I'd been doing this in an event handler for OnClientActiveTabChanged (which works fine), but I discovered that it leaves the page in the wrong state after a postback. I tried adding some code to the document.ready event handler to get the index, but when I do the following:

$(document).ready(function () {
    var index = $('#<%= TabContainer1.ClientID %>').[0].control.get_activeTabIndex();
    // Do some stuff with the index
});

...I get a null reference exception on the .control property. Is there a way to hook a client-side "ready" event for the TabContainer?

I’m not familiar with the event lifecycle with normal DOM elements (it seems like there ought to be a general onload event, but I don’t see one). If there isn’t an event that can be easily handled, it seemed like it might work to add an UpdatePanel with UpdateMode=Conditional and an AsyncPostBackTrigger that pointed to a hidden button with an onclick event handler that would get the active tab index – but that seems like a lot of moving pieces for something that I’d expect the DOM to expose already.

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

梦巷 2024-11-23 15:35:45

为时已晚，无法提供帮助，但我遇到了同样的问题并找到了解决方法。
将您的代码更改

$(document).ready(function () {
    var index = $('#<%= TabContainer1.ClientID %>').[0].control.get_activeTabIndex();
    // Do some stuff with the index
});

为

function pageLoad() {
    var index = $('#<%= TabContainer1.ClientID %>').[0].control.get_activeTabIndex();
    // Do some stuff with the index
};

此处的说明：
http://encosia.com/document-ready-and- pageload-are-not-the-same/

基本上，jQuery的ready事件“有点早”，TabContainer还没有初始化，而客户端ASP.Net的pageLoad已经足够晚了，TabContainer已经初始化到那时。

Too late to be helpful, but I've had the same issue and found a workaround.
Change you code

$(document).ready(function () {
    var index = $('#<%= TabContainer1.ClientID %>').[0].control.get_activeTabIndex();
    // Do some stuff with the index
});

function pageLoad() {
    var index = $('#<%= TabContainer1.ClientID %>').[0].control.get_activeTabIndex();
    // Do some stuff with the index
};

Explanation here:
http://encosia.com/document-ready-and-pageload-are-not-the-same/

Basically, jQuery's ready event is "a bit early" and the TabContainer is not initialized yet, whereas the client side ASP.Net's pageLoad is late enough and the TabContainer has been initialized by then.

回复收藏 0 原文