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

<sup> looks just like <sub> #667

Open
9 of 15 tasks
rjapenga opened this issue Aug 10, 2024 · 5 comments
Open
9 of 15 tasks

<sup> looks just like <sub> #667

rjapenga opened this issue Aug 10, 2024 · 5 comments
Labels
bug:upstream The bug is caused by a third party library.

Comments

@rjapenga
Copy link

Decision Table

  • My issue does not look like “The HTML attribute 'xxx' is ignored” (unless we claim support for it)
  • My issue does not look like “The HTML element <yyy> is not rendered”

Good Faith Declaration

Description

works just like on both Android and iOS in 6.3.1

See snack: https://snack.expo.dev/@rjapenga/superscript

React Native Information

confer snack

RNRH Version

6.3.1

Tested Platforms

  • Android
  • iOS
  • Web
  • MacOS
  • Windows

Reproduction Platforms

  • Android
  • iOS
  • Web
  • MacOS
  • Windows

Minimal, Reproducible Example

https://snack.expo.dev/@rjapenga/superscript

Additional Notes

Simple to reproduce

@rjapenga rjapenga added the bug Crush'em all. label Aug 10, 2024
@qwertychouskie
Copy link

For those who got confused reading the Description section, I'm pretty sure it's supposed to say this:

<sup> works just like <sub> on both Android and iOS in 6.3.1

GitHub "helpfully" interpreted the <sup> and <sub> tags, making for a confusing bug report.

FWIW, I tested the linked snack with 6.3.4 and it had the same issue.

I think this issue may be related to #76. See also this commit: 002b7fb

@qwertychouskie
Copy link

qwertychouskie commented Sep 20, 2024

Relevant upstream issue: facebook/react-native#30375

@jsamr Perhaps the FAQ should be updated to point to that upstream issue link. Right now it points to a defunct page.

EDIT: Snack that may be useful later: https://snack.expo.dev/11Yj2nxiXyE1UY1F7wID8

@jsamr jsamr added bug:upstream The bug is caused by a third party library. and removed bug Crush'em all. labels Sep 21, 2024
@jsamr
Copy link
Collaborator

jsamr commented Sep 23, 2024

@qwertychouskie Sure! PR welcomed.

@rjapenga
Copy link
Author

For those who got confused reading the Description section, I'm pretty sure it's supposed to say this:

<sup> works just like <sub> on both Android and iOS in 6.3.1

GitHub "helpfully" interpreted the <sup> and <sub> tags, making for a confusing bug report.

FWIW, I tested the linked snack with 6.3.4 and it had the same issue.

I think this issue may be related to #76. See also this commit: 002b7fb

Yes - sorry that I didn't notice how "helpful" gitHub was.

@rjapenga
Copy link
Author

If I understand all of this (mostly shorthand to me), you are saying that the bug is upstream and must be fixed by React Native. Is that correct? How does one notify Meta of this bug or is it already logged as a React Native bug? 30375 is listed as Android. I see the bug on iOS and Android.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug:upstream The bug is caused by a third party library.
Projects
None yet
Development

No branches or pull requests

3 participants