Repository navigation
fix: recognize progress pseudo-elements - #1968
Conversation
|
Hi @Arnav7x! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at [email protected]. Thanks! |
|
@Arnav7x is attempting to deploy a commit to the Meta Open Source Team on Vercel. A member of the Team first needs to authorize it. |
|
@Arnav7x are you able to sign the CLA? Thanks! |
Yep, just did. Works fine for me. |
What changed / motivation?
Added support for the following progress pseudo-elements in StyleX's ESLint validation and TypeScript style definitions:
::-webkit-progress-bar::-webkit-progress-value::-moz-progress-barThese are valid CSS pseudo-elements used to style different parts of native progress indicators. Without this support, the ESLint plugin reports them as unknown pseudo-elements, preventing their use in StyleX styles.
Added a regression test covering all three pseudo-elements to ensure they are recognized correctly.
Linked PR/Issues
Fixes #1967
Additional Context
Tests
git diff --checkcompleted successfully.Pre-flight checklist