Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

origin-* classes: would you take a PR for transformOrigin now, or after 5.0?

Ouverte
#509 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 3 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
56/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
react-native, tailwindcss, typescript
Domaine
frontend, mobile

Piste de recherche

Read the compatibility notes for the NativeWind v5 RC and inspect how origin-* classes are currently handled in react-native-css. The issue gives a reproduction using origin-top-left rotate-45 and the expected transformOrigin behavior on iOS and Android. Confirm whether a PR is wanted for the 5.0 release before starting; done means the class maps to the expected style and the behavior is covered on both platforms.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Before submitting a new issue
  • I tested using the latest version of the library, as the bug might be already fixed.
  • I tested using a supported version of react native.
  • I checked for possible duplicate issues, with possible answers.
  • I checked that React Native supports the styles I am using.
  • If using animations/transitions, I checked that React Native Reanimated supports the styles I am using.
Bug summary

More a question than a bug. We use react-native-css through the NativeWind v5 RC in our Expo app.

origin-top-left rotate-45 rotates around the center on iOS and Android, because the origin part is dropped. React Native has supported transformOrigin since 0.73, and style={{ transformOrigin: "top left", transform: [{ rotate: "45deg" }] }} rotates around the corner as expected. Checked on React Native 0.86.3, iOS 26.5 simulator and Android 17 emulator.

I saw it's listed as not supported in the RC compatibility notes, and that the v4 PR nativewind/nativewind#1126 was closed. Would you take a PR that maps the origin-* classes to transformOrigin now, or would you rather wait until after 5.0? Either is fine with me, the style prop works in the meantime.

Tailwind CSS classes
<View className="origin-top-left rotate-45" />
// style on iOS and Android: { transform: [{ rotateZ: "45deg" }] }
// expected: the same, plus a transformOrigin for the top left corner
Environment info
  npmPackages:
    react: 19.2.3 => 19.2.3
    react-native: 0.86.3 => 0.86.3
    react-native-css: 3.1.0-rc.0 => 3.1.0-rc.0
    tailwindcss: 4.1.12 => 4.1.12
Langage dominant
TypeScript
Étoiles
166
Forks
45
Merge moyen
13 j 14 h
PR mergées (30 j)
1

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de nativewind/react-native-css

Toutes les issues de nativewind/react-native-css

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.