Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    12.0p+ TextItem masking broken

    Hi Isomorphic,

    TextItem masking is broken in current online 12.0p and 13.0d (v12.0p_2021-07-06 / SNAPSHOT_v13.0d_2021-07-09) in Firefox 89 and Chromium 91. It's worst in 12.0p Firefox.

    Please replace the mask code for first name with the code for "color" you give in the sample description:

    Code:
    Custom mask characters can be defined by a standard regular expression character set or range. For example, a hexadecimal color code mask could be:
    \#>[0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F]
    Code:
    { name: "color", title: "Color", editorType: "TextItem",
    mask: "\#>[0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F][0-9A-F]", hint: "<nobr>#AABB00-style color code</nobr>"},
    • In 13.0d GC and FF the "\#" is not working as expected. It's interpreted as "only digit allowed"
    • In 12.0p FF the same is happening and also backspace is not removing character correctly
    Could you also add the color sample to the actual sample code? It shows another feature, Regexp in combination with masking, that the current samples don't show.

    Best regards
    Blama

    #2
    We'll take a look at the logic, but you should find the mask working as you expect if you escape the initial regex char, like "\\#...".

    The 12.0 misbehavior is one of a bunch of known issues in this code, already fixed in 12.1+ - we'll backport the fixes shortly and update here when it's in.

    Comment


      #3
      Hi Isomorphic,

      yes, it's working as expected in 13.0d with the \\#
      Can you add that sample to the code and perhaps just mention it in the sample description?

      Best regards
      Blama

      Comment


        #4
        We've back-ported the necessary fixes for the various 12.0 masked TextItem edit misbehaviors we mentioned.

        We've also confirmed that you do need to escape any escape-chars in masks, so a pair of backslashes is the correct usage - we'll make this clear in docs.

        The sample has been updated in 12.0+ as you suggested, so it demonstrates an "HTML Color" mask in use, rather than mentioning it in the sample doc.

        All of this will be in tomorrow's builds, dated July 14 or later.

        Comment


          #5
          Hi Isomorphic,

          this is fixed for me in 12.0p using v12.0p_2021-08-08, I can also see the sample and description changes.

          Thank you & Best regards,
          Blama

          Comment

          Working...
          X