Repository navigation
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughUpdated the feature flags guide to document color transition routing. Transitions remain on the animation loop when either endpoint uses 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Not worth a standalone docs PR. The note is recorded on #10305 instead, so it lands with platform color support rather than describing something CSS cannot express yet. |
Follow-up to #10328, to land together with platform color support (#10305), not before it.
The routing rules for platform-driven CSS transitions list the table, the callbacks and the iOS easing restriction, but not the shape a color value has to have. Only numeric colors reach the platform:
parseValueaccepts a color solely whenvalue.isNumber(), andparsePlatformValuesreturns nothing when either endpoint fails to parse, so aPlatformColoron one end keeps the whole property on the animation loop.Held as a draft on purpose. CSS does not support platform colors yet, so documenting how they route would describe something users cannot write. Once #10305 lands, this note belongs next to the other routing conditions, and the wording should be re-checked against whatever resolution that PR settles on.