Sticky Footer causes footer to not stick in IE11

Permalink Browser Info Environment
Hi,

This one seems "simple", and I can reproduce it in my setup.

So, in IE11, the highest version of IE in Windows 7, the Sticky Footer feature doesn't work, in fact it causes the footer to go even higher when enabled, whether the page has content in Main or not.

All I did to "fix" it was turn it off, clear cache, and IE11 now has the footer where one would expect it without Sticky Footer. Either at the bottom if the page causes scrolling, or higher if there's not a full page of Main content.

IE11 compatibility is an important feature to me. So, I'm hoping this shouldn't be a lot of work to get fixed.

Please let me know if you need any more info from me :)

Type: Ticket
Status: Archived
View Replies:
c5hub replied on at Permalink Reply
c5hub
The sticky footer functionality uses something called 'flexbox' which is more prevalent since CSS3. Unfortunately there is limited support for IE11 so if this is essential to you then you should leave this option turned off.

See link below for compatibility with this feature:
http://caniuse.com/#feat=flexbox...
BloodyIron replied on at Permalink Reply
Aha, so is this a hard limitation? As in, no real way to have it nicely working on IE11, or?

I'm not trying to be a stick in the mud here, just diligent, so your feedback/help is appreciated!
c5hub replied on at Permalink Reply
c5hub
Not currently.
BloodyIron replied on at Permalink Reply
What would it take?
c5hub replied on at Permalink Reply
c5hub
That's a question for Microsoft.
BloodyIron replied on at Permalink Reply
Well, considering IE11 is still the most used version of Internet Explorer on the web (https://www.w3counter.com/globalstats.php... ) and my client has a mandatory requirement of compatibility with IE11, I'm going to need your help solving this.

Is there any sort of work-around specific to IE11 that could be implemented to achieve the same effect? Is that CSS3 method the only way? Or is this a limitation of what you're prepared to do?

I know for a fact I'm not the only one out there with IE11 being part of the required spec. Consider that IE11 is the highest IE you can get in Windows 7, and how resilient people are to giving up Windows 7.
BloodyIron replied on at Permalink Reply
Also, I'm rather confused by the earlier mentioned flexbox compatibility list, since it says partial compatibility, and MS lists official support (https://msdn.microsoft.com/library/dn265027(v=vs.85).aspx... ) as of Sept 2012.

Sorry to talk in two separate posts, but I just wanted to add this without it being missed. Surely there must be a way to correct this for IE11. I know there will be others, lots, that benefit from this fix.
BloodyIron replied on at Permalink Reply
So yeah, turns out IE11 is actually used way more than I thought. It's the highest version in Windows 7, 8.1 and 10. There will not be a newer version of Internet Explorer.

Are you refusing support for this function for IE11 even though MS documentation says it's a compatible feature?
c5hub replied on at Permalink Reply
c5hub
The partial support status is due to a buggy implementation.

To be clear, this feature is not fully supported by IE11. The flexbox implementation has issues, and these are issues which are not our responsibility. You're asking us to spend time devising and implementing all manner of workarounds just to get this to work on IE 11. We won't do this.

Once MS sort the issues with the flexbox implementation this should work just as it does in other browsers, until then please leave this option turned off.

There are limits to the support we'll offer. I'm sorry if this is not what you want to hear.
BloodyIron replied on at Permalink Reply
Considering this is a paid product, the theme, I don't see why asking for a work around, or fix, is unreasonable. I would not be the only one impacted by this, and even still it sounds like you haven't explored what I would even consider a reasonable work-around. I understand there is a limit to reasonable support here, but you should stand behind your product and this function does not work for a major browser found in every currently supported version of Windows.

Would you be willing to put in a check-box beside the sticky footer checkbox "disable for IE11"? Whereby if the website detects the IE11 client the sticky footer is disabled?

Perhaps some additional information describing our experience with this feature would help put this in perspective.

When Sticky Footer is on, it works in Chrome, Firefox and last I checked Edge. But when IE11 is used it looks SO BAD that anyone using the website would just leave. This is such a big deal when it's enabled that it's embarrassing. It's embarrassing to us, my clients, and I'm very surprised you're not even the slightest bit embarrassed by how this actually looks when used, because it's like vomiting all over a page. The footer comes up to overlap the top 30% of the page. Would that look even the slightest bit professional to you? If you think yes, then maybe we should rethink the use of your product in the immediate and long-term.
BloodyIron replied on at Permalink Reply
What can we do to coordinate a work-around for this? This is a big issue for one of my clients, and I can't let this rest. I don't want to waste your time, but this is an absolute requirement for me to find something to improve the current situation.

I'm not asking you to re-write Internet Explorer, but we need to find a solution that works for both of us. What can we do to solve this? Please let me know, I really need your help here! :(
BloodyIron replied on at Permalink Reply
It's been about a month since your last reply, and I haven't actually seen any option presented from you that improves my situation. Just disabling the feature is not an acceptable option.

How about instead of letting this thread rot, and working against your public image, you present some options to me that could work for both of us. It doesn't even need to be a complex solution, but I do need your help.

As it stands, I am a PAYING customer, and while I understand that doesn't give me a blank cheque for support, right now I've only received some responses, with zero solutions that work for me.

So, help me out here, please. I need it.
c5hub replied on at Permalink Reply
c5hub
This feature is not compatible with IE11 - this is due to lack of support of certain CSS3 features within the browser.

Whilst this may not be the answer you are looking for, this is the only answer we have.

We would hope that this theme has so many features, block and tools above and beyond anything else out there, that this small discrepancy does not detract to much from the product.
BloodyIron replied on at Permalink Reply
Yeah, I'm starting to think you guys have no clue about customer support.

You're now repeating yourself, and not even addressing the possible solution I have proposed, let alone proposing a SOLUTION to the issue. The solution I postulated works around the IE11 compatibility issue, and yet you're not even talking about it.

I know that the theme pack is awesome, that's why I'm using it. But this feature makes your theme pack look like a steaming pile of garbage when it breaks. Seriously, I don't think you understand how BAD this makes the website looks. When enabled it is UNUSABLE.

I know that the issue is with IE11, that has been explained to me repeatedly. I am wanting a solution that works around it. Did you actually read the idea that I proposed?

I'm not talking about making it _WORK_ in IE11, that's clearly not possible. I'm talking about making it so I can have the feature work in browsers _THAT ARE NOT IE11_, while having the feature automatically disabled for IE11 at the same time.

This theme pack is awesome. I want to use it on more sites that I develop. But if this is the level of customer support I can come to expect in the future, then I'm going to be looking elsewhere. So please, help me find a solution here, or I'm voting with my dollar.

Oh, and this is on a public forum, so consider that this entire conversation is going to be read by other individuals. Do you really think it's going to reflect well upon you showing that you guys are _COMPLETELY UNWILLING_ to help fix a feature like this?
c5hub replied on at Permalink Reply
c5hub
Abusing our products and service over a minor feature because we will not bend over and spend time trying to do what Microsoft hasn't bothered to and; that your client seems unreasonable enough to persist in pushing you over, is not a good way to move fowards.

If you would like a refund please ask, we'll gladly oblige, how is that?

But no matter, we don't wish to converse with you any further on this one, and will not. Please feel free to continue however, we've nothing to hide here, and are more than happy to leave this thread open.

Thank you.
BloodyIron replied on at Permalink Reply
Hi,

I am responding now, because I believe in the fundamentals outlined in this XKCD strip :http://xkcd.com/979/ . As in, that one should post a solution, when found, so others can find it should they need it.


We, without ANY of your (c5hub) help, have found a solution. And we're going to share it, because it's the right thing to do, not because you (c5hub) somehow deserve it.

For those reading this, our fix disables the sticky footer in IE11, but lets it work in other browsers that support it (such as Chrome, Edge and Firefox). You will just need to modify one file, and create another.


This was originally written to adjust the v4.0.1 version of Fundamental, and should work for future versions.

1. Modify your /packages/fundamental/themes/fundamental/elements/head.php , this is the version we used :http://pastebin.com/ahHKwawn

2. Create the file /packages/fundamental/themes/fundamental/css/legacy-flexbox.css , this is the version we used :http://pastebin.com/7aECLjUS

3. Double check that both files have the correct filesystem permissions.

4. Clear the cache in the Concrete5 dashboard.

5. Enjoy.


It took us LESS THAN FIFTEEN MINUTES to find and create this solution OF OUR OWN ACCORD. Comparatively we tried FOR ALMOST THREE MONTHS to convince c5hub to provide any solution to this problem, and yet they continued to refuse to provide any help whatsoever apart from outlining why the problem exists.

We will not be seeking a refund because we frankly still need this theme, however we will know going forward that c5hub provides ABSOLUTELY, POSITIVELY, ZERO SUPPORT FOR THEIR CODE WHATSOEVER.

Considering how feature rich and functional fundamental is, it is flabbergasting that they would refuse such rudimentary support of their own product on a problem that was so easily solved.

Reader, please take into consideration that while fundamental is awesome, c5hub's support is probably going to be along the lines of what has happened here. I hope they get their act together, because this is a joke. It is the kind of support an amateur would provide.

I hope that this release helps solve problems in the future.
c5hub replied on at Permalink Reply
c5hub
That's a question for Microsoft.
admin replied on at Permalink Reply
Attention: Since there has been no activity on this issue for two weeks, this issue has been automatically archived.

To re-open this issue, reply to this message.
admin replied on at Permalink Reply
Attention: Since there has been no activity on this issue for two weeks, this issue has been automatically archived.

To re-open this issue, reply to this message.
admin replied on at Permalink Reply
Attention: Since there has been no activity on this issue for two weeks, this issue has been automatically archived.

To re-open this issue, reply to this message.

concrete5 Environment Information

# concrete5 Version
Core Version - 5.7.5.9
Version Installed - 5.7.5.9
Database Version - 20160615000000

# concrete5 Packages
Community CKEditor (0.9.0), Fundamental (3.0.6), Styled Maps (1.2.3).

# concrete5 Overrides
languages/ja_JP/LC_MESSAGES/messages.mo, languages/ja_JP/LC_MESSAGES, languages/ja_JP, languages/el_GR/LC_MESSAGES/messages.mo, languages/el_GR/LC_MESSAGES, languages/el_GR, languages/ru_RU/LC_MESSAGES/messages.mo, languages/ru_RU/LC_MESSAGES, languages/ru_RU, languages/it_IT/LC_MESSAGES/messages.mo, languages/it_IT/LC_MESSAGES, languages/it_IT, languages/es_PY/LC_MESSAGES/messages.mo, languages/es_PY/LC_MESSAGES, languages/es_PY, languages/nl_NL/LC_MESSAGES/messages.mo, languages/nl_NL/LC_MESSAGES, languages/nl_NL, languages/sv_SE/LC_MESSAGES/messages.mo, languages/sv_SE/LC_MESSAGES, languages/sv_SE, languages/cs_CZ/LC_MESSAGES/messages.mo, languages/cs_CZ/LC_MESSAGES, languages/cs_CZ, languages/da_DK/LC_MESSAGES/messages.mo, languages/da_DK/LC_MESSAGES, languages/da_DK, languages/fi_FI/LC_MESSAGES/messages.mo, languages/fi_FI/LC_MESSAGES, languages/fi_FI, languages/pt_BR/LC_MESSAGES/messages.mo, languages/pt_BR/LC_MESSAGES, languages/pt_BR, languages/fr_FR/LC_MESSAGES/messages.mo, languages/fr_FR/LC_MESSAGES, languages/fr_FR, languages/tr_TR/LC_MESSAGES/messages.mo, languages/tr_TR/LC_MESSAGES, languages/tr_TR, languages/de_DE/LC_MESSAGES/messages.mo, languages/de_DE/LC_MESSAGES, languages/de_DE, languages/en_GB/LC_MESSAGES/messages.mo, languages/en_GB/LC_MESSAGES, languages/en_GB, languages/ja_JP/LC_MESSAGES/messages.mo, languages/ja_JP/LC_MESSAGES, languages/ja_JP, languages/el_GR/LC_MESSAGES/messages.mo, languages/el_GR/LC_MESSAGES, languages/el_GR, languages/ru_RU/LC_MESSAGES/messages.mo, languages/ru_RU/LC_MESSAGES, languages/ru_RU, languages/it_IT/LC_MESSAGES/messages.mo, languages/it_IT/LC_MESSAGES, languages/it_IT, languages/es_PY/LC_MESSAGES/messages.mo, languages/es_PY/LC_MESSAGES, languages/es_PY, languages/nl_NL/LC_MESSAGES/messages.mo, languages/nl_NL/LC_MESSAGES, languages/nl_NL, languages/sv_SE/LC_MESSAGES/messages.mo, languages/sv_SE/LC_MESSAGES, languages/sv_SE, languages/cs_CZ/LC_MESSAGES/messages.mo, languages/cs_CZ/LC_MESSAGES, languages/cs_CZ, languages/da_DK/LC_MESSAGES/messages.mo, languages/da_DK/LC_MESSAGES, languages/da_DK, languages/fi_FI/LC_MESSAGES/messages.mo, languages/fi_FI/LC_MESSAGES, languages/fi_FI, languages/pt_BR/LC_MESSAGES/messages.mo, languages/pt_BR/LC_MESSAGES, languages/pt_BR, languages/fr_FR/LC_MESSAGES/messages.mo, languages/fr_FR/LC_MESSAGES, languages/fr_FR, languages/tr_TR/LC_MESSAGES/messages.mo, languages/tr_TR/LC_MESSAGES, languages/tr_TR, languages/de_DE/LC_MESSAGES/messages.mo, languages/de_DE/LC_MESSAGES, languages/de_DE, languages/en_GB/LC_MESSAGES/messages.mo, languages/en_GB/LC_MESSAGES, languages/en_GB

# concrete5 Cache Settings
Block Cache - On
Overrides Cache - On
Full Page Caching - On - In all cases.
Full Page Cache Lifetime - Every 6 hours (default setting).

# Server Software
Apache/2.4.18 (Ubuntu)

# Server API
apache2handler

# PHP Version
7.0.8-0ubuntu0.16.04.3

# PHP Extensions
apache2handler, calendar, Core, ctype, curl, date, dom, exif, fileinfo, filter, ftp, gd, gettext, hash, iconv, imagick, json, libxml, mcrypt, mysqli, mysqlnd, openssl, pcre, PDO, pdo_mysql, Phar, posix, readline, Reflection, session, shmop, SimpleXML, sockets, SPL, standard, sysvmsg, sysvsem, sysvshm, tokenizer, wddx, xml, xmlreader, xmlwriter, xsl, Zend OPcache, zip, zlib.

# PHP Settings
max_execution_time - 60
log_errors_max_len - 1024
max_file_uploads - 20
max_input_nesting_level - 64
max_input_time - 60
max_input_vars - 1000
memory_limit - 128M
post_max_size - 20M
sql.safe_mode - Off
upload_max_filesize - 20M
mysqli.max_links - Unlimited
mysqli.max_persistent - Unlimited
pcre.backtrack_limit - 1000000
pcre.recursion_limit - 100000
session.cache_limiter - <i>no value</i>
session.gc_maxlifetime - 1440
opcache.max_accelerated_files - 2000
opcache.max_file_size - 0
opcache.max_wasted_percentage - 5

Browser User-Agent String

Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36

Hide Post Content

This will replace the post content with the message: "Content has been removed by an Administrator"

Hide Content

Request Refund

You may not request a refund that is not currently owned by you.