[kapalkatParticipant]

Someone has just closed the ticket connected to this issue but I have added a comment with information why this should be still open and corrected:
https://github.com/jqwidgets/jQWidgets/issues/309

[kapalkatParticipant]

Hey @hristo
I have applied the workaround and it occurred, it’s generating wrong date in Firefox.
Please check this out in Firefox:
https://jsfiddle.net/kapalkat/vmcgfL18/3/
TEST1 end_date is: ‘9/2/2020, 10:50:00.0 AM’
and when I apply:

beforeprocessing: function (records) {
  if (navigator.userAgent.toLowerCase().indexOf('firefox') !== -1){
    records.forEach(function (record) {
      if (record.end_time) {
        record.end_time = record.end_time.replace(',', '');
      }
    })
  }
  return records;
},

I get ‘Sun Feb 09 2020 10:50:00 GMT+0100 (Central European Standard Time)’ instead ‘Wed Sep 02 2020 10:50:00 GMT+0200 (Central European Summer Time)’ (Chrome)
We haven’t noticed that as we were using ‘9/9/3000, 12:00:00.0 AM’ for previous test (date and month are the same here).

I have no idea what’s inside your lib as it’s minimized and thus really hard to read! Could you please help me here to get the correct dates in Firefox?

[kapalkatParticipant]

Hey Hristo

I assume that all date related records are affected in Firefox…? Why would only (‘September 9, 3000’) be broken?:)
So I would need to look for every ‘date’ record beforeprocerssing.
This is not a very good idea as date record is a string here…so I would need to search it for date ‘looking’ data.
Sounds ugly to me:)
Is there any way to pin this topic to some official jQWidgets bug that I could track it?

BR
TK

[kapalkatParticipant]

Hey Hristo

Thanks for your feedback. Indeed it is working fine. However the fiddle was just an example. In production the data is coming from build in function ‘toLocaleString()’:

var defaultDate = new Date(value);
var locale = defaultDate.toLocaleString();

So I would need to parse it and remove the comma.
What do you think; how long it can take to have this resolved on your side?

BR
Tomasz Kapalka

[kapalkatParticipant]

OK I have prepared fiddle snippet to show the problem:
https://jsfiddle.net/kapalkat/txueL17h/8/

Please open it first in Chrome and you will see correct date generated for end_time and later please open this in Firefox and you will see wrong date generated for the end_time field (current time is generated).

[kapalkatParticipant]

Hey jQWidgets team,

We experience the very same issue. Everywhere your grid components isused we are vulnerable to XSS attacks…!
Is there any update on this? Every major UI framework/lib (Vue, Angular, React) has built in XSS prevention data sanitizing.
If still no fix exists, please let me know how I can prevent this globally?
We use your lib in multiple project, hundreds of grid components are already there. I need some global fix. Changing each grid individually would is rather impossible…

[kapalkatParticipant]

@hristo

Yes the workaround works fine. Thanks!
In the meantime I have already created my own workaround which was using event delegation. Attaching it in case someone would like to take a look on it as well.

$('#contenttabletreegrid').click(function(event) {
    var rowIndicator = $(event.target).parents('tr').attr('data-key');

    if (rowIndicator) {
        var row = $("#treegrid").jqxTreeGrid('getRow', rowIndicator);
        var isRowExpanded = row.expanded;

        // Fire expand/collapse event
        if (isRowExpanded === true) {
          $("#treegrid").jqxTreeGrid('collapseRow', row.uid);
        } else {
          $("#treegrid").jqxTreeGrid('expandRow', row.uid);
        }
    }
});

BR
Tomasz

[kapalkatParticipant]

@jqwidgets based on your jsfiddle collapseRow example I have created new one which shows the problem:
http://jsfiddle.net/kapalkat/53cs9j8q/5/

[kapalkatParticipant]

[Author]

Posts