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

Linear Progress in reversed mode reverses content of the default slot #7261

Closed
mclate opened this issue Jun 20, 2020 · 3 comments · Fixed by #7319
Closed

Linear Progress in reversed mode reverses content of the default slot #7261

mclate opened this issue Jun 20, 2020 · 3 comments · Fixed by #7319

Comments

@mclate
Copy link

mclate commented Jun 20, 2020

Describe the bug
When using q-linear-progress with default slot and reverse property, whole content of default slot is being mirrored. (You can also see styles being messed a bit)
Also notice that in reversed mode default slot is hidden beneath the progress bar (see jsfiddle) in case when progress bar overlaps with the slot content.

Codepen/jsFiddle/Codesandbox (required)

https://jsfiddle.net/1ghd82k6/

To Reproduce
Steps to reproduce the behavior:

  1. Create q-linear-progress with a default slot as described in official documentation
  2. Apply reverse property
  3. Observe default slot dissappearing

Expected behavior
Default slot to remain unchanged and visible in reverse mode

Platform (please complete the following information):
OS: MacOS
Node:v14.3.0
Browsers: Brave

@mclate
Copy link
Author

mclate commented Jun 20, 2020

Looks like this is due to how reverse is implemented. I see that it applies transform: scale3d(-1, 1, 1); style to a whole q-linear-progress

@webnoob
Copy link
Contributor

webnoob commented Jun 28, 2020

@mclate As a work around, just do another transform on your content: https://codepen.io/webnoob/pen/wvMqbKG

@pdanpdan Do you have a suggested fix for this? Could we just re-apply a transform around the default slot content (similar to what I've done in the codepen above)? I've not looked at the code so it might be possible to just target the actual progress bar with the transform. Will look this afternoon. The transform applies to the entire element with no way to currently just target the progress bar as far as I can see.

@webnoob webnoob self-assigned this Jun 28, 2020
@pdanpdan pdanpdan self-assigned this Jul 5, 2020
@webnoob
Copy link
Contributor

webnoob commented Jul 10, 2020

Fix available in 1.12.9

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

Successfully merging a pull request may close this issue.

3 participants