I have a very simple ASP.NET 3.5 SP1 application, which has a postback trigger onchange for a checkbox (autopostback=true). For some reason, in all versions of IE when I click that checkbox the broswer crashes.
<asp:CheckBox ID="ckTrouble" runat="server" Text="Check this box" TextAlign="Left" AutoPostBack="True" />
The checkbox is in a user control, which sits on a normal old page, which uses a traditional masterpage. This works fine in Firefox and Chrome, only IE is causing the grief.
Thoughts?
It seems that this may have been a result of SmartNavigation="True". Anyone ever see this as a cause? See this.
Related
Below is the code for the same where I have set the default and selected style for the tab:
<cc1:AdvancedTabStrip id="subTs" AutoPostBack="True" runat="server"
TabDefaultStyle="background-color:#ffffff;font-family:arial;font-weight:bold;font-size:8pt;color:#000000;width:110;height:21;text-align:center;text-decoration:underline;border-color:#efefef;border-style:solid;border-width:1px;"
TabSelectedStyle="background-color:#ffffff;color:#000000;text-decoration:none;" >
<cc1:AdvancedTabItem ID="tabGeneral" Text="General" ControlToShow="pnlGeneral"></cc1:AdvancedTabItem>
<cc1:AdvancedTabItem ID="tabOpenPeriods" Text="Open Periods" ControlToShow="pnlOpenPeriods"></cc1:AdvancedTabItem>
<cc1:AdvancedTabItem ID="tabAdvanced" Text="Advanced" ControlToShow="pnlAdvanced"></cc1:AdvancedTabItem>
</cc1:AdvancedTabStrip>
The above code for styling works perfect in other browsers except IE-11
Can anyone please provide solution for the same asap as our customer are chasing for this very badly.
In IE11 there seems to be an issue where on the click it does nothing at all. I know for a regular button all you have to do is add the name property. Is it the same for a linkbutton in ie?
I have many of these across my site that will not work correctly now.
<asp:LinkButton ID="Submit" runat="server" CssClass="Contact" OnClick="Submit_Click"></asp:LinkButton>
I'm using the .NET framework 4.0 and the corresponding version of the Ajax control toolkit.
On my page I have a combobox defined like this:
<asp:ComboBox ID="cbUserName" AutoCompleteMode="SuggestAppend"
CaseSensitive="false" runat="server" BackColor="#FFFFCC">
</asp:ComboBox>
In IE9 the combobox allows me to either type in it or select from the list of users. In FireFox, however, it's not letting me type in the box. The dropdownlist also doesn't filter when I'm typing in FireFox either. I'm wondering if anyone else has seen this behavior, and if there's a work-around?
EDIT
For what it's worth, the demo on the ASP.NET Ajax Control Toolkit site actually works fine in FireFox.
I was also getting the problem of not being able to enter text into a Combobox in FireFox, but I could in IE and Chrome. After a day of looking into the problem I found that setting the MaxLength property to something greater than 0 allowed FireFox to accept entry in the text field for the combobox.
I hope this helps someone having the same problem.
ddlBox.SelectedIndex = 0
Until the latest iteration of Ajax control toolkit, I didn't need to set that. But then I updated, and I couldn't type into the empty text box, which used to be displayed with the first item. So I added that code and it works fine again.
The similar issue has been reported here, make sure you used the same version of firefox and toolkit. If not try to upgrade them and again try.
<ajaxToolkit:ComboBox ID="ComboBox1" runat="server" DropDownStyle="DropDownList" AutoCompleteMode="SuggestAppend" CssClass="" AppendDataBoundItems="false">
<asp:ListItem>Fox</asp:ListItem>
</ajaxToolkit:ComboBox>
This worked for me in firefox.
Im not sure if you mistaking the ability to type but a combobox will only allow you to type out the ListItems. so in this case it will only allow you to type out Fox..
I experienced the same problem. I couldn't find an elegant solution online so I built my own AjaxControlToolkit.dll from two different sets of the toolkit source code.
I used everything from the latest release except for I replaced ComboBox.cs and ComboBox.pre.js with their versions from AjaxControlToolkit_8502f32ba9ce. (~July 2011)
Try using:
ajaxToolkit:ComboBox ID="ComboBox1" runat="server" DropDownStyle="DropDownList"
AutoCompleteMode="SuggestAppend" CssClass="" AppendDataBoundItems="false"
MaxLength="100"
I have a problem with FireFox and ASP.NET UpdatePanel.
I have in a form a checkbox and an UpdatePanel. When I check the checkbox, an asp:panel which is into the UpdatePanel should become visible.
<asp:CheckBox ID="cbMoreOptions" runat="server" Text="plus d'options" AutoPostBack="True" OnCheckedChanged="cbOptions_CheckedChanged" />
<asp:UpdatePanel ID="UpdatePanel1" runat="server">
<ContentTemplate>
<asp:Panel ID="Panel1" runat="server" Visible="false">
sssssssss
</asp:Panel>
</ContentTemplate>
<Triggers>
<asp:AsyncPostBackTrigger ControlID="cbMoreOptions" EventName="CheckedChanged" />
</Triggers>
</asp:UpdatePanel>
Everything is working fine but not after I refresh the page while the checkbox is checked. If this is happening, the checkbox rest checked the page doesn’t make postback more to the server. The firebug shows that the page gets a response and when I verify the its content I have en error 500 which tell that the information of the page is corrupt. All this is happening only in Firefox. In IE8 and Google Chrome everything is ok.
Does anybody have an idea how can I avoid this? It’s a bug of Firefox?
All the weird comportment continues until I make enter into the URL textbox. Even if I make F5 nothing happens. What is the difference between F5 and enter into the URL? They shouldn’t have the same result?
Thanks a lot.
Have you tried placing the checkbox "cbMoreOptions" inside the UpdatePanel?
Place in inside the UpdatePanel ContentTemplate section and set an AsyncPostBackTrigger for the CheckBox.
We had this problem a long time ago and it was the way firefox uses in-memory cache to store the state of a page which messes up the way ASP.NET handles VIEWSTATE hidden field. Check if caching turned on for your aspx pages and disable it.
Edit: Here's a link that explains it in detail.
What is the difference between F5 and enter into the URL? They
shouldn’t have the same result?
If you hit enter in the address bar, it does a GET request, i.e. you enter your page's lifecycle with !IsPostBack.
When you hit F5, I observed that firefox will repeat the last request, so if that last request was a POST, it will repeat it. That's why your page stay in a buggy state. If the first post back caused an error (the checkbox' checkedChanged), hitting F5 will just repeat that error.
So, no, the don't have the same result.
I don't have any documentation to backup this statement, but this is what I observed. If anyone can point a source I'll be glad to see it.
I have a gridview that is within an updatepanel for a modal popup I have on a page.
The issue is that the entire page refreshes every time I click an imagebutton that is within my gridview. This causes my entire page to load and since I have grayed out the rest of the page so that the user cannot click on it this is very annoying.
Does any one know what I am missing.
Edit: I entered a better solution at the bottom
Make sure you have the following set on the UpdatePanel:
ChildrenAsTriggers=false and UpdateMode=Conditional
do you have ChildrenAsTriggers="false" on the UpdatePanel?
Are there any javascript errors on the page?
I had this problem and came across the following article:
http://bloggingabout.net/blogs/rick/archive/2008/04/02/linkbutton-inside-updatepanel-results-in-full-postback-updatepanel-not-triggered.aspx
My button wasn't dynamically created in the code like in this example, but when I checked the code in the aspx sure enough it was missing an ID property. On adding the ID the postback became asynchronous and started to behave as expected.
So, in summary, check your button has an ID!
Are you testing in Firefox or IE? We have a similar issue where the entire page refreshes in Firefox (but not IE). To get around it we use a hidden asp:button with the useSubmitBehavior="false" set.
<asp:Button ID="btnRefresh" runat="server" OnClick="btnRefresh_Click" Style="display: none" UseSubmitBehavior="false" />
Several months later this problem was fixed. The project I was working in was a previous v1.1 which was converted with 2.0. However, in the web.config this line remained:
<xhtmlConformance mode="Legacy"/>
When it was commented out all of the bugs that we seemed to have with the ajax control toolkit disappeared
Is the Modal Window popped up using the IE Modal window? Or is it a DIV that you are showing?
If it is an IE Modal Pop up you need to ensure you have
<base target="_self" />
To make sure the post back are to the modal page.
If it is a DIV make sure you have your XHTML correct or it might not know what to update.
I would leave the onClick and set it as the trigger for the updatePanel.
That's odd that it works in FF and not IE. That is opposite from the behavior we experience.
UpdatePanels can be sensitive to malformed HTML. Do a View Source from your browser and run it through something like the W3C validator to look for anything weird (unclosed div or table being the usual suspects)
If you use Firefox, there's a HTML validator Extension/AddOn available that works quite nicely.
For reference..
I've also noticed, when using the dreaded <asp:UpdatePanel ... /> and <asp:LinkButton ... />, that as well as UpdateMode="Conditional" on the UpdatePanel the following other changes are required:
ViewStateMode="Enabled" is required on <asp:Content ... /> (I've set it to Disabled in the MasterPage)
ClientIDMode="Static" had to be removed from <%# Page ... />
To prevent post-backs add return false to the onclick event.
button.attribute.add("onclick","return false;");
Sample:
string PopupURL = Common.GetAppPopupPath() + "Popups/StockChart.aspx?s=" + symbol;
hlLargeChart.Attributes.Add("onclick", String.Format("ShowPopupStdControls(PCStockChartWindow,'{0}');return false;", PopupURL));