v1.7.6 IE9 default pagination button issue

v1.7.6 IE9 default pagination button issue

bettenkbettenk Posts: 2Questions: 0Answers: 0
edited October 2013 in General
Hello. I just started supporting a webapp using dataTables v1.7.6 and on IE9, the default pagination back buttons "<" and "<<" are displaying incorrectly. I'm new to dataTables; what I have been told about how dataTables were used in this webapp is that all defaults were used.

The issue in IE9 is that "<" is showing in place of "<<" and there is no "button" where "<<" should be, just a blank placeholder that is clickable - clicking on the incorrect "<" button has the correct action for where the button is (back to page 1) and clicking where missing "<" should be goes back one page. The pagination numbers and forward buttons ">" and ">>" are correct and functional.

Here is a snippet of the rendered HTML:
[code]
Showing 1 to 25 of 481 records

<


1
2
3

>
>>

[/code]

Thank you in advance for any assistance with this...

Replies

  • allanallan Posts: 63,498Questions: 1Answers: 10,471 Site admin
    1.7.6 is very out of date now. I'd suggest firstly upgrading to the latest release and then linking to a test case showing the issue please.

    Allan
  • bettenkbettenk Posts: 2Questions: 0Answers: 0
    FIXED: in jquery.dataTables.js (v1.7.6) file, the default pagination back characters '<' and '<<' needed to be encoded so IE9 would render both properly:

    [code]
    this.oLanguage = {
    "sProcessing": "Processing...",
    "sLengthMenu": "Show _MENU_ records",
    "sZeroRecords": "No matching records found",
    "sEmptyTable": "No data available in table",
    "sInfo": "Showing _START_ to _END_ of _TOTAL_ records",
    "sInfoEmpty": "Showing 0 to 0 of 0 records",
    "sInfoFiltered": "(filtered from _MAX_ total records)",
    "sInfoPostFix": "",
    "sSearch": "Search:",
    "sUrl": "",
    "oPaginate": {
    "sFirst": "<<",
    "sPrevious": "<",
    "sNext": ">",
    "sLast": ">>"
    },
    "fnInfoCallback": null
    };
    [/code]

    This can be closed.
This discussion has been closed.