-
-
Notifications
You must be signed in to change notification settings - Fork 375
Fix: Sticky Navbar, AOSSIE Logo Visibility & Image Aspect Ratio Warnings #598
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
reach2saksham
wants to merge
2
commits into
AOSSIE-Org:main
from
reach2saksham:fix/navbar-sticky-logo-issue
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🌐 Web query:
Tailwind CSS arbitrary color syntax backticks v3 to-[] from-[] via-[]💡 Result:
In Tailwind CSS v3+, gradient stop utilities support arbitrary colors/values using square brackets — no backticks are part of Tailwind’s syntax:
If you’re using a CSS variable and Tailwind can’t infer the “type”, add a type hint (works for any arbitrary value, including gradient stops):
Tailwind generates CSS by scanning your source as plain text, so avoid building these class names dynamically at runtime (that’s when you might see people wrap class strings in JS backticks only because they’re using template literals, not because Tailwind requires them). If you must generate them dynamically, you’ll need a safelist/other approach so the classes still exist at build time. [1] [2] [3]
Sources: Tailwind gradient color stops + “custom value” examples [1], Tailwind arbitrary value type-hint syntax (
[color:...]) [2], Tailwind class detection behavior [3].🏁 Script executed:
Repository: AOSSIE-Org/website
Length of output: 89
🏁 Script executed:
Repository: AOSSIE-Org/website
Length of output: 657
Remove backticks from Tailwind arbitrary color tokens on Line 152.
The
to-[#00843D]/0,from-[#00843D]/0, andvia-[#00843D]/40syntax is invalid. Tailwind CSS arbitrary values use square brackets without backticks:to-[#00843D]/0,from-[#00843D]/0,via-[#00843D]/40.🎯 Proposed fix
📝 Committable suggestion
🤖 Prompt for AI Agents