I do not use JQuery but I believe that once when I was searching the
Internet for something else I saw that JQuery has a function called $ that
did just that. And the author showed the Javascript code from that library.
I'm not sure if that is what I need but now that I want it I can't find it.
Bottom line: Can you point to (or supply) Javascript code to recursively
search for a element given it's Id?
Thanks in advance
Perhaps you mean something like
var element = document.getElementById('someID');
regards
A.G.
Just use
var element = document.getElementById('someID');
Cal Who wrote:
Javascript code to recursively search for a element given the element's Id
22-May-10
I need Javascript code to recursively search for a element given the
element's Id so that I can modify a elements attributes.
I do not use JQuery but I believe that once when I was searching the
Internet for something else I saw that JQuery has a function called $ that
did just that. And the author showed the Javascript code from that library.
I am not sure if that is what I need but now that I want it I cannot find it.
Bottom line: Can you point to (or supply) Javascript code to recursively
search for a element given it is Id?
Thanks in advance
Previous Posts In This Thread:
Submitted via EggHeadCafe - Software Developer Portal of Choice
Free Online Courses Available for Eggheadcafe.com Users
http://www.eggheadcafe.com/tutorials/aspnet/5261083e-6e03-4b25-8728-fc3cf6855293/free-online-courses-avail.aspx
<script type="text/javascript">
function SetMargins(id) {
var element = document.getElementById(id);
...
Which is in the .master and the id looks like I'd expect:
id = "ctl00_BottomImageCPH_QQQ"
I called it from and aspx.vb file
<asp:Content ID="Content8" runat="server"
ContentPlaceHolderID="BottomImageCPH">
<script type="text/javascript">
SetMargins('<%=QQQ.ClientID%>');
</script>
<div runat="server" id="QQQ" style="margin-left: 10%; margin-right: 10%;" >
...
Why the null??
Thanks
> Why the null??
Because of ASP.NET's control ID munging.
var control = document getElementById('<%=MyControl.ClientID%>');
--
Mark Rae
ASP.NET MVP
http://www.markrae.net
From the second snippet it appears the SetMargins method is being
called as the document is rendered. The document is rendered from top
to bottom. If SetMargins is called before control QQQ is rendered to
the document, the document won't find the control, and
document.getElementById will return null.
You may have to read that last sentence a couple of times ;)
I would suggest attaching a javascript method to the page body's
onload event. That method will be called after the page has been
rendered. From within that method make the call to SetMargins.
regards
A.G.
No?
As ways, Thanks
>
> You may have to read that last sentence a couple of times ;)
>
> I would suggest attaching a javascript method to the page body's
> onload event. That method will be called after the page has been
> rendered. From within that method make the call to SetMargins.
But there are no events in a content page, is there?
>
> regards
> A.G.
Thanks
> No?
Yes, but it seems from other replies that you're trying to call the
SetMargins function before the page is completely rendered, which is why
it's not finding the control...
This is true but a solution can be found at
http://www.webreference.com/programming/javascript/onloads/
regards
A.G.
I moved the call to right after the </div> and that seems to have fixed it.
I'm not sure if that is a reliable way.
Do you think adding an event would be more reliable (say over different
browser types)
In this situation I don't see the "magically change" he referred to
probably because the rendering and change is so close.
In any event I'm saving that link for possible later need- good stuff.
Thanks
Thanks
I would use the onload event because the page has been loaded. Leaving
the call in-line with the rendering works but is subject to error if
the mark-up gets re-arranged by someone else. AFAIK all browsers
support the onload event so that should not be an issue.
>In this situation I don't see the "magically change" he referred to
>probably because the rendering and change is so close.
>
If the user could see the change there wouldn't be any magic ;)
>In any event I'm saving that link for possible later need- good stuff.
>
regards
A.G.