-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
[Media Object] Mixins not functioning in flex mode #9038
Comments
I may have fixed part of the problem by adding
|
I don't think there is any flex mode set up for this component. Should be straight forward to add it though. |
@rafibomb I see you added help wanted so going to assume assigning it to yourself doesn't mean you don't want someone to take it... @marcusmoore would you like to take a crack at a PR to address this? |
@kball Unfortunately I don't have the time right now. I can take a look in a few weeks if it's still open but I can't commit to it right now. |
I took a swing at refactoring the Media Object mixins here: #10679 |
Addresses Media Object mixin issue in Flex mode. #9038.
This looks like the PR addressing this was successfully merged into core so closing this. |
…n-flex-mode for v6.5.0 310e3dc Addresses Media Object mixin issue in Flex mode. foundation#9038. af9d697 Adds Media Object visual test page. 606f164 fix: prevent side-effect from .stack-for in media-object Co-Authored-By: Nicolas Coden <nicolas@ncoden.fr> Signed-off-by: Nicolas Coden <nicolas@ncoden.fr>
How can we reproduce this bug?
Assuming we are compiling our assets
media-object-container
andmedia-object-section()
)What did you expect to happen?
The output from the example code and the component code would be the same.
What happened instead?
The required
.main-section
is overridden by the compiled media object mixin.The
Test case:
Here is a gist with my code and some screenshots demonstrating the issue:
Desktop
Mobile
The text was updated successfully, but these errors were encountered: