Forum Replies Created
-
AuthorPosts
-
I understand, thanks for your support!
This reply has been marked as private.This reply has been marked as private.This reply has been marked as private.1.
Here is what it looks like on my mobile phone (very far from full screen):
Compare this to this one (which is also a screenshot of the same mobile phone):
That is how I want it to look in the ideal world.
Other lightboxes handles this Much better.
Here is an example from Jetpack Carousel (almost fullscreen):
Here is an example from iLightBox (almost fullscreen as well):
Go back to the first picture and take a look again. It’s only a fraction of the size compared to the other ones.
3.
Black works fine.4.
Fair enough, but my note about you having the totally wrong information on your product site doesn’t bother you at all? Jeez.This reply has been marked as private.http://themeforest.net/item/enfold-responsive-multipurpose-theme/4519990
There you go. That’s the only link that is relevant to all the points I described. Since I got the exact same answer in my other thread, I doubt that you actually read the post itself.
What link? Did you even read the description, or did you not understand what I meant?
We can close this issue if you want, since I don’t reallt have an issue here.
However, I still don’t think you understand me here. I know that it is 100% on the latest version, but that was NOT the case before 3.1, and it doesn’t say anything about it in the changelog, why I wondered if this was an unintentional change or not. If it was, indeed, unintentional, then I would prefer not to customize my css, and just wait until it’s fixed.
But it doesn’t really matter. It is a minor issue at most, and I appreciate your solution. If you want, you can leave a final answer, otherwise just mark it as solved. Don’t really want to waste support time here. I have other issues that are by far more important in that case ;)
Thanks for your support!
Thanks for you answer. However, I was mainly just curious if this was intentional or not. If not, I could’ve wait for next release for it to be “fixed” otherwise. Reason for this is that I prefer to avoid customized css as much as possible. Should future behaviour be changed, this would become obsolete and override future changes, which I prefer to avoid.
Thank you very much, that did the trick!
Case closed, happy with the response!
Thank you for your response. However, the code only hides the text when I try it on my mobile device. The white “block” with the short “arrow” is still there, and thus covers up part of the picture (and the purpose from the beginning was to not have it cover up the picture). I guess moving the white block to below the picture would also be an acceptable solution.
-
AuthorPosts