Skip to content
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

I can't override the color style of the active menu items in the offcanvas menu #391

Open
Strngest opened this issue Feb 3, 2024 · 3 comments
Labels

Comments

@Strngest
Copy link

Strngest commented Feb 3, 2024

I am using the current version of the template 2.0.18. I cannot override the color style of the active menu items in the offcanvas menu in the "custom.css" file. The problem is that in the "template.css" file, this style is defined as "!important".

Here is the code from the "template.css" file:

.offcanvas-menu .offcanvas-inner ul.menu li.active a {
color: #00aeef !important
}

The "!important" modifier is clearly unnecessary here.
This effect was not observed in earlier versions of the Helix Ulimate template.
In earlier versions of the template, the color of the active menu items was changed by editing "custom.css" file, but after updating the template, this feature disappeared. Please fix this minor flaw in the wonderful Helix Ultimate Framework.

@joomleb
Copy link

joomleb commented Feb 9, 2024

Hi @Strngest
Yes, the not adequate use of "important" has been reported more than one time, like #318
It should be deprecated and code cleaned.

Maybe also #323 is related to this.

@mi-prakash Please, Can you clean the code for the next HU release ?

@mi-prakash
Copy link
Collaborator

@Strngest @joomleb
I'll check the issue,
thanks for the feedback

@mi-prakash mi-prakash added the bug label Feb 9, 2024
mi-prakash added a commit that referenced this issue May 6, 2024
#391 !important removed from offcanvas active menu color
@joomleb
Copy link

joomleb commented May 7, 2024

Hi guys,
Helix Ultimate 2.1.1 has been released:

@Strngest
Please, Is this fixed for you ?

@mi-prakash
Should this fix solve also the #318 report ?
Is the #323 related to this.?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants