Author Topic: Grid break with string of specific pattern  (Read 508 times)

ami dev

  • Pro Ultimate
  • Newbie
  • *
  • Posts: 18
    • View Profile
Grid break with string of specific pattern
« on: January 20, 2020, 06:52:37 am »
Hi.

If a character string of a specific pattern using tags is set as data, the grid will be broken.

Pattern: "<<x"
* x is any alphabet

Specifically, it occurs only when the alphabet continues after "less than" is repeated twice as shown below.

NG:
  <<x

OK:
  <
  <<
  <<x>
  <x>>
  x>>
  >>
  >
  <<=
  <<あ

Is there any workaround for this?
Thank you.

paramvir

  • Administrator
  • Hero Member
  • *****
  • Posts: 4418
    • View Profile
Re: Grid break with string of specific pattern
« Reply #1 on: January 20, 2020, 03:52:55 pm »
Ami

Thanks for reporting issue. Please add below code to fix it.

Code: [Select]
pq.escapeHtml = function( val){
return val.replace(/&/g, "&amp;").replace(/<([a-z,A-Z]+)/g, "&lt;$1")
}

ami dev

  • Pro Ultimate
  • Newbie
  • *
  • Posts: 18
    • View Profile
Re: Grid break with string of specific pattern
« Reply #2 on: January 21, 2020, 01:47:01 pm »
By applying the code presented, it was displayed correctly.
Many thanks.

By the way, will this fix be included in future releases?

paramvir

  • Administrator
  • Hero Member
  • *****
  • Posts: 4418
    • View Profile
Re: Grid break with string of specific pattern
« Reply #3 on: January 21, 2020, 01:50:10 pm »
yes it would be included in future releases.

ami dev

  • Pro Ultimate
  • Newbie
  • *
  • Posts: 18
    • View Profile
Re: Grid break with string of specific pattern
« Reply #4 on: January 21, 2020, 02:10:59 pm »
I'm relieved.
Thank you.

paramvir

  • Administrator
  • Hero Member
  • *****
  • Posts: 4418
    • View Profile
Re: Grid break with string of specific pattern
« Reply #5 on: January 29, 2020, 10:32:42 pm »
This is fixed in v7.1.0

ami dev

  • Pro Ultimate
  • Newbie
  • *
  • Posts: 18
    • View Profile
Re: Grid break with string of specific pattern
« Reply #6 on: January 30, 2020, 07:20:41 am »
We confirmed that it was fixed.
Many thanks.