Dons't work in IE

Hello all,

I'm developing an application that is working very fine in firefox. But in IE it doesn´t even pass the first step, the login authorization...

I really don't understand. In firefox I don't have any problem...


Please help me.
:)

have you stepped through your code when you try and run it in ie?

What application. Just a HTML page or CSS. What version of IE you used.

vbdotnetboy:

Quote:

---

have you stepped through your code when you try and run it in ie?

---

No, In my pc I only debug the application in Firefox



eranga262154:

Quote:

---

What application. Just a HTML page or CSS. What version of IE you used.

---

I'm devoloping an application for a customer area for a web site.

I don't use CSS. It's a simple html page and I use IE version is IE6

.......

CSS=Cascading Style Sheet

It's the "correct" way of applying different styles to your page. IE6 is a browser. Nothing to do with CSS.

What OS are you using? What version of IE? What exactly is on your login page? Does it have any 'fanciful' javascript validation checks? Show the HTML source when the page is rendered.

Quote:

---

Originally Posted by timeshifter

.......

CSS=Cascading Style Sheet

It's the "correct" way of applying different styles to your page. IE6 is a browser. Nothing to do with CSS.

---

You are correct.

But what I'm looking is that, some some CSS tags are not supported on few versions of IE and FF.

The tags are equally supported in both. The difference is in the usage. If you have nested tags, IE and Fx may not read them the same way. This is true of HTML in general. If you have extra spaces in your HTML code, Fx will just ignore them, but IE will try to render them as literal spaces, which tends to make things look bad. CSS is CSS. Fx and IE are the culprits.

Just for the record, almost ANY site can be made to look identical in IE and Fx. It just takes some fiddling and very precise CSS.

Quote:

---

Originally Posted by achor

No, In my pc I only debug the application in Firefox

---

well try debugging it in ie and see what happens... if it's a matter of you not liking IE that's no reason for not testing/debugging it in ie. when i write web apps i test it in every browser possible, fx, ie, netscape, and opera to name a few.

The majority of the world uses Fx or IE, so those are my main testers. Lately, though, Fx has been moving pretty slowly... it's kinda strange...

Quote:

---

Originally Posted by timeshifter

The tags are equally supported in both. The difference is in the usage. If you have nested tags, IE and Fx may not read them the same way. This is true of HTML in general. If you have extra spaces in your HTML code, Fx will just ignore them, but IE will try to render them as literal spaces, which tends to make things look bad. CSS is CSS. Fx and IE are the culprits.

Just for the record, almost ANY site can be made to look identical in IE and Fx. It just takes some fiddling and very precise CSS.

---

You say that, supportability depends on the way of coding, is it?

Not supportability. The ability for the same site to look identical in every browser. Spacer images are a good start... style tags in <td> and <tr> tags aren't such a good start.

Styling does not explain the inability to login on IE.

I was simply pointing out a tactical difference between the two.

As for the login, have you checked IE's settings to make sure there's no security crap getting in the way?

Quote:

---

Originally Posted by timeshifter

have you checked IE's settings to make sure there's no security crap getting in the way?

---

Is there FF have such security restrictions.

I forgot to answer here what was the problem...

I didn't found the exact problem but i redesign the page and it's working.

The first page had much validation errors.

Anyway thank you all

Tally those modifications with your old page. You may find where the error is.

I don't believe this...
Now it's working in IE and it isn't in firefox...

GGRRRRRR!!!!

Anyway, congrats..

firefox does have BUGS with javascript event's - I have come accors this when adding onMouseDown="someJavaScriptFunction()" to a control or button.

Basically because asp.net adds the javascript function __doPostBack onclick etc event Firefox can fire both events insetead of waiting for the first events function to finish which might stop the second event(__doPostBack) to fire.

So if you have javascript validation firefox might be letting it through by firing both event anyway.

I have not had any problem like this with the standard validation controls though

That lends further credence to the thought that one ought to have both client and server side validation for a page. You can never be too sure.

Quote:

---

Originally Posted by mendhak

That lends further credence to the thought that one ought to have both client and server side validation for a page. You can never be too sure.

---

Even on over own server. I mean at that time I can do anything on both server side as well as client side. ???

Yes, because the page itself can be bypassed by sending a simple request in get/post format to the target page. The target page will faithfully process it, and will assume that the client (in thise case no client) will have validated it.