• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 406
  • Last Modified:

ASP.Net clientId render incorrectly.

On some PCs (not all) my the clientIds in a repeater control get out of whack. This problem is specific to IE11 but I don't see the issue on most IE 11 PCs. I have a PC in my development environment that has the problem, I have another one that does not. Both these PCs are running Win 7 64 bit and the IE setup is identical. I've tried several variations of the page directive "ClientIDMode" but it doesn't seem to correct my issue.
I've also tried some meta tags to force it to render in a specific IE version but that had no affect. See attachment for more details

 Thanks in advance






Server is: IIS7 .net 4.5
Website is: C# vs 2012
example.docx
bad.txt
bad.txt
0
Bob Hoffman
Asked:
Bob Hoffman
  • 4
  • 3
1 Solution
 
SriVaddadiCommented:
Specify client id mode to "Predictable"

example:

<asp :TextBox ID ="txt" runat ="server" ClientIDMode ="Predictable" />

You can find more info here
0
 
Bob HoffmanDeveloperAuthor Commented:
This is that same as doing it globally in a page directive.... had no affect. Thanks
0
 
SriVaddadiCommented:
The default value of ClientIDMode for a page is Predictable. The default value of ClientIDMode for a control is Inherit.

However, if you use Visual Studio to convert a Web project to ASP.NET 4 from an earlier version, Visual Studio automatically sets the site default to AutoID in the Web.config file.
0
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
Bob HoffmanDeveloperAuthor Commented:
The solution started out as ASP.Net 4, there is no AutoId in the web.config, only the page directive. I tried all the various ClientIDModes at the page directive level, I could see in the Ids in markup were changed as expected, but on my one dev box it was still messing up?  I pretty sure that it has something to do with the client not the site itself, I just can't isolate the issue. Thanks
0
 
Bob HoffmanDeveloperAuthor Commented:
Solution was to move the no-cache meta tags to the bottom of the page and to turn off IIS7 Static HTTP compression and  turn on dynamic HTTP Compression. Never figured out why the problem was NOT on all IE 11 PCs?

This link explain why move the no-cache meta tags to the bottom makes a difference:

http://www.htmlgoodies.com/beyond/reference/article.php/3472881
0
 
SriVaddadiCommented:
Thanks for shaing the solution. Greatly appreciate it
0
 
Bob HoffmanDeveloperAuthor Commented:
Found the solution on my own.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now