web/data/cubicweb.tablesorter.css
author Adrien Di Mascio <Adrien.DiMascio@logilab.fr>
Tue, 05 Jan 2010 22:11:37 +0100
branchstable
changeset 4210 9d9be21640ac
parent 1077 fe26a0cda180
child 5819 1017163825c7
permissions -rw-r--r--
[forms] fix multiple edit bug introduced by changeset cebdf8ee5ad7 Changeset cebdf8ee5ad7 assumed that edited entity was either explicitly passed to the form or found in first row / first col of the resultset because of the one_line_rset() selector. But one_line_rset() is actually trickier : the selector returns 1 if the resultset has more than one row **if** an explicit row is specified during selection process. This is exactly what is done in the 'muledit' form : for row in xrange(len(self.rset)): form = self.vreg['forms'].select('edition', self.req, rset=self.rset, row=row, #... This changeset thus takes row in consideration to find edited entity if 'row' was explcitly specified.

/* tables */
/*table.tablesorter {
	font-family:arial;
	background-color: #CDCDCD;
	margin:10px 0pt 15px;
	font-size: 8pt;
	width: 100%;
	text-align: left;
} */

table.listing tr .headerSortUp {
  background-image: url(asc.gif);
}
table.listing tr .headerSortDown {
  background-image: url(desc.gif);
}
table.listing tr .headerSortDown, table.listing tr .headerSortUp {
   background-color: #DDD;
   background-repeat: no-repeat;
   background-position: center right;
}