Hello,
In my C# asp.net 2.0 application, I have a webform with a button server
control on it. The webform, like most others in the site, subscribes to
a master page. I have determined that the button always renders with an
id of "ct100_ContentPlaceHolder1_btnContinue" in both the IE and
Firefox browsers.
I created the following javascript code segment to disable it when the
page loads. I have reasons for not wanting to do this with server side
code...
document.all['ct100_ContentPlaceHolder1_btnContinue'].disabled = true;
Now, when I view this in IE, the button is disabled. But when I view it
in Firefox, it's not. Also, there are no javascript errors returned by
either browser. Also, I have already updated my browserCaps section in
web.config, if that is relevant.
Why does the button remain enabled when viewing the page with Firefox?
11  7337 
YOu need to actually query, in code behind, to determine what the postback
event is for the control and emit the JavaScript accordingly. I am not sure
this conquers all Firefox issues, but it guarantees a proper path down the
rabbit hole even if you rename the control for some reason. I do not have a
sample for this.
If you have to go absolutely generic, you can get the control that posted
from Request["EVENTTARGET"], but this does not work with all controls.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
*************************************************
Think outside of the box!
*************************************************
"Joey" <jo*********@topscene.comwrote in message
news:11**********************@h48g2000cwc.googlegr oups.com...
Hello,
In my C# asp.net 2.0 application, I have a webform with a button server
control on it. The webform, like most others in the site, subscribes to
a master page. I have determined that the button always renders with an
id of "ct100_ContentPlaceHolder1_btnContinue" in both the IE and
Firefox browsers.
I created the following javascript code segment to disable it when the
page loads. I have reasons for not wanting to do this with server side
code...
document.all['ct100_ContentPlaceHolder1_btnContinue'].disabled = true;
Now, when I view this in IE, the button is disabled. But when I view it
in Firefox, it's not. Also, there are no javascript errors returned by
either browser. Also, I have already updated my browserCaps section in
web.config, if that is relevant.
Why does the button remain enabled when viewing the page with Firefox?
Joey,
This code works for me. Be sure to declare your DTD as XHTML 1.1
Transitional. You may find that helps because the way the disabled
attribute was handled has changed since the HTML 3.2 spec.
<script type="text/javascript">
<!--
function disableButton(buttonId) {
if (document.all) {
var btn = document.all[buttonId; btn.disabled = 'true';
}
else {
var btn = document.getElementById(buttonId); btn.disabled = 'true';
}
}
// -->
</script>
....
<!-- After button is defined -->
<script type="text/javascript">
disableButton('ct100_ContentPlaceHolder1_btnContin ue');
</script>
Brennan Stehling http://brennan.offwhite.net/blog/
Joey wrote:
Hello,
In my C# asp.net 2.0 application, I have a webform with a button server
control on it. The webform, like most others in the site, subscribes to
a master page. I have determined that the button always renders with an
id of "ct100_ContentPlaceHolder1_btnContinue" in both the IE and
Firefox browsers.
I created the following javascript code segment to disable it when the
page loads. I have reasons for not wanting to do this with server side
code...
document.all['ct100_ContentPlaceHolder1_btnContinue'].disabled = true;
Now, when I view this in IE, the button is disabled. But when I view it
in Firefox, it's not. Also, there are no javascript errors returned by
either browser. Also, I have already updated my browserCaps section in
web.config, if that is relevant.
Why does the button remain enabled when viewing the page with Firefox?
document.all is an IE only collection, it does not exist in the w3c
standard, so it works in ie only. use the w3c standard:
document.getElementById('ct100_ContentPlaceHolder1 _btnContinue').disabled =
true;
-- bruce (sqlwork.com)
"Joey" <jo*********@topscene.comwrote in message
news:11**********************@h48g2000cwc.googlegr oups.com...
Hello,
In my C# asp.net 2.0 application, I have a webform with a button server
control on it. The webform, like most others in the site, subscribes to
a master page. I have determined that the button always renders with an
id of "ct100_ContentPlaceHolder1_btnContinue" in both the IE and
Firefox browsers.
I created the following javascript code segment to disable it when the
page loads. I have reasons for not wanting to do this with server side
code...
document.all['ct100_ContentPlaceHolder1_btnContinue'].disabled = true;
Now, when I view this in IE, the button is disabled. But when I view it
in Firefox, it's not. Also, there are no javascript errors returned by
either browser. Also, I have already updated my browserCaps section in
web.config, if that is relevant.
Why does the button remain enabled when viewing the page with Firefox?
Can you provide a simple example as to how to query, in code behind,
for the correct id?
Cowboy (Gregory A. Beamer) wrote:
YOu need to actually query, in code behind, to determine what the postback
event is for the control and emit the JavaScript accordingly. I am not sure
this conquers all Firefox issues, but it guarantees a proper path down the
rabbit hole even if you rename the control for some reason. I do not have a
sample for this.
If you have to go absolutely generic, you can get the control that posted
from Request["EVENTTARGET"], but this does not work with all controls.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
*************************************************
Think outside of the box!
*************************************************
"Joey" <jo*********@topscene.comwrote in message
news:11**********************@h48g2000cwc.googlegr oups.com...
Hello,
In my C# asp.net 2.0 application, I have a webform with a button server
control on it. The webform, like most others in the site, subscribes to
a master page. I have determined that the button always renders with an
id of "ct100_ContentPlaceHolder1_btnContinue" in both the IE and
Firefox browsers.
I created the following javascript code segment to disable it when the
page loads. I have reasons for not wanting to do this with server side
code...
document.all['ct100_ContentPlaceHolder1_btnContinue'].disabled = true;
Now, when I view this in IE, the button is disabled. But when I view it
in Firefox, it's not. Also, there are no javascript errors returned by
either browser. Also, I have already updated my browserCaps section in
web.config, if that is relevant.
Why does the button remain enabled when viewing the page with Firefox?
Okay, I changed it to...
document.getElementById('ct100_ContentPlaceHolder1 _btnContinue').disabled=true
Now it still works fine in IE, and it still doesn't work in Firefox.
Any other ideas, anyone?
bruce barker (sqlwork.com) wrote:
document.all is an IE only collection, it does not exist in the w3c
standard, so it works in ie only. use the w3c standard:
document.getElementById('ct100_ContentPlaceHolder1 _btnContinue').disabled =
true;
-- bruce (sqlwork.com)
"Joey" <jo*********@topscene.comwrote in message
news:11**********************@h48g2000cwc.googlegr oups.com...
Hello,
In my C# asp.net 2.0 application, I have a webform with a button server
control on it. The webform, like most others in the site, subscribes to
a master page. I have determined that the button always renders with an
id of "ct100_ContentPlaceHolder1_btnContinue" in both the IE and
Firefox browsers.
I created the following javascript code segment to disable it when the
page loads. I have reasons for not wanting to do this with server side
code...
document.all['ct100_ContentPlaceHolder1_btnContinue'].disabled = true;
Now, when I view this in IE, the button is disabled. But when I view it
in Firefox, it's not. Also, there are no javascript errors returned by
either browser. Also, I have already updated my browserCaps section in
web.config, if that is relevant.
Why does the button remain enabled when viewing the page with Firefox?
Okay, nevermind. I cleared the cache in Firefox, and now it works.
Thanks a lot!
Joey wrote:
Okay, I changed it to...
document.getElementById('ct100_ContentPlaceHolder1 _btnContinue').disabled=true
Now it still works fine in IE, and it still doesn't work in Firefox.
Any other ideas, anyone?
bruce barker (sqlwork.com) wrote:
document.all is an IE only collection, it does not exist in the w3c
standard, so it works in ie only. use the w3c standard:
document.getElementById('ct100_ContentPlaceHolder1 _btnContinue').disabled =
true;
-- bruce (sqlwork.com)
"Joey" <jo*********@topscene.comwrote in message
news:11**********************@h48g2000cwc.googlegr oups.com...
Hello,
>
In my C# asp.net 2.0 application, I have a webform with a button server
control on it. The webform, like most others in the site, subscribes to
a master page. I have determined that the button always renders with an
id of "ct100_ContentPlaceHolder1_btnContinue" in both the IE and
Firefox browsers.
>
I created the following javascript code segment to disable it when the
page loads. I have reasons for not wanting to do this with server side
code...
>
document.all['ct100_ContentPlaceHolder1_btnContinue'].disabled = true;
>
Now, when I view this in IE, the button is disabled. But when I view it
in Firefox, it's not. Also, there are no javascript errors returned by
either browser. Also, I have already updated my browserCaps section in
web.config, if that is relevant.
>
Why does the button remain enabled when viewing the page with Firefox?
>
"Joey" <jo*********@topscene.comwrote in message
news:11**********************@h48g2000cwc.googlegr oups.com...
Okay, nevermind. I cleared the cache in Firefox, and now it works.
BTW, you could make your HTML more readable by giving your MasterPage(s) and
ContentPages meaningful IDs... E.g. in the code behind your MasterPage:
protected void Page_Init(object sender, EventArgs e)
{
this.ID = "MyMasterPage";
}
And then explicitly name every ContentPage in its HTML e.g.
<asp:Content ContentPlaceHolderID="MyContentPage" runat="server">
<asp:TextBox ID="MyTextBox" runat="server" />
</<asp:Content>
Then, client side, your control will ALWAYS be called
MyMasterPage_MyContentPage_MyTextBox- this makes your life massively easier
because it means you don't have to ask ASP.NET to tell you the controls'IDs,
as you already know them.
In this way, you can use client-side JavaScript to refer to your controls in
two ways:
document.aspnetForm.MyMasterPage_MyContentPage_MyT extBox
or
document.getElementById('MyMasterPage_MyContentPag e_MyTextBox')
Also, don't forget that no matter what ID you give the <formtag in your
MasterPage, ASP.NET will ALWAYS rename it to aspnetForm :-)
Forget that , use inline aspx code to pass the control's .ClientID property.
This is the most reliable.
"Mark Rae" <ma**@markNOSPAMrae.comschreef in bericht
news:e4**************@TK2MSFTNGP04.phx.gbl...
"Joey" <jo*********@topscene.comwrote in message
news:11**********************@h48g2000cwc.googlegr oups.com...
>Okay, nevermind. I cleared the cache in Firefox, and now it works.
BTW, you could make your HTML more readable by giving your MasterPage(s)
and ContentPages meaningful IDs... E.g. in the code behind your
MasterPage:
protected void Page_Init(object sender, EventArgs e)
{
this.ID = "MyMasterPage";
}
And then explicitly name every ContentPage in its HTML e.g.
<asp:Content ContentPlaceHolderID="MyContentPage" runat="server">
<asp:TextBox ID="MyTextBox" runat="server" />
</<asp:Content>
Then, client side, your control will ALWAYS be called
MyMasterPage_MyContentPage_MyTextBox- this makes your life massively
easier because it means you don't have to ask ASP.NET to tell you the
controls'IDs, as you already know them.
In this way, you can use client-side JavaScript to refer to your controls
in two ways:
document.aspnetForm.MyMasterPage_MyContentPage_MyT extBox
or
document.getElementById('MyMasterPage_MyContentPag e_MyTextBox')
Also, don't forget that no matter what ID you give the <formtag in your
MasterPage, ASP.NET will ALWAYS rename it to aspnetForm :-)
I agree. You never know what the hiearchy will be when your pages and
controls are used. Hard-coding the names in Javascript will ensure
they break sooner or later.
What I normally do is declare Javascript variables in a static .js file
with the major of the Javascript behavior. And then with the ASP.NET
controls, I insert script blocks which set those variables.
<script ...>
var buttonId;
functions...
</script>
<!-- later from the ASP.NET control -->
<script ...>
buttonId = 'Page_Button1';
</script>
Search for RegisterScriptBlock on MSDN.
Brennan Stehling http://brennan.offwhite.net/blog/
Edwin Knoppert wrote:
Forget that , use inline aspx code to pass the control's .ClientID property.
This is the most reliable.
"Mark Rae" <ma**@markNOSPAMrae.comschreef in bericht
news:e4**************@TK2MSFTNGP04.phx.gbl...
"Joey" <jo*********@topscene.comwrote in message
news:11**********************@h48g2000cwc.googlegr oups.com...
Okay, nevermind. I cleared the cache in Firefox, and now it works.
BTW, you could make your HTML more readable by giving your MasterPage(s)
and ContentPages meaningful IDs... E.g. in the code behind your
MasterPage:
protected void Page_Init(object sender, EventArgs e)
{
this.ID = "MyMasterPage";
}
And then explicitly name every ContentPage in its HTML e.g.
<asp:Content ContentPlaceHolderID="MyContentPage" runat="server">
<asp:TextBox ID="MyTextBox" runat="server" />
</<asp:Content>
Then, client side, your control will ALWAYS be called
MyMasterPage_MyContentPage_MyTextBox- this makes your life massively
easier because it means you don't have to ask ASP.NET to tell you the
controls'IDs, as you already know them.
In this way, you can use client-side JavaScript to refer to your controls
in two ways:
document.aspnetForm.MyMasterPage_MyContentPage_MyT extBox
or
document.getElementById('MyMasterPage_MyContentPag e_MyTextBox')
Also, don't forget that no matter what ID you give the <formtag in your
MasterPage, ASP.NET will ALWAYS rename it to aspnetForm :-)
I meant:
var o = document.getElementById('<%=txt_Index.ClientID%>') ;
o.value = ....
"Brennan Stehling" <of******@gmail.comschreef in bericht
news:11**********************@m7g2000cwm.googlegro ups.com...
>I agree. You never know what the hiearchy will be when your pages and
controls are used. Hard-coding the names in Javascript will ensure
they break sooner or later.
What I normally do is declare Javascript variables in a static .js file
with the major of the Javascript behavior. And then with the ASP.NET
controls, I insert script blocks which set those variables.
<script ...>
var buttonId;
functions...
</script>
<!-- later from the ASP.NET control -->
<script ...>
buttonId = 'Page_Button1';
</script>
Search for RegisterScriptBlock on MSDN.
Brennan Stehling
http://brennan.offwhite.net/blog/
Edwin Knoppert wrote:
>Forget that , use inline aspx code to pass the control's .ClientID
property.
This is the most reliable.
"Mark Rae" <ma**@markNOSPAMrae.comschreef in bericht
news:e4**************@TK2MSFTNGP04.phx.gbl...
"Joey" <jo*********@topscene.comwrote in message
news:11**********************@h48g2000cwc.googlegr oups.com...
Okay, nevermind. I cleared the cache in Firefox, and now it works.
BTW, you could make your HTML more readable by giving your
MasterPage(s)
and ContentPages meaningful IDs... E.g. in the code behind your
MasterPage:
protected void Page_Init(object sender, EventArgs e)
{
this.ID = "MyMasterPage";
}
And then explicitly name every ContentPage in its HTML e.g.
<asp:Content ContentPlaceHolderID="MyContentPage" runat="server">
<asp:TextBox ID="MyTextBox" runat="server" />
</<asp:Content>
Then, client side, your control will ALWAYS be called
MyMasterPage_MyContentPage_MyTextBox- this makes your life massively
easier because it means you don't have to ask ASP.NET to tell you the
controls'IDs, as you already know them.
In this way, you can use client-side JavaScript to refer to your
controls
in two ways:
document.aspnetForm.MyMasterPage_MyContentPage_MyT extBox
or
document.getElementById('MyMasterPage_MyContentPag e_MyTextBox')
Also, don't forget that no matter what ID you give the <formtag in
your
MasterPage, ASP.NET will ALWAYS rename it to aspnetForm :-)
"Edwin Knoppert" <ne**@hellobasic.comwrote in message
news:45**********************@text.nova.planet.nl. ..
var o = document.getElementById('<%=txt_Index.ClientID%>') ;
o.value = ....
Yes, I agree that is more robust... This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: nntp |
last post by:
I have a set of links which I want search engines to crawl them, but I want
to disable them from my visitors, so I will ask the link owners to pay me to
let me enable them.
<a disabled...
|
by: techfuzz |
last post by:
I scoured this group and others looking for the best way to disable a
button after the first click to prevent multiple submissions, but
never did find anything that worked like they said it would. ...
|
by: Sinity |
last post by:
Anyone knows the method/codes to disable the clicked button after first
click by using .aspx-- to prevent people to click many time when waiting for
the server response.
I tried to do this by...
|
by: Al Cohen |
last post by:
I'm using a LinkButton to call some code, then do a redirect. The code
does some queries, sends some emails, and takes a few moments before the
redirect is performed.
I'd like to disable my...
|
by: GD |
last post by:
Hi,
I wonder how to disable the "submit" behavior of a button. What I want is to
assign values to dynamically added user controls without page postback.
Problem: dynamically created control can...
|
by: Jeff |
last post by:
I have a payment form with a submit button. A large percentage of users
double-click the submit button thus submitting their payment information
twice. I would like to use javascript to disable...
|
by: Robert Ladd |
last post by:
Hi,
I'm trying to disable the asp.net calendar control from a javascript
function, but it doesn't disable the doPostBack.
To simplify the situation, assume a page with 4 controls. A...
|
by: blarfoc |
last post by:
Hi, I have to disable a button on a aspx page after the user clicks it.
I have to disable the button with javascript because the process takes
20 seconds to run the full course.
I kno I need to...
|
by: Patrick Flaherty |
last post by:
Hi,
Experienced programmer but new to PHP. Moreover I'm to use PHP with Xoops on
top (this adds object orientation?).
I don't seem to find a xoops Usenet group?
Whatever the case (and...
|
by: FAQ server |
last post by:
-----------------------------------------------------------------------
FAQ Topic - How do I disable the right mouse button?
-----------------------------------------------------------------------...
|
by: taylorcarr |
last post by:
A Canon printer is a smart device known for being advanced, efficient, and reliable. It is designed for home, office, and hybrid workspace use and can also be used for a variety of purposes. However,...
|
by: Charles Arthur |
last post by:
How do i turn on java script on a villaon, callus and itel keypad mobile phone
|
by: ryjfgjl |
last post by:
If we have dozens or hundreds of excel to import into the database, if we use the excel import function provided by database editors such as navicat, it will be extremely tedious and time-consuming...
|
by: emmanuelkatto |
last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud.
Please let me know.
Thanks!
Emmanuel
|
by: BarryA |
last post by:
What are the essential steps and strategies outlined in the Data Structures and Algorithms (DSA) roadmap for aspiring data scientists? How can individuals effectively utilize this roadmap to progress...
|
by: nemocccc |
last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
|
by: Sonnysonu |
last post by:
This is the data of csv file
1 2 3
1 2 3
1 2 3
1 2 3
2 3
2 3
3
the lengths should be different i have to store the data by column-wise with in the specific length.
suppose the i have to...
|
by: Hystou |
last post by:
There are some requirements for setting up RAID:
1. The motherboard and BIOS support RAID configuration.
2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...
|
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven...
| |
