Problem with currencySymbol containing dollar sign character

Current behavior

When the currencySymbol contains a dollar sign a problem happens with the caret position. When you try to edit a value already formatted the caret always go to the end of the input.

Expected behavior

The caret should stay on the same place.

Steps to reproduce the problem

1. Tested on autoNumeric version <v4.5.9>
2. In the browser <Chrome> version <74>
3. On the <Linux> operating system
4. Then instantiate the autoNumeric object with the following options:

new AutoNumeric(domElement, { currencySymbol: 'R$ ' });

or

new AutoNumeric(domElement).brazilian();

or

new AutoNumeric(domElement, { currencySymbol: '$ ' });

1. Input some value. Click outside the input. Click back inside the input, put the caret before the decimal character. Type some number. ERROR! The caret went to the end!

Debugging

The problem is the function _formatValue.

        var leftReg;

        if (this.settings.currencySymbolPlacement === AutoNumeric.options.currencySymbolPlacement.suffix) {
          leftReg = new RegExp("^.*?".concat(leftAr.join('.*?')));
        } else {
          // prefix is assumed
          leftReg = new RegExp("^.*".concat(this.settings.currencySymbol, ".*").concat(leftAr.join('.*?'))); // Fixes issue #647 when using a currency that has some characters in it that matches the value we just entered (ie. numbers in the currency)
        } // Search cursor position in formatted value

        var newLeft = value.match(leftReg);

When the currencySymbol has a dollar sign the value.match does not work. The dollar sign on the leftReg expression should be escaped.

Link to live example

I’ve tested on the autonumeric codepen example… Just change .french() to .brazilian() and that is it!

Thanks!!!

[VEnis]

As a quick workaround you can use another unicode dollar sign symbol like https://www.compart.com/en/unicode/U+FF04 as a currency symbol

[Blackbaud-TrevorBurch]

@AlexandreBonneau - I see that a fix #684, which this appears to be a duplicate of, this was merged into the codebase on July 7. However, it does not seem that a release has been cut with this fix. Would you happen to have an ETA for when a release might happen for this fix? Thanks for any info! 😄