Chore: CSS conflicting property in development

[a0m0rajab]

Type of feature

🐛 Fix

Current behavior

This could be a minor development but thought to address it here, when I worked on #2185 I got this warning in the console:

Warning: Updating a style property during rerender (overflowY) when a conflicting property is set (overflow) can lead to styling bugs. To avoid this, don't mix shorthand and non-shorthand properties for the same value; instead, replace the shorthand with separate values.

I thought it would worth to open an issue for that and check it, this happened at this stream

Suggested solution

No response

Additional context

Discovered in #2185

Code of Conduct

• I agree to follow this project's Code of Conduct

Contributing Docs

• I agree to follow this project's Contribution Docs

[github-actions]

Thanks for the issue, our team will look into it as soon as possible! If you would like to work on this issue, please wait for us to decide if it's ready. The issue will be ready to work on once we remove the "needs triage" label.

To claim an issue that does not have the "needs triage" label, please leave a comment that says ".take". If you have any questions, please reach out to us on Discord or follow up on the issue itself.

For full info on how to contribute, please check out our contributors guide.

[nickytonline]

Feel free to work on this if you'd like @a0m0rajab.

[a0m0rajab]

@nickytonline thanks for the suggestion, I think I will keep it open and work on something else these days, might pick it up in the next few weeks if no one picked it up.

[sital002]

.take

[sital002]

I am not able to reproduce the bug can you provide the URL for it.

[nickytonline]

@a0m0rajab, do you remember what page this warning was happening on?

[a0m0rajab]

It was in this URL: app.opensauced.pizza/ai/dashboard/filter/top-100-repos?range=30

Here is the video of the error: https://www.youtube.com/live/pGGV8cVsaj0?si=m_PlWAzwxV22lJ06&t=4563

I think it appeared when I run the project in debugger in VsCode.

[nickytonline]

This might only be a development mode issue as it does not occur on that page in production.

[a0m0rajab]

I think so since the warning does not appear on production, do you think we should work on this or just ignore that?

[brandonroberts]

Let's close this one for now as its a dev only warning