homena / jmesa

Automatically exported from code.google.com/p/jmesa
0 stars 0 forks source link

Dynamic filter hangs #320

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Implements a DroplistFilterEditor on certain column
2. Load the table
3. Select one of the value of DroplistFilterEditor enabled column

What is the expected output? What do you see instead?
Expected : Correctly filtered new table, with enabled dynamic filter
Observed : Correctly filtered new table, with disabled dynamic filter

What version of the product are you using? On what operating system?
Jmesa   : 3.0.4
Server  : Websphere portal
Browser : Firefox, Google chrome

Please provide any additional information below.
- Same observation found after clicking the 'clear filter' function
- Table is supporting PortletTableModel and TableModel

Original issue reported on code.google.com by Inventor...@gmail.com on 30 May 2011 at 9:08

GoogleCodeExporter commented 9 years ago
Did you figure out your problem yet? 

Original comment by jeff.johnston.mn@gmail.com on 7 Jun 2011 at 3:42

GoogleCodeExporter commented 9 years ago
Nope I did not :( 

Any hints or can we have this case assigned and worked on? :)

Original comment by Inventor...@gmail.com on 8 Jun 2011 at 1:01

GoogleCodeExporter commented 9 years ago
I think this is very close to issue 256.

http://code.google.com/p/jmesa/issues/detail?id=256

I am not able to reproduce this. You are going to have to debug this locally. 
There is not much to it though. The place to look is in the jquery.jmesa.js 
file at the createDroplistDynFilter() method.

Original comment by jeff.johnston.mn@gmail.com on 9 Jun 2011 at 3:03

GoogleCodeExporter commented 9 years ago
I had almost the same issue when i used dynFilters.
My jmesa table updates every 10 seconds by making an ajax request, so if the 
filter is used when the request is sent, then the table updates but the filter 
cannot be accessed anymore (you cannot click on the filter to access the 
filter's input field).

After a short debugging i realized that the problem is from the 
createDynFilter() method, the dynFilter is not set to null if it is opened 
while the request is sent.

So i needed to check if the filter is visible before returning the created 
dynFilter, or else create a new one.

Line 456:
if (dynFilter) {
   // return only if dynFilter is visible
   // In my case i had just one filter so i checked:
   // document.getElementsByClassName("dynFilter")[0].style.overflow == "visible"
   return;
}

Original comment by tothsanyi.mail@gmail.com on 17 Nov 2011 at 10:30