More On ASP.NET Validators And Validation Summary Rendering of Properties

Paulo Morgado — Mon, 23 Jun 2008 00:47:00 GMT

On previous posts [^][^] I mentioned the size of ASP.NET validators and validation summary rendering and the fact that expando attributes are being used to add properties. Mohamed also mentions this issue.

Besides the fact that custom attributes aren't XHTML conformant, Firefox differs from Internet Explorer in the way it handles these attributes.

On Internet Explorer, these attributes are converted in string properties of the HTML element. On Firefox, on the other hand, these attributes are only accessible through the attributes collection.

I wonder why I don’t like client-side JavaScript development.

Internet Explorer vs. FireFox

Paulo Morgado — Sun, 25 May 2008 22:32:54 GMT

Until recent I had never used FireFox (FF) because Internet Explorer (IE) was good enough for me.

I don't do much web page development and because I own licenses for Visual Studio (VS), HTTPWatch and IEWatch (tried the Internet Explorer Developer Toolbar but it keeps bowing up and killing IE and I've seen Nikhil Kothari's Web Development Helper installed and doesn't work well when non US English characters are displayed) I never needed anything else.

Over the years I've seen all the campaigning against IE and promoting FF as a better, more standards compliant, more secure and what else.

A few days back I had to do some work with ASP.NET validation summary and validators and needed to check if it worked on FF.

Talk about disappointment:

FireBug is by far no better than the tools I've been using.
FF needs its own proxy configurations - For me, any application running on Windows that needs its own proxy settings it's just a badly developed application.
(I'm sure I'd find much more if I used it.)

IE isn't a good developer tool yet (not even in IE8 at this time [^]) and it should have been for a long time. Or, at least, VS should have better support HTML and CSS debugging.

But, on the other hand, Windows Internet Explorer is just another application built on top of the Web Browser Control[^] (which is part of the IE installation, but can be used by itself). You can build any Windows application that uses a Web Browser Control (I've built more than one). Looks like the same is not as simple with FF [^].

I don't intend to start a web browser war. I just wanted to state my disappointment. I guess FF fans set my expectation too high.

Paulo Morgado : FireFox

More On ASP.NET Validators And Validation Summary Rendering of Properties

Internet Explorer vs. FireFox