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

[bug]: documentation examples render </ as ↙️ #2138

Closed
5 tasks
elmarsto opened this issue Apr 4, 2023 · 2 comments · Fixed by #2147
Closed
5 tasks

[bug]: documentation examples render </ as ↙️ #2138

elmarsto opened this issue Apr 4, 2023 · 2 comments · Fixed by #2147
Labels
area: docs kind: bug Something isn't working

Comments

@elmarsto
Copy link

elmarsto commented Apr 4, 2023

Which react-spring target are you using?

  • @react-spring/web
  • @react-spring/three
  • @react-spring/native
  • @react-spring/konva
  • @react-spring/zdog

What version of react-spring are you using?

n/a

What's Wrong?

image

To Reproduce

Visit React-spring docs w Firefox on Linux. (Other platforms and browsers may also be affected)

Expected Behaviour

</ should render as </ and not ↙️

Link to repo

https://www.react-spring.dev/docs/components/use-chain

@elmarsto elmarsto added the template: bug This issue might be a bug label Apr 4, 2023
@joshuaellis joshuaellis added kind: bug Something isn't working area: docs and removed template: bug This issue might be a bug labels Apr 4, 2023
@elmarsto
Copy link
Author

elmarsto commented Apr 4, 2023

Interesting. Chrome on Linux does not have this problem. It would appear that the font Space Mono has ligatures activated in Firefox, but not in Chrome.

Tentative diagnosis is incomplete browser CSS‌ reset, to paper over varying browser defaults.

I wonder if this CSS would fix it

investigating

@elmarsto
Copy link
Author

elmarsto commented Apr 5, 2023

Confirmed it's like this on Firefox Windows as well. This is an FF problem.
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: docs kind: bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants