Skip to content
New issue

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

backtick characters do not render correctly #1598

Open
4 tasks done
oznu opened this issue Oct 17, 2024 · 1 comment
Open
4 tasks done

backtick characters do not render correctly #1598

oznu opened this issue Oct 17, 2024 · 1 comment

Comments

@oznu
Copy link

oznu commented Oct 17, 2024

Describe the bug

When using the ` character it does not render correcly.

How to reproduce

This can be reproduced on the Clarity Docs site, https://clarity.design/documentation/input :


When single back ticks around around a word, the backticks get displayed over the first character.

Input should be `test`, but displays as:

image

When using multiple back ticks, only the first is shown:

Input should be ``` (3 back ticks in a row):

image

This behaviour is also observed in non-input fields, for example, editing the source of clarity to add ` around the word input in this paragraph:

image
image

Expected behaviour

Backticks are rendered correctly as per the user's input.

Versions

Clarity version:

  • v17.x
  • v18.x

Framework version:

  • Angular v17.x
  • Angular v18.x

Device:

  • Type: Desktop
  • OS: macOS and Windows
  • Browser: Edge, Firefox, Safari

Thanks 😄

@oznu oznu changed the title "backtick" characters do not render correctly ` "backtick" ` characters do not render correctly Oct 17, 2024
@oznu oznu changed the title ` "backtick" ` characters do not render correctly backtick characters do not render correctly Oct 17, 2024
@oznu oznu changed the title backtick characters do not render correctly backtick characters do not render correctly Oct 17, 2024
@dtsanevmw
Copy link
Contributor

Hello,

We are aware of this issue but it requires updating the font version which for us now is a breaking change and it could happen in a major release.

Regards,
Daniel Tsanev

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants