Jan Sorgalla
Jan Sorgalla
Yes, that's a good idea. I'm goint to implement that for the next version. 👍
There has been no special reason, never thought about that use case when leaving them out. Will consider adding a default theme back.
On page load, the hash can be read from `window.location.hash`. If theres a inline element with a corresponding ID, that could be used as an ID selector to open the...
The only way currently is to overwrite the css: https://github.com/jsor/lity/blob/7c3162be6238c80c9df59ea5dc48169aef2efc2f/dist/lity.css#L169-L197
I suspect this some other error which just prevents the lity code from running. Do you have a reproducible test case?
Unfortunately, that doesn't help much. Still same guess as in https://github.com/jsor/lity/issues/168#issuecomment-382986878 :(
This is the intended behaviour. What do you expect intead?
Are you using a `` as closing control? Try using a `` or use a workaround like: ```js $(document).on('click', '[data-lity-close]', function (e) { e.preventDefault(); }); ```
You're probably calling `on()` on a HTMLElement, not on a jQuery instance. You must ensure to wrap the element like `$(element).on(...)` instead of `element.on(...)`.
Yep, this isn't ideal atm. sorry. It's on my todo-list...