-
Notifications
You must be signed in to change notification settings - Fork 284
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Range Slider - External Container creating extra Div's #68
Comments
taking me a while , and still its no the final fix, but I'm getting there... |
Fixed in 0.8.3.beta.6 |
thanks. that worked. Noticed one more small thing not related to the range slider issue, but related to ajax. I'll open a new issue. |
With this fix if filter_container_id is not defined then the whole column header gets emptied, as can be seen in the second table on this page Perhaps this line should do something like this instead?
|
@stt , thanks for pointing me to this issue with empty header , I actually noticed this several days ago , and haven't had the time to look at this, anyhow, I refactored that function now and fixed this issue. will be released in 0.8.5.beta.2 |
Note: This issue only happens under the following conditions:
If I put a range slider filter in an external container and move the slider, then it is creating extra Div's that are empty. I noticed this originally because of some CSS rules I had, the extra Div's were actually causing the page to grow in height. I took the CSS rules out, but the DIV's are still created, but not shown and the page does not grow in height.
From tracking what is going on in the source code, it appears that what is going on is that every time the the table draws, the
code at line 1946 is appending a new Div.
Here is a look at the HTML that get's created for the container:
Notice the last 8 lines. Every point that slider moves, one of these Div's is created.
FWIW, here's how I'm setting things up:
Also, FWIW, here's my Ajax call in the table setup. I don't think it matters that I'm calling localstorage, as this will also happen if I make an Ajax call to a .txt file like in your 1.10 load from Ajax example.
The text was updated successfully, but these errors were encountered: