Closed GoogleCodeExporter closed 8 years ago
I found that it works if I do an id-based call for each table, e.g.
$('#foo1').dataTable().makeEditable({
sUpdateURL: function(value, settings)
{
alert(value + $(this).attr('id') );
return value;
},
});
$('#foo2').dataTable().makeEditable({
sUpdateURL: function(value, settings)
{
alert(value + $(this).attr('id') );
return value;
},
});
This is without adding any buttons or adding the button-related config to the
initialisation. So... not sure why the class selector wouldn't work the same
way.
Original comment by brianna.laugher
on 26 Jul 2011 at 3:34
I will investigate this. However if you are using same initialization on
different tables then you are using identical UpdateData server page for
updating values in differen tables. Why you need this as you have identical
data managed with the sme function but in the different table.
This is not related to the issue you have reported - it just looks strange to
me.
Original comment by joc...@gmail.com
on 20 Aug 2011 at 8:41
Well, I could make them the same table actually, but I had them as separate
tables to insert a heading and break up the layout a bit. I am using an id on
the cell to identify my data rather than row/column info.
Original comment by brianna.laugher
on 21 Aug 2011 at 5:59
Hi,
Please use different ids instead of classes. I have tried this and there are
few other issues that happens when I fix this.
For now this will be know bug because there are easy workaround (using
different ids as an example).
Jovan
Original comment by joc...@gmail.com
on 29 Sep 2011 at 6:10
Original issue reported on code.google.com by
brianna.laugher
on 25 Jul 2011 at 7:36Attachments: