-
Notifications
You must be signed in to change notification settings - Fork 94
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
conflict with bootstrap #211
Comments
I have seen this too. Simon |
We are aware of this issue. The "modal" class was used traditionally by Joomla! to add modals. I think that the fix by @K2Joom does solve the issue. |
We need to wait for this. There is a related issue #246 . |
My two cents here, since this modal is also used in the frontend editing panel, and this is the default modal of older Joomla! version (which are supported with this version), this needs to be solved in the template. In the upcoming version where only Joomla! 3.x is supported the modal will be completely stripped. |
MooTools will be completely dropped so this issue will be resolved. |
@kricore This has nothing to do with Mootools. It's the "modal" class name that conflicts with Bootstrap styles. |
Since mootools will be removed and a new lightbox engine will be used, the On Wed, Mar 9, 2016 at 6:00 PM, Lefteris Kavadas notifications@github.com
|
No, that's not the case. The class name will probably maintained for backwards compatibility, for people that are using overrides. |
Let's drop the CSS class. We'll add a notice in the release notes about it. Those who had the class on their overrides won't see a difference as the new initialization method is backwards compatible and will trigger the new modal. Obviously people who had the "modal" class so far either didn't use Bootstrap or they had used a workaround all this time. So you @kavadas and @kricore you are both right :) Closing this one. |
Hi,
I'd like to inform you that there is a conflict between the k2 2.6.8 and the bootstrap 3.2.0: The images of the k2 items don't display. I've found that the problem is caused by the class="modal" of the links:
thanks for the attention,
Marc
The text was updated successfully, but these errors were encountered: