Gelmiş geçmiş en büyük porno sitemiz olan 2pe de her zaman en kaliteli pornoları sunmayı hedefledik. Diğer video sitemiz olan vuam da ise hd porno ağırlıklı çalışmalara başladık.

    You found a bug! We've classified it as EXTGWT-3361 . We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.
  1. #1
    Sencha Premium Member
    Join Date
    Aug 2013
    Posts
    7
    Vote Rating
    0
    zoec is on a distinguished road

      0  

    Default HTML encoding occurring twice on

    HTML encoding occurring twice on


    Hi,

    We've upgraded to GXT 2.3.0 and have a problem with some Field<D> validation messages that get shown. Specifically message strings that contain characters that will be HTML encoded (e.g. & > <). Looking at the markInvalid method I can see that the string is first encoded when it arrives in the method. Then, we're using the default option of showing the error icon when validation fails, and when the error icon's setTooltip method is called, it is passed the encoded string, which then gets encoded a second time, because it uses setText which was a change in 2.3.0.

    For example, if the string passed in is "Do not include <", the first encoding gives you "Do not include &lt;", and the second will turn that to "Do not include &amp;lt;", so the visual result is:
    "Do not include &lt;".

    We only have one such message, so I have a workaround in place on the particular field that is used.

  2. #2
    Sencha - GXT Dev Team
    Join Date
    Feb 2009
    Location
    Minnesota
    Posts
    2,717
    Vote Rating
    87
    Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light

      0  

    Default


    Thanks for the report! I have opened a bug in our bug tracker.

Thread Participants: 1

Tags for this Thread