Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Web Development
  3. ASP.NET
  4. Required Field Validator

Required Field Validator

Scheduled Pinned Locked Moved ASP.NET
helptutorial
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • K Offline
    K Offline
    Kushi Bobby
    wrote on last edited by
    #1

    Hi all, Am using editor and multiline textbox.user selects one of it by using radio button.I used 2 required field validators,to validate those 2 controls. Its all fine upto here.In the button click event,in Internet explorer its working fine by displaying appropriate error message, but in mozilla it is showing two error messages at a time. I hard coded these validators visibility to false in the appropriate radio button selected value loop. Pls guide me any other way to forward Have a Nice Day Dudes

    I 1 Reply Last reply
    0
    • K Kushi Bobby

      Hi all, Am using editor and multiline textbox.user selects one of it by using radio button.I used 2 required field validators,to validate those 2 controls. Its all fine upto here.In the button click event,in Internet explorer its working fine by displaying appropriate error message, but in mozilla it is showing two error messages at a time. I hard coded these validators visibility to false in the appropriate radio button selected value loop. Pls guide me any other way to forward Have a Nice Day Dudes

      I Offline
      I Offline
      icestatue
      wrote on last edited by
      #2

      All I have to say is what the F**K was microsoft thinking when they made the textbox component this way. Microsoft left no easy way to trap the error code coming off a detected client side script attack. It makes no sense that there is no event to capture when a detected validation has failed. The work arounds to make something as simple as string x = Textbox.Text; is rediculous. If you work at Microsoft and you read this all I have to say is EAT MY ASS!

      nothing

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups