Another issue I found was the use of the Value attribute on Submit buttons. This is handy because you can change the Value attribute depending on the action and then pick up the button with its Name attribute in a controller method.
Enter the ipad safari browser. Apparently this browser does not pickup the value attribute value and put it in the request variables. It just comes to the controller method as empty.
The solution was to create a hidden input field and set it. Then pick it up as a parameter to the controller method. Works like a charm.
I have been working for months on converting an ASP classic app to MVC 3. This new version needs to run on FF and Ipad Safari.
one of the things we found was the user of just the Name attribute for controls such as input and so forth. This works fine in IE and some other browsers. But Safari chokes on this. The solution is to make the Name and the ID the same and then all the browsers are happy.
When you download the samples for this sdk, they are going to be read only as they are coming from the web. Windows 7 is pretty smart about this and automatically marks them read only, then VS 2010 picks that up and warns you
Then when you try to run the sample, if the sample tries to read the config files it will most likely throw an exception.
The solution I found was to use Windows Explorer and mark all sample folders as read write. Make sure VS is closed when you do this.
Then open VS and boom, it should work.
The SDK is here