Forum Replies Created
-
Posts
-
Thanks very much for your response! I will be putting the site live shortly and then I can send you links.
The mention of iOS changes is helpful; we may be getting closer.
I tried Chrome as well. In Chrome, with the above code under Enfold 2.7.1, the “sticky footer” DOES stay in place on ANY size window, regardless of whether a right-scrollbar is in place. The code used to behave correctly this way under OS X/Safari and 2.5.2, but now under OSX/Safari and 2.7.1, the “sticky footer” only shows IF there is a right-scrollbar on the page. With no right-scrollbar under OSX/Safari and 2.7.1, no “sticky footer” appears, although it is still “there” (you can still click the links), but is “invisible.”
I think I will go live, and then I will send you links, but in the meantime can you please do me a huge favor:
If you try the exact same code on a page where there is NO right-scrollbar (i.e. either low page content, and/or large window), do you get the same sticky footer, or does it “disappear”:
— Under OS X/Safari?
— Under iOS (tablet or phone)?And if the “sticky footer” does “disappear” on “no-scrollbar” pages only under OSX/Safari and iOS (but not under other browsers), is there any way to fix this so the code behaves the same way under all browsers?
That’s OK, thanks for your helpful response! Once I was able to get my logo spacing and overlap (with the mobile menu icon) worked out, the mobile drop down menu is not so important, and I suppose the current mobile menu is more modern and future-looking anyway.
The “fixed socket” bug/behavior change in 2.7.1 that I posted about in another post is far more important to me to get fixed, so if there is any way we might be able to resolve that, I would be ever-so-grateful!
Hey Devin,
#socket { font-size: 15px !important; position: fixed; bottom: 0px; width: 100%; overflow: hidden; }
#socket .container { padding: 4px 0 6px 0; }
html { background: #ffffff; }For me, the above css code DOES (or DID) create a fixed socket container in 2.5.2. What is confusing and unfortunate is why it STOPPED working the same way in 2.7.1 (more details in the post linked above). It may be some change related to how fixed positioning or transparency is newly handled in 2.7.1? Were there changes maded in those areas in 2.7.1?
Now in 2.7.1, with that code, the “fixed socket” only shows IF a scrollbar is present. In 2.5.2 the “fixed socket” showed with or w/o scrollbar present.
Since it WAS working great to give a “fixed socket” in 2.5.2, I’m hoping the Kriesi team might have some insight into why it STOPPED working the same in 2.7.1, and how to fix it? I’d love to get it back to how it was working, because it was a really key feature I need for my site! Any ideas how to get it working again in 2.7.1?
Yes, I’m sorry you are having similar issues! Stuff like this is very frustrating, and costs everybody a lot of time. I’m really hoping the Kriesi team can help get these issues fixed, so that I don’t have to revert back to an “old” theme version indefinitely!
At least in my experience, in version 2.5.2 this custom css code USED to work to “lock” a socket in place, at the bottom of ANY page regardless of browser/window size, no matter how much or how little page content was present, etc. It was great.
#socket { font-size: 15px !important; position: fixed; bottom: 0px; width: 100%; overflow: hidden; }
#socket .container { padding: 4px 0 6px 0; }
html { background: #ffffff; }NOW under 2.7.1, in my system with that same custom CSS, I only “see” the socket if there is a right-side scrollbar present. On pages with no scroll-bar, no socket shows any more under 2.7.1 (although it stil seems to be there, but just not “visible”). (I posted here: https://kriesi.at/support/topic/2-7-1-update-changed-custom-css-socket-behavior/)
If you want to try the above code in Version 2.7.1 and see if you get the same behavior in your system, and post back here, that would be very helpful. That code used to work great to give a “fixed socket” in 2.5.2, but it stopped working correctly in 2.7.1!
