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

fix(inpage): Renaming selector for active element - FRONT-4386 #3358

Merged
merged 1 commit into from
Apr 23, 2024

Conversation

planctus
Copy link
Collaborator

This turn out to be a kind of conflict between the selector added to the active "heading element" and the default css which excludes h2s with a selector starting with ecl. So the fix is only renaming this selector to prevent this exclusion.

Copy link

@github-actions github-actions bot temporarily deployed to pull request April 23, 2024 11:16 Inactive
Copy link
Contributor

@emeryro emeryro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm a little worried by this change. If users are relying on the css class for something on their side, it would be a (limited) breaking change. Also I see that the spyClass is still using 'ecl-inpage-navigation__item--active'. Is it on purpose?

The only other solution I see would be to add an exception in our css. That's quite dirty also, though...
image

@planctus
Copy link
Collaborator Author

I don't know, it doesn't really feel like anything critical, we do not style that selector at all, we can mark the pr with "markup changes" in case, if we really worry about any usage of this selector, it seems cleaner doing this than introducing an exception for this selector in the default css.
For the other selector, that is not problematic and we have some styles associated to.

@planctus planctus removed the Question label Apr 23, 2024
@emeryro emeryro merged commit 9f04e8a into v4-dev Apr 23, 2024
7 checks passed
@emeryro emeryro deleted the FRONT-4386-In-page-active-heading branch April 23, 2024 13:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants