Databases
StackOverflow2013
Postsdbo
POWhat might cause Google chrome to not render ASP.Net validators where Firefox does?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhat might cause Google chrome to not render ASP.Net validators where Firefox does?
    primarykey
    data
    text
    <p>A registration page in a site I'm working on collects information on 2 named contacts, who are <strong>required</strong> to have email addresses and telephone numbers which do not overlap with one another.</p> <p>I use several <strong>requiredfieldvalidators</strong>, <strong>regularexpressionvalidators</strong>, <strong>CompareValidators</strong> and some <strong>customvalidators</strong>.</p> <p><strong>STAGING-> Firefox</strong>: When I view this page using Firefox, all is fine. </p> <p><strong>Staging-> Chrome</strong>: When I view it using Chrome anything to do with validators is missing from the HTML source of the rendered page. The javascript and tags pertaining to said validation is completely absent from these pages.</p> <p><strong>Local -> Chrome</strong>: All fine again</p> <p>So what am I doing wrong?</p> <hr> <p><strong>Updates</strong>:</p> <ul> <li>Staging machine has .Net 3.5 SP1. Local machine has 3.5 SP1 and 4.0 </li> <li>%SystemRoot%\Microsoft.NET\Framework\ <strong>v2.0.50727</strong>\CONFIG\Browsers folder is same on both machines.</li> <li>Tried removing browser files from %SystemRoot%\Microsoft.NET\Framework\ <strong>v4.0.30319</strong>\Config\Browsers on local dev machine. No effect. Validators still work when referencing local Server</li> </ul> <hr> <p><strong>SOLVED:</strong> Full marks to Will because without his help (below) I would have spent hours at this.</p> <p>Technically the incorrect browser sniffing was down to some rouge browsercaps info in one of the web.configs in the solution. the differences between dev and deploy came about because web.config differs in these scenarios</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USRory Becker
    1. USRory Becker
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhat might cause Google chrome to not render ASP.Net validators where Firefox does?
      1. USRory Becker
      1. VTFavorite
    2. VO
      singulars
      1. POWhat might cause Google chrome to not render ASP.Net validators where Firefox does?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POWhat might cause Google chrome to not render ASP.Net validators where Firefox does?
      1. This table or related slice is empty.
      1. VTUpMod
    1. CODo you have JavaScript enabled in the Staging Chrome?
      singulars
      1. POWhat might cause Google chrome to not render ASP.Net validators where Firefox does?
      1. USMichael Stum
    2. COI don't think it's anything you are doing; the framework itself makes some determinations about validation support on the client-side... question: does the validation work server-side?
      singulars
      1. POWhat might cause Google chrome to not render ASP.Net validators where Firefox does?
      1. USBrian Mains
    3. CO@Michael Same version of chrome works locally, but fails against the staging site.
      singulars
      1. POWhat might cause Google chrome to not render ASP.Net validators where Firefox does?
      1. USRory Becker
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload