Note that there are some explanatory texts on larger screens.

plurals
  1. POEmpty space (or white space) shown in between cells in ajax fetched data fed to table in IE9 browser only,
    primarykey
    data
    text
    <p>As the title suggest, I have a table which is loaded from database. First only 15 rows are fetched. Later there is way to make it show 15 , 50 and 100 records to show using dropdown list. Which is fetched via ajax. Some how if I make the fetch record count more than 59 or above, empty space is created in between cell at random row. It happens only in IE9 browsers. IE Browsers version&lt; 9 are good, FireFox, Chrome, Safari are good as well. This is my first question so I'm not allowed to post image, so I'll put some numeric forms below. </p> <p>|..1..||..2..||...3...||....4....||.5.||..6..||..7..|</p> <p>Let's assume the above is a row,the bar acting as border right and left. What I get in IE9 ajax fetched data is something like below</p> <p>|..1..||..2..||...3...||....4....||.5.||..6..||..7..|</p> <p>|..1..|_ _ _|..2..||...3...||....4....||.5.||..6..||..7..|</p> <p>|..1..||..2..||...3...||....4....||.5.||..6..||..7..|</p> <p>|..1..||..2..||...3...|_ _ _ _|....4....||.5.||..6..||..7..|</p> <p>|..1..||..2..||...3...||....4....||.5.||..6..||..7..|</p> <p>You see the space (represented by _ 'underscore') in the 2nd ( after 1st column)and 4th (after 3rd column) row. I am not getting any idea, as the IE developer/debugger toolbar isn't helping much. The effect is not random as I get the same empty space between cell on refresh or after clear cache. Might it be due to ajax fetched data has something to do with IE9 rendering it? Did anyone face any such problem or a close one. Any help would be appreciated. </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload