Skip to main content

How to disable validation for a submit button

By
Pornim de la o aplicate MVC 3 pe care avem o forma cu mai multe controale de tip input-submit. Se doreste ca unul sau mai multe butoane care fac submit sa nu facă și validarea modelului client-side.
<form ... >
    ....
    <input id="bSave" type="submit" value="Save" />
    <input id="bAddToy" type="submit" value="Add toy" />
</form>
O solutie care pare la indemana este ca la al doilea buton din exemplu sa fie transformat într-un link (ancora). Din CSS poate sa fie făcut sa arate exact ca un buton de input iar la click poate sa apeleze un jQuery care apelează acțiunea dorita făcînd submit și la model.
O a doua soluție găsita, care mi s-a părut extrem de simpla și care rezolva aceasta problema este adăugarea class="cancel" la butonul de input la care dorim sa nu facem validarea:
<input id="bAddToy" type="submit" value="Add toy" class="cancel" />
Voi ce propuneri aveți?
Labels:

Comments

  1. TudorSeptember 21, 2011 at 9:11 PM

    Pentru ultimele versiuni de browsere care suporta HTML5, pe unele din ele, merge atributul 'formnovalidate':
    http://wufoo.com/html5/attributes/12-formnovalidate.html
    si care se refera la atributele de validare introduse in HTML5..

    Din pacate multi useri nu au inca ultimele versiuni, asa ca probabil ar trebui un mecanism de fallback la validarea clasica folosind JS daca validarea din HTML5 nu e suportata ..

    ReplyDelete

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

By
After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(
Post a Comment
Read more

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

By
Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see
8 comments
Read more

Navigating Cloud Strategy after Azure Central US Region Outage

By
 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too
Post a Comment
Read more