Text box inside a Form tag not firing on Go button click in IOS devices

Question

0.00/5 (No votes)

See more:

I have a textbox inside a form tag for implementing site search, My problem after entering text in textbox and On clicking go button in android devices page redirection occures and search result is displayed, but in IOS devices postback not occuring My code is shown below

XML

<form id="search-wrap" class="ezsearch-summary" method="get" action="/ezSearch" target="_blank">

                        <input id="Text1" class="search-input" name="q" type="text" value="" autocomplete="off"/>
                    </form>

Posted 19-Jun-15 1:09am

Prasad_NC

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Ben J. Boyle · Answer 1 · 2015-06-19T03:28:00

Not sure if this is your exact problem but there's a bug somewhere between MS and Apple – when they updated Safari on iOS8 they bumped the version to be Webkit 600, but the code in .NET that’s looking for the browser capabilities screws up and only looks at the first two numbers, so it’s seeing “Webkit 60” instead. The Ajax controls therefore don’t think the browser supports the callbacks and falls back to not using it.

Fix is relatively simple – we need to override the browser capabilities in the web.config – add this to System.Web

XML

<browsercaps>
      <filter>
            <case match="AppleWebKit">
                  EcmaScriptVersion = 1.5
                  supportsCallback = true
            </case>
      </filter>
</browsercaps>

This isn't the only solution, but was the most expedient for us when we encountered a similar problem earlier this year.

References: http://www.brillianceweb.com/blog/article/69/aspnet-20-misidentifies-safari-71-on-ios-and-os-x#sthash.0FuAyobK.dpbs