Fixed Header with select list in header
Fixed Header with select list in header
morph
Posts: 1Questions: 0Answers: 0
OK, so I have narrowed my issue down to the Fixed Header. I have been using the dataTables control for a while now and have found it to be superb for my sites - I've got it to do just about everything I have needed but this has me stumped! I have stripped everything back to the simplest terms for testing and you can see that version here:
http://www.the-morph.co.uk/test/TrainingComps2.aspx
- It loads with the Fixed Header OFF.
- Make a selection from the drop down in the header.
- Make a selection from the drop down in row 1.
- Click 'Check Selections' and see what you have chosen - all is correct.
- Now click the checkbox to turn ON the Fixed Header.
- Make a selection from the drop down in the header.
- Make a selection from the drop down in row 1.
- Click 'Check Selections' and see what you have chosen
- The selection from Row 1 is always correct but the header selection is ALWAYS 1 instead of what you chose - huh?!
- Turn OFF the Fixed Header and all works as expected.
Any ideas would be really helpful, thank you.
http://www.the-morph.co.uk/test/TrainingComps2.aspx
- It loads with the Fixed Header OFF.
- Make a selection from the drop down in the header.
- Make a selection from the drop down in row 1.
- Click 'Check Selections' and see what you have chosen - all is correct.
- Now click the checkbox to turn ON the Fixed Header.
- Make a selection from the drop down in the header.
- Make a selection from the drop down in row 1.
- Click 'Check Selections' and see what you have chosen
- The selection from Row 1 is always correct but the header selection is ALWAYS 1 instead of what you chose - huh?!
- Turn OFF the Fixed Header and all works as expected.
Any ideas would be really helpful, thank you.
This discussion has been closed.
Replies
document.body.appendChild(nDiv);
to
document.forms[0].appendChild(nDiv);
That allows my button events to fire just fine, but you will run into issues if you try to use control values because you will now have multiple controls with the same ID. In that case, ASP.NET concatenates control values with a comma separator (for string values like TextBox.Text - not sure about all other properties).
Sorry I can't provide a solution, but hope this information helps. Good luck!