We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug
Below, selector string is created using the id of the element.
ui-kit/packages/components/inputs/money-input/src/money-input.tsx
Lines 43 to 44 in 5ce0b2a
According to https://developer.mozilla.org/en-US/docs/Web/API/Document/querySelector
Note: Characters that are not part of standard CSS syntax must be escaped using a backslash character.
To Reproduce
When the high precision price tooltip is activated on a list of MoneyInputs managed by formik, such an exception is thrown:
MoneyInput
formik
Expected behavior
Non supported characters in the selector string should be escaped like so (notice double \):
\
document.querySelector("#portal-tiers\\.1\\.value")
Using CSS.escape(str) seems to be a good solution: https://developer.mozilla.org/en-US/docs/Web/API/CSS/escape_static
CSS.escape(str)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
Below, selector string is created using the id of the element.
ui-kit/packages/components/inputs/money-input/src/money-input.tsx
Lines 43 to 44 in 5ce0b2a
According to https://developer.mozilla.org/en-US/docs/Web/API/Document/querySelector
To Reproduce
When the high precision price tooltip is activated on a list of
MoneyInput
s managed byformik
, such an exception is thrown:Expected behavior
Non supported characters in the selector string should be escaped like so (notice double
\
):document.querySelector("#portal-tiers\\.1\\.value")
Using
CSS.escape(str)
seems to be a good solution:https://developer.mozilla.org/en-US/docs/Web/API/CSS/escape_static
The text was updated successfully, but these errors were encountered: