(Edited the question's focus due to some more investigation)
I have a simple page with a gridview inside an update panel. When I click the column header to sort, the postback fires and the sorting works, but a blank space appears at the top of the page, pushing everything down.
If I remove the UpdatePanel, things work fine and no blank space appears.
It doesn't happen in Firefox/Chrome, I only see the issue in IE 7 (or IE8/9 when Compatibility Mode is set to IE7 Standards).
So I'm wondering how to get around this, since users could still be using IE7 or have Compatibility mode on (quite a large and diverse user base on this system.) in a newer version of IE.
All I can see is that, on the async postback, this is added to the top of the form (first element in asp.net main form):
<DIV>
<INPUT id="ctl00_ScriptManager1_HiddenField" type="hidden" name="ctl00_ScriptManager1_HiddenField" value="" />
</DIV>
(IE tool is capitalizing)
I tried styling that input field but it didn't make a difference.
It's not a huge deal, but, if the UpdatePanel doesn't work properly, it makes me wonder what else will break in Compat Mode.
Thanks
This is old but to all who are interested... Set the rendering mode of the update panel to inline. This can happen when you have empty update panels.
Related
In Visual Studio 2010 if I click on any <div> or <span> anywhere in the design view it selects this one grid always. Has anyone ever seen this? Are there any ways to fix this?
The only controls in design view that I can click on are textboxes / dropdowns / buttons / linkbuttons etc. So when I want to quickly jump to a span to edit its contents I have to click on the nearest one of those controls then make my way over to the <span>. Cause if I click on the <span>, BOOM highlight the gridview. It is driving me insane!
UPDATE
when i exceed 17 columns in the gridview this is happening. anything less than 17 does not cause this issue. i'd say this is a bug, and after a certain amount of columns the gridview does not function properly in design view and throws off other elements in the page.
This is what I have done do "work around" this problem.
It is a design view problem, not code.
Any time you have a grid view that has enough fields to push if off to the right of the visible editing area in design view, this bug will occur. Clicking spans and divs will always highlight that grid, it is so annoying.
You can expand your design view window wide enough to see the entire grid and this problem goes away for the time being. it is extremely annoying but works.
i am sure there are other work arounds but i have not seen anyone else have this problem (most people dont use the design view).
In my asp.net webform page I have a simple form with a single inputfield and a submit button. When initiating the post request and then hover over the submit button, the browser stops showing the loading state (progress bar dissapears, the "Done" label appears and the loading animation in the tab becomes the site icon again.
I have been able to narrow the bug down to the followihg css rule:
.button:hover {
background-image:url("/content/images/buttonHoverGradient.jpg");
}
on the following html
<input type="submit" class="button" title="Select a provider" value="Select">
It seems to me IE initiates the request to fetch the image and then takes the status of this new request as the overal status. I don't have a clue how to prove this. Any ideas?
UPDATE
The buttons class is used all over the page and we cannot know the dimensions of them on beforehand. Therefore using a single background as suggested by #teresko image with several states embedded is not an option.
UPDATE
It seems to be in other versions of IE too. Some research seems to point to the Doctype (which is currently quircks as asp.net webforms 3.5 doesn't really alow for strict)
Did you try to just use a same image for both normal and :hover state of the button , and only change the position of image on mouseover? Kinda like in this example.
This should solve at least part of the problem.
I have a display problem when I try to use a ajax combobox inside a tab control:
when my tab control loads on the page where the combobox is, everything works fine; however, if it loads on a another page, the you change to the page which contains the combobox, the right button (which opens the list of the combobox) isn't displayed at all.
Has someone been through this behavior? And maybe found a solution ?
Thanks in advance !
Use Firebug in FireFox (this tool is very good if you dont use it) and right-click the area where your drop arrow should be, then select "Inspect Element". At the bottom of your browser screen, you will see a couple windows. One window will detail teh styles being applied to the arrow area.
Look for a style that is making visibility of either a <td> or <img> to be hidden. The Ajax ComboBox control, sadly, is laid out in a table.
I've run into a strange problem with an HTML form. I've built a dynamic table that adds a new row when you enter data into an existing blank row; because there are some server requirements in adding a row, I make an AJAX call to do this in the onblur event. It took a while to make this work for all browsers, but eventually all was happy with the world ... until IE8. Now, what happens is that, when the call returns from AJAX, the cursor shows in the next textbox (correctly), but the keyboard no longer works. I have to close the modal window (actually an IFRAME), then the keyboard starts to work again. If I put IE8 into compatibility mode, it works fine.
Has anybody seen behavior like this, or have any ideas for a workaround?
Thanks, Jim
I had problems with DIVs placed above an INPUT, that cloacked the cursor... and once the DIV was not above it, the cursor appeared back again.
Just an idea: Maybe your IFRAME captured the focus (and/or the keyboard).
I'm having an unexpected "annoying" popup in IE7 (and possibly other versions). As expected IE prompts you about unsaved form data when closing the window which is fine. But I have a form inside a div and now when I toggle the display CSS style between none and block, IE thinks I'm closing the form with unsaved data and shows the warning about closing an unsaved form! I don't want my users to be annoyed when simply hiding a form in my IE-based web app.
Anyone know how to overcome this?
Make sure that your doc type is transitional rather than strict
The prompt isn't IE's-- your HTML has an onbeforeunload handler which triggers the warning.