Bug #556

Actions on elements in page >1 cause undefined objects

Added by Hector Sanjuan almost 10 years ago. Updated almost 10 years ago.

Status:ClosedStart date:04/01/2011
Priority:HighDue date:
Assignee:Hector Sanjuan% Done:

100%

Category:Sunstone
Target version:Release 3.0
Resolution:fixed Pull request:
Affected Versions:

Description

As pagination is reset, the position of the updated element cannot be found in the current page, causing an ungly javascript error.

Associated revisions

Revision cd7d6299
Added by Hector Sanjuan almost 10 years ago

Fixes bug #556: Updating elements on page >1 error

The element tr is now retrieved from the whole pool of elements in the
datatable, not just from the visible ones. Also, pagination is not resetted
anymore when updating a single element.

Revision 3805f538
Added by Abel Coronado about 3 years ago

F #5528: Standardized js (#556)

  • F #5528: Standardized js
  • F #5528: Applied standard in 2 random files
  • F #5528: Added no-trailing-spaces rule

History

#1 Updated by Hector Sanjuan almost 10 years ago

  • % Done changed from 0 to 100
  • Resolution set to fixed

#2 Updated by Hector Sanjuan almost 10 years ago

  • Status changed from New to Closed

Fix is now upstream

Also available in: Atom PDF