Home/ Questions/Q 938313
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T21:37:23+00:00

Very strange issue… I have something like this in my Controller: public ActionResult Initialize(IEnumerable<MyModel>

  • 0

Very strange issue… I have something like this in my Controller:

public ActionResult Initialize(IEnumerable<MyModel> Requests)
{
...

}

I generate form elements in my submitting View that look like this:

Requests[90ed54f6-4650-44c7-8cc2-c4d225a9a334].Name
Requests[90ed54f6-4650-44c7-8cc2-c4d225a9a334].Address
Requests[db67e8e5-94f8-4b35-b69c-65184980f2a1].Name
Requests[db67e8e5-94f8-4b35-b69c-65184980f2a1].Address

On Firefox, when I submit this with multiple elements, the binder works and I get a collection of objects. On Safari, the exact same data always generates only 1 object in the collection.

Weirdly, in the debugger if I look at Requests.Params.AllKeys[] I see the values — they’re being submitted, just somehow not binding. I use Firebug on Firefox but don’t have an equivalent tool for Safari. Since I see the values in the Request.Params, I assume that it’s not an issue with the form values being passed in — just something about they way they’re being bound to the ViewModel…

The binder is kind of black magic to me — I’m not sure where this lives and if I can step through this to see what it’s doing.

Any ideas what this might be or how I might chase this down?

Edit: This works correctly in IE as well — just Safari is acting weird.

Edit 2: I lied… Safari does not post the index values as I would expect:

Requests.index = {GUID}
Requests[90ed54f6-4650-44c7-8cc2-c4d225a9a334].Name
Requests[90ed54f6-4650-44c7-8cc2-c4d225a9a334].Address
Requests.index = {GUID}
Requests[db67e8e5-94f8-4b35-b69c-65184980f2a1].Name
Requests[db67e8e5-94f8-4b35-b69c-65184980f2a1].Address

Both Firefox and Internet Explorer post both Requests.index values as comma separated values, but Safari only posts the first. I’m not sure what “correct” is for this case, but this is something I can sink my teeth into.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    So the final solution to this had to do with improperly placed <input> tags. Specifically, I was placing a hidden <input> after a <tr> and before a <td>. On Firefox and IE it’s very forgiving and this was working. On Safari for some reason, it would not consider the 2nd-Nth elements to be valid form inputs. Putting the <input> elements inside of the <td> worked for all browsers.

    Thanks for your help guys.

    • 0