Form 2.0 fields don't appear on some instances of IE10 | Community
Skip to main content
March 3, 2014
Question

Form 2.0 fields don't appear on some instances of IE10

  • March 3, 2014
  • 10 replies
  • 4240 views
Hi,

I was wondering if anyone is having troubles with the new forms on IE10? Some people in my company can see the forms and others can't even after clearing their cache.

Is anyone else having the same troubles?

Bec
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

10 replies

Dave_Roberts
New Participant
August 19, 2020

Hey Bec,

I don't have a solution for this, but I also have a few reasons that I don't worry about optimizing for IE10 with most stuff.

 

I did a quick Google search for "IE 10 support" and it looks like support for this browser ended at the beginning of the year. I understand that this doesn't exactly solve the issue of folks using an older browser that's no longer support, but it may not be worth trying to support retired versions of browsers, especially IE. 

 

Here's a link to a short list of 628 reasons not to use IE10 because of security issues that arise (and do not get resolved) because of the lack of support from Microsoft: https://www.cvedetails.com/vulnerability-list/vendor_id-26/product_id-9900/version_id-138705/Microsoft-Internet-Explorer-10.html

 

As far as I'm aware the "modern standard" for IE got accelerated recently and Edge/11 is really the furthest you should have go "back in time" with MS browsers. It looks like 11 and the 1st version of Edge are already slated to roll out next year, here's a link to an article w/ more info: https://redmondmag.com/articles/2020/08/17/end-of-support-ie11-and-edgehtml.aspx

 

It might be worth looking into running a more secure browser and updating to something more modern where you wouldn't see these types of display errors or be faced with this caliber of security issues. It looks like in the last year, if you rounded up ALL the versions of IE (which includes 11, but not Edge) you'd end up with about 1.7% of the Global Market (https://gs.statcounter.com/browser-market-share#monthly-201907-202007-bar) -- said another way, not too many folks are using IE at all, let alone an unsupported version, so it's not very likely that you'll encounter this problem in the wild (in my experience anyway). Here's a look at the chart on the link above:

 

 

For what it's worth, Marketo also does not support IE11, they've made the cutoff at Edge already: https://docs.marketo.com/display/public/DOCS/Supported+Browsers so this might be something worth looking into getting updated if you're using an older browser internally.

 

Hope this helps in some ways,

Dave

SanfordWhiteman
New Participant
August 20, 2020

If 2% of your leads can't fill out a form, or it looks so horrendously ugly, that's unacceptable. Not having your site show at all in IE because you used unsupported JS to manage your layout — something I've seen in the wild — is just plain amateurish.

 

Obviously small visual differences may be OK, though.

 

Bear in mind that browser share varies greatly by industry. If you have a B2B enterprise software company, then anyone hitting your site from a Windows 2012-2016 server with no 3rd-party software should be assumed to be using IE.

Dave_Roberts
New Participant
August 21, 2020

Sure, you wouldn't want to exclude IE users, especially if your target audience is full of IE users, that's pretty straight-forward, but I don't think the 2% (globallly) that are using IE are the issue here, it's more a matter of a fraction of that percent using an OUTDATED version of IE that sounds like an issue here. 

 

Would you recommend optimizing for retired versions of browsers like IE10 and earlier? I've always kinda thought that there's a "cutoff" point in terms of producing backward-compatible code and was under the impression that IE10 and earlier were before that point -- mostly because Microsoft isn't supporting those versions of the browser which means anyone using them is at an ever-increasing risk of security and performance issues as time goes on. I get that you can't "enforce" that orgs use good software, but where do you think the line should be drawn in terms of dealing with antiquated browsers or ESPs? 

New Participant
August 19, 2020

I found the line-height and text size was adjusted on my landing page. I had success using this code:

 

@media all and (-ms-high-contrast: none), (-ms-high-contrast: active) { .mktoForm input[type=date], .mktoForm input[type=email], .mktoForm input[type=number], .mktoForm input[type=tel], .mktoForm input[type=text], .mktoForm input[type=url], .mktoForm select.mktoField, .mktoForm input[type=date], .mktoForm input[type=email], .mktoForm input[type=number], .mktoForm input[type=tel], .mktoForm input[type=text], .mktoForm input[type=url], .mktoForm select.mktoField { font-size: 1.3em!important; line-height:0.5em!important } }

 

March 18, 2014
Btw - Bec, if you could provide a link to the form in question, that'd be very helpful.

Thanks!
March 18, 2014
Hey Bec,

I'll try to track down the case you opened on this.  There was some confusion around IE support that might have caused some runarounds on a few support cases.

If you haven't heard back on this yet, I'll circle back on the thread when I have more info.

Thanks,

Jason
Vlada_Prasolova
New Participant
March 6, 2014
same issues with me - but in IE 9
March 5, 2014
Hi Cheryl,

Are you able to let me know if there are any solutions to this issue?

Thanks,
Bec
March 4, 2014
Thanks Dan, that was my thoughts too as I can replicate the issue when I turn mine to compatibility mode.

Image demonstration below:



Dan_Stevens_
New Participant
March 4, 2014
We've had issues when using Form 2.0 when IE10/IE11 are running in compatibility mode.  Once disabled, the forms behaved as expected.  Obviously this isn't something you can ask your visitors to do, but it may help to identify what is causing this issue.
March 4, 2014
Hi Cheryl,

Thanks for the response.

I have received a response from support however, the issues is that it isn't working on a non-marketo page and the test they ran to verify if it worked was on a marketo landing page therefore comparing apples with oranges. The response was that nothing was wrong and that this is not an issue, but since some users cannot register or fill out a form it is an issue. They mentioned that others have not complained, though just because others haven't picked it up yet as the forms are still new, it doesn't mean there isn't an issues. I spoke to an internal developer and this is what they think the issue is: 

When marketo forms are being embedded they place the labels inside input elements using the placeholder attribute.  For example:
<input type="text" placeholder="First Name" ... />
This is known to have issues with ie9, and so labels are not appearing for IE9 users:

http://stackoverflow.com/questions/6366021/placeholder-in-ie9


Any help would be greatly appreciated.

Thanks,
Bec

March 4, 2014
Hi Bec,

Have you given support a call about this issue?

Thanks,
Cheryl