#issue number 1934 Fix "first-child" pseudo class error #1935
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🌟 What does this PR do?
Fix the error thrown by Emotion JS when using
:first-child
pseudo class selector.The error stems from the
RunningTimerDescription
component inside theTimer
component.The
RunningTimerDescription
component, denoted by the smaller rectangle with orange stroke, is targeted via>div:first-child
. However, this component uses Emotion JS, which sometimes inject a<style>
element as the first child of an element, making the:first-child
rule vulnerable to break.Hence, I removed the
>div::first-child
rule and applied CSS properties directly to theRunningTimerDescription
.🐛 Recommendations for testing
:first-child
selector.Timer
component and press Enter key or click the Stop button next to it. The input field will turn into theRunningTimerDescription
and all the styling remain the same as before.📝 Links to relevant issues or information
#1934
Fixes #1934