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

Clipboard button container styling #470

Closed
AbdulTheActivePiecer opened this issue Oct 3, 2023 · 3 comments · Fixed by #523
Closed

Clipboard button container styling #470

AbdulTheActivePiecer opened this issue Oct 3, 2023 · 3 comments · Fixed by #523
Labels
enhancement Improvement request

Comments

@AbdulTheActivePiecer
Copy link

AbdulTheActivePiecer commented Oct 3, 2023

Hello.

Right now on v16.0.0, the clipboard button, be it a template or a component, it only shows on hover and disappears when not, and that styling is placed on the div container itself, can you please add a class instead so people can modify it.
image

A hacky fix would be to do this in your styles.scss/css
markdown{ //clipboard-container div[style="position: absolute; top: 0.5em; right: 0.5em; opacity: 0; transition: opacity 250ms ease-out 0s;"]{ opacity: 1 !important; } }

@prince-t-asamoah
Copy link

l

Awesome hack my friend, was getting frustrated on how to override this behaviour of the copy button. I think they should use classes to override this behavior

@MiriamS
Copy link

MiriamS commented Feb 14, 2024

I need to keep the button always visible, otherwise it's not accessible. Since the styles are added inline they would overwrite anything in css/scss. Is there a config option to have the button always present? I agree classes would be much better.

@jfcere
Copy link
Owner

jfcere commented May 26, 2024

Inline styling concerning the opacity transition has been removed and as suggested, CSS classes have been added to allow the customization of the position and transition on hover if desired.

This modification has been released as part of v18.0.0 along with Angular 18 update.

Please read the breaking changes carefully to know how to handle the changes.

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

Successfully merging a pull request may close this issue.

4 participants