Menu
▾
▴
[Anthem.NET-users] RE: anthem-dot-net-users digest, Vol 1 #172 - 3 msgs
|
From: Rice, P. <Pau...@co...> - 2006-03-21 19:28:42
|
See http://forums.anthemdotnet.com/forums/viewtopic.php?t=3D63 -----Original Message----- From: ant...@li... [mailto:ant...@li...] On Behalf Of ant...@li... Sent: Tuesday, March 21, 2006 11:40 AM To: ant...@li... Subject: anthem-dot-net-users digest, Vol 1 #172 - 3 msgs Send anthem-dot-net-users mailing list submissions to ant...@li... To subscribe or unsubscribe via the World Wide Web, visit =09 https://lists.sourceforge.net/lists/listinfo/anthem-dot-net-users or, via email, send a message with subject or body 'help' to ant...@li... You can reach the person managing the list at ant...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of anthem-dot-net-users digest..." Today's Topics: 1. Problem with focus.... (Mike Weichert) 2. RE: Anthem generated code and HTML Tidy (Brian @ AJP) 3. RE: Anthem generated code and HTML Tidy (John Murphy) --__--__-- Message: 1 Date: Tue, 21 Mar 2006 12:17:57 -0500 From: "Mike Weichert" <mwe...@gm...> To: ant...@li... Subject: [Anthem.NET-users] Problem with focus.... Hi guys, I'm having some problems with using tab character to change focus from one control to another. I have the tabindex properties set as they should. If I tab through each control (textbox) without entering a value, they work as expected. However, if I enter a value into a textbox and then tab, the control looses focus. The AutoPostBack property of all the controls is set to false, and the AutoUpdateAfterCallBack property is set to true. This is using the latest .NET 1.1 version. Thanks, Mike -- // This is my personal e-mail account // that I use for communication only. // Please send any e-mails with attachments // to mwe...@wi.... --__--__-- Message: 2 Reply-To: <br...@aj...> From: "Brian @ AJP" <br...@aj...> To: "'Manu Temmerman-Uyttenbroeck'" <man...@gm...> Cc: <ant...@li...> Subject: RE: [Anthem.NET-users] Anthem generated code and HTML Tidy Date: Tue, 21 Mar 2006 11:52:55 -0000 Organization: AJP Interactive - Part of AJP Consultants Ltd This is a multi-part message in MIME format. ------=3D_NextPart_000_002A_01C64CDD.FF41BEE0 Content-Type: text/plain; charset=3D"us-ascii" Content-Transfer-Encoding: 7bit I began to mind when I'd spent many weeks in discussion and testing with my Indian subcontractors to get a large web application to pass the W3C validators so that that site could carry the "XHTML" and "CSS" and "WAI-AAA" badges, only to find that as soon as I added Anthem controls to a simple page I lost all my validation ticks. =20 I found the solution and made the suggestion but when it was pointed out that the integral ASP.Net hidden fields all use the same invalid identifiers I decided to drop my campaign. I don't know why the W3C validators and Tidy let the Microsoft "__*" identifiers through and object to others, but that's another issue. =20 Now on revisiting it, and having seen some press about Microsoft's stated intention to make IE7 standards compliant, I'm thinking that they could easily issue a patch to the framework to replace all their double underscores and generate valid IDs for the __EVENTTARGET and __EVENTARGUMENT and __VIEWSTATE hidden fields. If they do that, and Anthem continues to use the invalid double underscores, then Anthem could get the blame for lots of invalid HTML. =20 I'll pick up the latest snapshot today, and locate the required changes and email you the relevant lines to change, if you don't mind. I tried CVS and couldn't get my head around it :-/ =20 Per my original suggestion, I propose replacing the invalid "__*" with a valid "AJAX_*" =20 That would clearly identify to any human reader trying to step through or debug the code that this element is peculiar to an AJAX addition to the page. =20 I'm equally happy to make it Anthem_ to give Jason some recognition for his fantastic development, but I wondered if that would be as clear to anyone coming later to review the generated code. Would they necessarily know that Anthem was an implementation of AJAX? =20 I'm a firm believer also in Alzheimer's law of programming: "After 3 weeks you forget why you used that identifier or construct, so your names and comments need to be very, very clear." =20 So, unless anyone objects loudly (and quickly), I'm going to recommend changing the invalid "__" to a valid "AJAX_". =20 Code will follow. =20 =20 Brian Lowe, AJP Interactive w: www.ajpi.co.uk <http://www.ajpi.co.uk/> e: br...@aj... f: 07075 167630 =20 _____ =20 From: ant...@li... [mailto:ant...@li...] On Behalf Of Manu Temmerman-Uyttenbroeck Sent: 21 March 2006 09:24 To: br...@aj... Cc: Roberto; ant...@li... Subject: Re: [Anthem.NET-users] Anthem generated code and HTML Tidy I personally don't really mind this invalid html. But if you really do mind, I don't mind changing it :) Could you therefore maybe submit a patch on sourceforge? It will save me time to do it. Or send me a mail with what I have to change where. Pls download first the latest snapshot so we are using the same code... =20 Could you do this for me? =20 Manu. =20 On 3/21/06, Manu Temmerman-Uyttenbroeck <man...@gm...> wrote:=20 Ok Brian. If I'll find the change I'll check in the change tonight. I hope it won't break any code though...=20 Hmm on second thought... I won't check it in. Could you maybe make some testing for this? If you can assure me that it won't break anything, then I'll check it in. =20 Manu. =20 On 3/21/06, Brian @ AJP <br...@aj...> wrote:=20 If you follow the W3C recommendation for HTML and XHTML you will find that an identifier must begin with a letter, not a number or underscore, so the ASP.Net 'standard' hidden fields do use invalid HTML, and so you can expect all ASP.Net pages to fail this validation test. (I don't know why Tidy doesn't highlight "__EVENTTARGET" and "__EVENTARGUMENT" - maybe there's a switch in it that turns a blind eye to it because it knows it's Microsoft.)=20 =20 I suggested a fix for the anthem-generated element IDs by simply changing a couple of lines of code in manager.cs, but didn't press it because fixing it seemed pointless in light of the major Microsoft invalidations.=20 =20 Now I'm thinking it should be fixed while we know about it and how to fix it. The alternative is to carry on with known invalid generated IDs. If Microsoft (newly committed to 'compatibility' and 'standards') issues a patch to the ASP.Net framework that fixes their invalid IDs, then Anthem would be left out in the cold and would be to blame for invalidating otherwise valid mark-up. =20 What does the team think?=20 =20 =20 =20 Brian Lowe, AJP Interactive w: www.ajpi.co.uk <http://www.ajpi.co.uk/> e: br...@aj... f: 07075 167630 =20 _____ =20 From: ant...@li... <mailto:ant...@li...> [mailto:ant...@li...] On Behalf Of Manu Temmerman-Uyttenbroeck Sent: 21 March 2006 06:32 To: Roberto Cc: ant...@li... Subject: Re: [Anthem.NET-users] Anthem generated code and HTML Tidy =20 Brian Lowe asked the same question 11th of February. This was my answer then: =20 Your pages are invalid because of id attributes that start with "__", correct? If so, then I'm a little bit confused. In the url you pasted is that the name and id attributes can only start with letters. Every generated aspx page contains following html elements: <input type=3D"hidden" name=3D"__EVENTTARGET" id=3D"__EVENTTARGET" = value=3D"" /> <input type=3D"hidden" name=3D"__EVENTARGUMENT" id=3D"__EVENTARGUMENT" value=3D"" /> Does this mean that every generated aspx page is invalid? If so, then I would putting 'fixing' this in Anthem on the bottom of the priority list. If I'm wrong, then sorry... Brian? Could you pls let me know your=20 comment on this? So I have the same question again. The 2 hidden fields generated by asp are also seen as invalid? =20 Manu. =20 On 3/21/06, Roberto <ro...@lt...> wrote:=20 Hi Guys =20 I was using the latest builds of Anthem.NET, but I suspect the error has been there for a while... It seems u can't validate a page using HTML tidy with Anthem controls since the control names generate ID's such as ID=3D"__Button1__" which I think is not allowed in the spec. Below is an example of the like that gives me a warning in HTML tidy even though it's not an error it would be cool if it could be fixed.=20 =20 Does anyone have a fix for this? <span id=3D"__Button1__"><input type=3D"submit" name =3D"Button1" value=3D"Start Ajax" onclick=3D"AnthemButton_Click(this,'Button1',true,'Getting info',false,Button1_PreCallBack,Button1_PostCallBack,null,true,true);ret urn false;"=20 id=3D"Button1" /></span><span id=3D"ProgressSection" style=3D"visibility:hidden;" ><img src=3D"images/indicator.gif" border=3D"0" style=3D"vertical-align:middle; padding-left:5px; padding-right:2px;"=20 alt=3D"Progress Icon" />Please wait while retrieving = information...</span> line 36 column 9 - Warning: <span> ID "__Button1__" uses XML ID synta =20 Regards Rob No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.2.6/286 - Release Date: 20/03/2006 ------=3D_NextPart_000_002A_01C64CDD.FF41BEE0 Content-Type: text/html; charset=3D"us-ascii" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3D3DContent-Type content=3D3D"text/html; =3D charset=3D3Dus-ascii"> <META content=3D3D"MSHTML 6.00.2900.2802" name=3D3DGENERATOR></HEAD> <BODY> <DIV dir=3D3Dltr align=3D3Dleft><SPAN = class=3D3D656311511-21032006><FONT=3D20 face=3D3D"Comic Sans MS" color=3D3D#000080 size=3D3D2>I began to mind = when I'd =3D spent many=3D20 weeks in discussion and testing with my Indian subcontractors to get a = =3D large web=3D20 application to pass the W3C validators so that that site could carry the =3D "XHTML"=3D20 and "CSS" and "WAI-AAA" badges, only to find that as soon as I added =3D Anthem=3D20 controls to a simple page I lost all my validation =3D ticks.</FONT></SPAN></DIV> <DIV dir=3D3Dltr align=3D3Dleft><SPAN = class=3D3D656311511-21032006><FONT=3D20 face=3D3D"Comic Sans MS" color=3D3D#000080 =3D size=3D3D2></FONT></SPAN> </DIV> <DIV dir=3D3Dltr align=3D3Dleft><SPAN = class=3D3D656311511-21032006><FONT=3D20 face=3D3D"Comic Sans MS" color=3D3D#000080 size=3D3D2>I found the = solution and =3D made the=3D20 suggestion but when it was pointed out that the integral ASP.Net hidden =3D fields=3D20 all use the same invalid identifiers I decided to drop my campaign. I = =3D don't know=3D20 why the W3C validators and Tidy let the Microsoft "__*" identifiers =3D through and=3D20 object to others, but that's another issue.</FONT></SPAN></DIV> <DIV dir=3D3Dltr align=3D3Dleft><SPAN = class=3D3D656311511-21032006><FONT=3D20 face=3D3D"Comic Sans MS" color=3D3D#000080 =3D size=3D3D2></FONT></SPAN> </DIV> <DIV dir=3D3Dltr align=3D3Dleft><SPAN = class=3D3D656311511-21032006><FONT=3D20 face=3D3D"Comic Sans MS" color=3D3D#000080 size=3D3D2>Now on revisiting = it, =3D and having seen=3D20 some press about Microsoft's stated intention to make IE7 standards =3D compliant,=3D20 I'm thinking that they could easily issue a patch to the framework to = =3D replace=3D20 all their double underscores and generate valid IDs for the =3D __EVENTTARGET and=3D20 __EVENTARGUMENT and __VIEWSTATE hidden fields. If they do that, and =3D Anthem=3D20 continues to use the invalid double underscores, then Anthem could get = =3D the blame=3D20 for lots of invalid HTML.</FONT></SPAN></DIV> <DIV dir=3D3Dltr align=3D3Dleft><SPAN = class=3D3D656311511-21032006><FONT=3D20 face=3D3D"Comic Sans MS" color=3D3D#000080 =3D size=3D3D2></FONT></SPAN> </DIV> <DIV dir=3D3Dltr align=3D3Dleft><SPAN = class=3D3D656311511-21032006><FONT=3D20 face=3D3D"Comic Sans MS" color=3D3D#000080 size=3D3D2>I'll pick up the = latest =3D snapshot=3D20 today, and locate the required changes and email you the relevant lines =3D to=3D20 change, if you don't mind. I tried CVS and couldn't get my head around = =3D it=3D20 :-/</FONT></SPAN></DIV> <DIV dir=3D3Dltr align=3D3Dleft><SPAN = class=3D3D656311511-21032006><FONT=3D20 face=3D3D"Comic Sans MS" color=3D3D#000080 =3D size=3D3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D3D656311511-21032006><FONT face=3D3D"Comic Sans MS" = =3D color=3D3D#000080=3D20 size=3D3D2>Per my original suggestion, I propose replacing the invalid = =3D "__*" with a=3D20 valid "AJAX_*"</FONT></SPAN></DIV> <DIV><SPAN class=3D3D656311511-21032006><FONT face=3D3D"Comic Sans MS" = =3D color=3D3D#000080=3D20 size=3D3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D3D656311511-21032006><FONT face=3D3D"Comic Sans MS" = =3D color=3D3D#000080=3D20 size=3D3D2>That would clearly identify to any human reader trying to = step =3D through or=3D20 debug the code that this element is peculiar to an AJAX addition to the=3D20 page.</FONT></SPAN></DIV> <DIV><SPAN class=3D3D656311511-21032006><FONT face=3D3D"Comic Sans MS" = =3D color=3D3D#000080=3D20 size=3D3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D3D656311511-21032006><FONT face=3D3D"Comic Sans MS" = =3D color=3D3D#000080=3D20 size=3D3D2>I'm equally happy to make it Anthem_ to give Jason some =3D recognition for=3D20 his fantastic development, but I wondered if that would be as clear to = =3D anyone=3D20 coming later to review the generated code. Would they necessarily know = =3D that=3D20 Anthem was an implementation of AJAX?</FONT></SPAN></DIV> <DIV><SPAN class=3D3D656311511-21032006><FONT face=3D3D"Comic Sans MS" = =3D color=3D3D#000080=3D20 size=3D3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D3D656311511-21032006><FONT face=3D3D"Comic Sans MS" = =3D color=3D3D#000080=3D20 size=3D3D2>I'm a firm believer also in Alzheimer's law of programming: = =3D "After 3=3D20 weeks you forget why you used that identifier or construct, so your =3D names and=3D20 comments need to be very, very clear."</FONT></SPAN></DIV> <DIV><SPAN class=3D3D656311511-21032006><FONT face=3D3D"Comic Sans MS" = =3D color=3D3D#000080=3D20 size=3D3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D3D656311511-21032006><FONT face=3D3D"Comic Sans MS" = =3D color=3D3D#000080=3D20 size=3D3D2>So, unless anyone objects loudly (and quickly), I'm going to = =3D recommend=3D20 changing the invalid "__" to a valid "AJAX_".</FONT></SPAN></DIV> <DIV><SPAN class=3D3D656311511-21032006><FONT face=3D3D"Comic Sans MS" = =3D color=3D3D#000080=3D20 size=3D3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D3D656311511-21032006><FONT face=3D3D"Comic Sans MS" = =3D color=3D3D#000080=3D20 size=3D3D2>Code will follow.</FONT></SPAN></DIV> <DIV><SPAN class=3D3D656311511-21032006><FONT face=3D3D"Comic Sans MS" = =3D color=3D3D#000080=3D20 size=3D3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D3D656311511-21032006><FONT face=3D3D"Comic Sans MS" = =3D color=3D3D#000080=3D20 size=3D3D2></FONT></SPAN> </DIV> <DIV align=3D3Dleft> <DIV style=3D3D"WIDTH: 80%; HEIGHT: 1px" align=3D3Dleft><!-- NAME = SECTION =3D --> <MARQUEE id=3D3DMarquee1=3D20 style=3D3D"BORDER-TOP: blue 1px solid; DISPLAY: block; FONT-SIZE: 10pt; = =3D COLOR: #30c; FONT-FAMILY: Trebuchet; HEIGHT: 33px"=3D20 trueSpeed scrollAmount=3D3D1 scrollDelay=3D3D20 direction=3D3Ddown =3D behavior=3D3Dslide loop=3D3D1=3D20 border=3D3D"2"><FONT face=3D3D"Comic Sans MS"><B>Brian Lowe</B>, = AJP=3D20 Interactive<BR></FONT></MARQUEE><!-- JOB TITLE SECTION --> <MARQUEE id=3D3DMarquee2=3D20 style=3D3D"BORDER-RIGHT: 0px; BORDER-TOP: 0px; DISPLAY: block; = FONT-SIZE: =3D 8pt; BORDER-LEFT: 0px; WIDTH: 300px; COLOR: #30c; BORDER-BOTTOM: 0px; = =3D FONT-FAMILY: Trebuchet"=3D20 trueSpeed scrollAmount=3D3D3 scrollDelay=3D3D1 behavior=3D3Dslide = loop=3D3D1 =3D border=3D3D"0"><FONT=3D20 face=3D3D"Comic Sans MS">w: <U><A style=3D3D"COLOR: blue"=3D20 href=3D3D"http://www.ajpi.co.uk/">www.ajpi.co.uk</A></U></FONT></MARQUEE>= < !=3D -- PHONE NUMBER SECTION <marquee id=3D3D"Marquee3" style=3D3D"FONT-SIZE: 10pt; WIDTH: = 300px;" =3D truespeed=3D3D"" scrollamount=3D3D"1" scrolldelay=3D3D"2" = behavior=3D3D"slide" =3D loop=3D3D"1" border=3D3D"0"> <font size=3D3D"1" face=3D3D"Comic Sans MS">m: 07753 205716</font> </marquee> --><!-- EMAIL ADDRESS SECTION --> <MARQUEE id=3D3DMarquee3=3D20 style=3D3D"BORDER-RIGHT: 0px; BORDER-TOP: 0px; DISPLAY: block; = FONT-SIZE: =3D 8pt; BORDER-LEFT: 0px; WIDTH: 300px; COLOR: #30c; BORDER-BOTTOM: 0px; = =3D FONT-FAMILY: Trebuchet"=3D20 trueSpeed scrollAmount=3D3D1 scrollDelay=3D3D1 behavior=3D3Dslide = loop=3D3D1 =3D border=3D3D"0"><FONT=3D20 face=3D3D"Comic Sans MS">e: <U><A style=3D3D"COLOR: blue"=3D20 href=3D3D"mailto:br...@aj...">br...@aj...</A></U></FONT></MARQU= E E=3D > <MARQUEE id=3D3DFAX_NUMBER_SECTION=3D20 style=3D3D"BORDER-RIGHT: 0px; BORDER-TOP: 0px; DISPLAY: block; = FONT-SIZE: =3D 8pt; BORDER-LEFT: 0px; WIDTH: 300px; COLOR: #30c; BORDER-BOTTOM: 0px; = =3D FONT-FAMILY: Trebuchet"=3D20 trueSpeed scrollAmount=3D3D2 scrollDelay=3D3D8 behavior=3D3Dslide = loop=3D3D1 =3D border=3D3D"0"><FONT=3D20 face=3D3D"Comic Sans MS">f: 07075 =3D 167630</FONT></MARQUEE></DIV></DIV><BR><BR> <DIV> </DIV><BR> <BLOCKQUOTE style=3D3D"MARGIN-RIGHT: 0px"> <DIV class=3D3DOutlookMessageHeader lang=3D3Den-us dir=3D3Dltr = align=3D3Dleft> <HR tabIndex=3D3D-1> <FONT face=3D3DTahoma size=3D3D2><B>From:</B>=3D20 ant...@li...=3D20 [mailto:ant...@li...] <B>On Behalf =3D Of=3D20 </B>Manu Temmerman-Uyttenbroeck<BR><B>Sent:</B> 21 March 2006=3D20 09:24<BR><B>To:</B> br...@aj...<BR><B>Cc:</B> Roberto;=3D20 ant...@li...<BR><B>Subject:</B> Re:=3D20 [Anthem.NET-users] Anthem generated code and HTML =3D Tidy<BR></FONT><BR></DIV> <DIV></DIV> <DIV>I personally don't really mind this invalid html. But if you =3D really do=3D20 mind, I don't mind changing it :)</DIV> <DIV>Could you therefore maybe submit a patch on sourceforge? It will =3D save me=3D20 time to do it.</DIV> <DIV>Or send me a mail with what I have to change where. Pls download =3D first=3D20 the latest snapshot so we are using the same code...</DIV> <DIV> </DIV> <DIV>Could you do this for me?</DIV> <DIV> </DIV> <DIV>Manu.<BR><BR> </DIV> <DIV><SPAN class=3D3Dgmail_quote>On 3/21/06, <B =3D class=3D3Dgmail_sendername>Manu=3D20 Temmerman-Uyttenbroeck</B> <<A=3D20 =3D href=3D3D"mailto:man...@gm...">manu.temmermanuytt= e n=3D br...@gm...</A>>=3D20 wrote:</SPAN>=3D20 <BLOCKQUOTE class=3D3Dgmail_quote=3D20 style=3D3D"PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: = =3D #ccc 1px solid"> <DIV style=3D3D"DIRECTION: ltr"> <DIV>Ok Brian. If I'll find the change I'll check in the change =3D tonight. I=3D20 hope it won't break any code though... </DIV> <DIV>Hmm on second thought... I won't check it in. Could you maybe = =3D make some=3D20 testing for this? If you can assure me that it won't break anything, =3D then=3D20 I'll check it in.</DIV></DIV> <DIV style=3D3D"DIRECTION: ltr"><SPAN class=3D3Dsg> <DIV> </DIV> <DIV>Manu.<BR><BR> </DIV></SPAN></DIV> <DIV style=3D3D"DIRECTION: ltr"><SPAN class=3D3De =3D id=3D3Dq_10a1c1c629190bf8_2> <DIV><SPAN class=3D3Dgmail_quote>On 3/21/06, <B =3D class=3D3Dgmail_sendername>Brian @=3D20 AJP</B> <<A onclick=3D3D"return =3D top.js.OpenExtLink(window,event,this)"=3D20 href=3D3D"mailto:br...@aj..." =3D target=3D3D_blank>br...@aj...</A>> wrote:=3D20 </SPAN> <BLOCKQUOTE class=3D3Dgmail_quote=3D20 style=3D3D"PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; = BORDER-LEFT: =3D #ccc 1px solid"> <DIV style=3D3D"DIRECTION: ltr"> <DIV dir=3D3Dltr align=3D3Dleft><SPAN><FONT face=3D3D"Comic Sans = MS" =3D color=3D3D#000080=3D20 size=3D3D2>If you follow the W3C recommendation for HTML and XHTML = =3D you will=3D20 find that an identifier must <U>begin</U> with a letter, not a =3D number or=3D20 underscore, so the ASP.Net 'standard' hidden fields=3D20 <EM><STRONG>do</STRONG></EM> use invalid HTML, and so you can =3D expect=3D20 <STRONG><EM>all</EM></STRONG> ASP.Net pages to fail this =3D validation test.=3D20 (I don't know why Tidy doesn't highlight "__EVENTTARGET" and=3D20 "__EVENTARGUMENT" - maybe there's a switch in it that turns a =3D blind eye to=3D20 it because it knows it's Microsoft.) </FONT></SPAN></DIV> <DIV dir=3D3Dltr align=3D3Dleft><SPAN><FONT face=3D3D"Comic Sans = MS" =3D color=3D3D#000080=3D20 size=3D3D2></FONT></SPAN> </DIV> <DIV dir=3D3Dltr align=3D3Dleft><SPAN><FONT face=3D3D"Comic Sans = MS" =3D color=3D3D#000080=3D20 size=3D3D2>I suggested a fix for the anthem-generated element IDs = by =3D simply=3D20 changing a couple of lines of code in manager.cs, but =3D didn't press it=3D20 because fixing it seemed pointless in light of the major Microsoft =3D invalidations. </FONT></SPAN></DIV> <DIV dir=3D3Dltr align=3D3Dleft><SPAN><FONT face=3D3D"Comic Sans = MS" =3D color=3D3D#000080=3D20 size=3D3D2></FONT></SPAN> </DIV> <DIV dir=3D3Dltr align=3D3Dleft><SPAN><FONT face=3D3D"Comic Sans = MS" =3D color=3D3D#000080=3D20 size=3D3D2>Now I'm thinking it <EM>should</EM> be fixed while we = =3D know about it=3D20 and how to fix it. The alternative is to carry on with known =3D invalid=3D20 generated IDs. If Microsoft (newly committed to 'compatibility' = =3D and=3D20 'standards') issues a patch to the ASP.Net framework that fixes = =3D their=3D20 invalid IDs, then Anthem would be left out in the cold and = =3D would be=3D20 to blame for invalidating otherwise valid =3D mark-up.</FONT></SPAN></DIV> <DIV dir=3D3Dltr align=3D3Dleft><SPAN><FONT face=3D3D"Comic Sans = MS" =3D color=3D3D#000080=3D20 size=3D3D2></FONT></SPAN> </DIV> <DIV dir=3D3Dltr align=3D3Dleft><SPAN><FONT face=3D3D"Comic Sans = MS" =3D color=3D3D#000080=3D20 size=3D3D2>What does the team think? </FONT></SPAN></DIV> <DIV dir=3D3Dltr align=3D3Dleft><SPAN><FONT face=3D3D"Comic Sans = MS" =3D color=3D3D#000080=3D20 size=3D3D2></FONT></SPAN> </DIV> <DIV dir=3D3Dltr align=3D3Dleft><SPAN><FONT face=3D3D"Comic Sans = MS" =3D color=3D3D#000080=3D20 size=3D3D2></FONT></SPAN> </DIV> <DIV><FONT face=3D3D"Comic Sans MS" color=3D3D#000080 =3D size=3D3D2></FONT> </DIV> <DIV align=3D3Dleft> <DIV style=3D3D"WIDTH: 80%" align=3D3Dleft><FONT face=3D3D"Comic = Sans =3D MS"><B>Brian=3D20 Lowe</B>, AJP Interactive<BR></FONT><FONT face=3D3D"Comic Sans =3D MS">w: <U><A=3D20 style=3D3D"COLOR: blue" onclick=3D3D"return =3D top.js.OpenExtLink(window,event,this)"=3D20 href=3D3D"http://www.ajpi.co.uk/" =3D target=3D3D_blank>www.ajpi.co.uk</A></U></FONT>=3D20 <FONT face=3D3D"Comic Sans MS">e: <U><A style=3D3D"COLOR: = blue"=3D20 onclick=3D3D"return top.js.OpenExtLink(window,event,this)"=3D20 href=3D3D"mailto:br...@aj..."=3D20 target=3D3D_blank>br...@aj...</A></U></FONT> <FONT=3D20 face=3D3D"Comic Sans MS">f: 07075 = 167630</FONT></DIV></DIV><BR><BR> <DIV> </DIV><BR> <BLOCKQUOTE style=3D3D"MARGIN-RIGHT: 0px"> <DIV lang=3D3Den-us dir=3D3Dltr align=3D3Dleft> <HR> <FONT face=3D3DTahoma size=3D3D2><B>From:</B> <A=3D20 onclick=3D3D"return top.js.OpenExtLink(window,event,this)"=3D20 = href=3D3D"mailto:ant...@li..." =3D = target=3D3D_blank>ant...@li... =3D </A>[mailto:<A onclick=3D3D"return =3D top.js.OpenExtLink(window,event,this)"=3D20 = href=3D3D"mailto:ant...@li..." =3D =3D target=3D3D_blank>ant...@li...</A>]=3D= 20 <B>On Behalf Of </B>Manu Temmerman-Uyttenbroeck<BR><B>Sent:</B> =3D 21 March=3D20 2006 06:32<BR><B>To:</B> Roberto<BR><B>Cc:</B> <A=3D20 onclick=3D3D"return top.js.OpenExtLink(window,event,this)"=3D20 = href=3D3D"mailto:ant...@li..."=3D20 =3D target=3D3D_blank>ant...@li...</A><BR><B>Su= b j=3D ect:</B>=3D20 Re: [Anthem.NET-users] Anthem generated code and HTML=3D20 Tidy<BR></FONT><BR> </DIV></BLOCKQUOTE></DIV> <DIV style=3D3D"DIRECTION: ltr"><SPAN> <DIV></DIV> <DIV>Brian Lowe asked the same question 11th of February. This was =3D my=3D20 answer then:</DIV> <DIV style=3D3D"DIRECTION: ltr"> </DIV> <DIV style=3D3D"DIRECTION: ltr"><EM>Your pages are invalid because = =3D of id=3D20 attributes that start with "__",<BR>correct?<BR>If so, then I'm a =3D little=3D20 bit confused. In the url you pasted is that the<BR>name and id =3D attributes=3D20 can only start with letters. Every generated aspx <BR>page =3D contains=3D20 following html elements:<BR><BR><input type=3D3D"hidden"=3D20 name=3D3D"__EVENTTARGET" id=3D3D"__EVENTTARGET" value=3D3D"" =3D /><BR><input=3D20 type=3D3D"hidden" name=3D3D"__EVENTARGUMENT" = id=3D3D"__EVENTARGUMENT" =3D value=3D3D"" />=3D20 <BR><BR>Does this mean that every generated aspx page is invalid? =3D If so,=3D20 then I<BR>would putting 'fixing' this in Anthem on the bottom of = =3D the=3D20 priority<BR>list. If I'm wrong, then sorry... <SPAN=3D20 name=3D3D"st">Brian</SPAN>? Could you pls let me know your =3D <BR>comment on=3D20 this?<BR></EM></DIV> <DIV>So I have the same question again. The 2 hidden fields = =3D generated=3D20 by asp are also seen as invalid?</DIV> <DIV> </DIV> <DIV>Manu.<BR><BR> </DIV> <DIV><SPAN class=3D3Dgmail_quote>On 3/21/06, <B=3D20 class=3D3Dgmail_sendername>Roberto</B> <<A=3D20 onclick=3D3D"return top.js.OpenExtLink(window,event,this)"=3D20 href=3D3D"mailto:ro...@lt..." =3D target=3D3D_blank>ro...@lt...</A>>=3D20 wrote: </SPAN> <BLOCKQUOTE class=3D3Dgmail_quote=3D20 style=3D3D"PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; =3D BORDER-LEFT: #ccc 1px solid"> <DIV style=3D3D"DIRECTION: ltr"> <DIV><FONT face=3D3DArial size=3D3D2>Hi Guys</FONT></DIV> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV> <DIV><FONT face=3D3DArial size=3D3D2>I was using the latest = builds =3D of=3D20 Anthem.NET, but I suspect the error has been there for a =3D while... It=3D20 seems u can't validate a page using HTML tidy with Anthem =3D controls since=3D20 the control names generate ID's such as ID=3D3D"__Button1__" = which =3D I think=3D20 is not allowed in the spec. Below is an example of the like that =3D gives=3D20 me a warning in HTML tidy even though it's not an error it would =3D be cool=3D20 if it could be fixed. </FONT></DIV> <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV> <DIV><FONT face=3D3DArial size=3D3D2>Does anyone have a fix = for=3D20 this?</FONT></DIV> <DIV><PRE><SPAN style=3D3D"BACKGROUND-COLOR: =3D rgb(221,221,255)"><<SPAN>span</SPAN><SPAN> =3D id</SPAN>=3D3D<SPAN>"__Button1__"</SPAN>><<SPAN>input</SPAN><SPAN> = =3D type</SPAN>=3D3D<SPAN>"submit" </SPAN><SPAN>name </SPAN>=3D3D<SPAN>"Button1" </SPAN><SPAN>value</SPAN>=3D3D<SPAN>"Start = Ajax" =3D </SPAN><SPAN>onclick</SPAN>=3D3D<SPAN>"AnthemButton_Click(this,'Button1',= t r=3D ue,'Getting =3D info',false,Button1_PreCallBack,Button1_PostCallBack,null,true,true);ret u=3D rn false;"=3D20 </SPAN><SPAN>id</SPAN>=3D3D<SPAN>"Button1" =3D </SPAN><SPAN>/</SPAN>></<SPAN>span</SPAN>><<SPAN>span</SPAN> <=3D SPAN> id</SPAN>=3D3D<SPAN>"ProgressSection" =3D </SPAN><SPAN>style</SPAN>=3D3D<SPAN>"visibility:hidden;" </SPAN>><<SPAN>img</SPAN><SPAN> =3D src</SPAN>=3D3D<SPAN>"images/indicator.gif" =3D </SPAN><SPAN>border</SPAN>=3D3D<SPAN>"0" =3D </SPAN><SPAN>style</SPAN>=3D3D<SPAN>"vertical-align:middle; =3D padding-left:5px; padding-right:2px;"=3D20 </SPAN><SPAN>alt</SPAN>=3D3D<SPAN>"Progress Icon" =3D </SPAN><SPAN>/</SPAN>>Please wait while retrieving =3D information...</<SPAN>span</SPAN>></SPAN></PRE></DIV> <DIV><PRE><SPAN style=3D3D"BACKGROUND-COLOR: =3D rgb(221,221,255)">line 36 column 9 - Warning: <span> ID =3D "__Button1__" uses XML ID synta</SPAN></PRE><PRE><SPAN =3D style=3D3D"BACKGROUND-COLOR: rgb(221,221,255)"></SPAN> </PRE></DIV> <DIV><SPAN style=3D3D"BACKGROUND-COLOR: rgb(221,221,255)"><FONT = =3D face=3D3DArial=3D20 size=3D3D2>Regards Rob</FONT></SPAN><SPAN=3D20 style=3D3D"BACKGROUND-COLOR: =3D rgb(221,221,255)"></SPAN></DIV></DIV><BR>No=3D20 virus found in this outgoing message.<BR>Checked by AVG = Free=3D20 Edition.<BR>Version: 7.1.385 / Virus Database: 268.2.6/286 - =3D Release=3D20 Date: 20/03/2006<BR><BR><BR></BLOCKQUOTE></DIV><BR></SPAN></DIV> <DIV style=3D3D"DIRECTION: ltr"> =3D <BLOCKQUOTE></BLOCKQUOTE></DIV></BLOCKQUOTE></DIV><BR></SPAN></DIV></BLO C=3D KQUOTE></DIV><BR></BLOCKQUOTE></BODY></HTML> ------=3D_NextPart_000_002A_01C64CDD.FF41BEE0-- --__--__-- Message: 3 Subject: RE: [Anthem.NET-users] Anthem generated code and HTML Tidy Date: Tue, 21 Mar 2006 12:36:58 -0500 From: "John Murphy" <jm...@ge...> Cc: "ant...@li..." <ant...@li...> I think it should be Anthem_. Anyone who uses multiple ajax libraries may run into a collision with AJAX_*. I don't think anyone will be confused by the Anthem_* markup if they are already including anthem.dll and creating pages with anthem: tags. Did I object quickly and loudly enough? -----Original Message----- From: ant...@li... [mailto:ant...@li...] On Behalf Of Brian @ AJP Sent: Tuesday, March 21, 2006 6:53 AM To: 'Manu Temmerman-Uyttenbroeck' Cc: ant...@li... Subject: RE: [Anthem.NET-users] Anthem generated code and HTML Tidy I began to mind when I'd spent many weeks in discussion and testing with my Indian subcontractors to get a large web application to pass the W3C validators so that that site could carry the "XHTML" and "CSS" and "WAI-AAA" badges, only to find that as soon as I added Anthem controls to a simple page I lost all my validation ticks. =20 I found the solution and made the suggestion but when it was pointed out that the integral ASP.Net hidden fields all use the same invalid identifiers I decided to drop my campaign. I don't know why the W3C validators and Tidy let the Microsoft "__*" identifiers through and object to others, but that's another issue. =20 Now on revisiting it, and having seen some press about Microsoft's stated intention to make IE7 standards compliant, I'm thinking that they could easily issue a patch to the framework to replace all their double underscores and generate valid IDs for the __EVENTTARGET and __EVENTARGUMENT and __VIEWSTATE hidden fields. If they do that, and Anthem continues to use the invalid double underscores, then Anthem could get the blame for lots of invalid HTML. =20 I'll pick up the latest snapshot today, and locate the required changes and email you the relevant lines to change, if you don't mind. I tried CVS and couldn't get my head around it :-/ =20 Per my original suggestion, I propose replacing the invalid "__*" with a valid "AJAX_*" =20 That would clearly identify to any human reader trying to step through or debug the code that this element is peculiar to an AJAX addition to the page. =20 I'm equally happy to make it Anthem_ to give Jason some recognition for his fantastic development, but I wondered if that would be as clear to anyone coming later to review the generated code. Would they necessarily know that Anthem was an implementation of AJAX? =20 I'm a firm believer also in Alzheimer's law of programming: "After 3 weeks you forget why you used that identifier or construct, so your names and comments need to be very, very clear." =20 So, unless anyone objects loudly (and quickly), I'm going to recommend changing the invalid "__" to a valid "AJAX_". =20 Code will follow. =20 =20 Brian Lowe, AJP Interactive w: www.ajpi.co.uk <http://www.ajpi.co.uk/> e: br...@aj... f: 07075 167630 =20 _____ =20 From: ant...@li... [mailto:ant...@li...] On Behalf Of Manu Temmerman-Uyttenbroeck Sent: 21 March 2006 09:24 To: br...@aj... Cc: Roberto; ant...@li... Subject: Re: [Anthem.NET-users] Anthem generated code and HTML Tidy =09 =09 I personally don't really mind this invalid html. But if you really do mind, I don't mind changing it :) Could you therefore maybe submit a patch on sourceforge? It will save me time to do it. Or send me a mail with what I have to change where. Pls download first the latest snapshot so we are using the same code... =20 Could you do this for me? =20 Manu. =09 =20 On 3/21/06, Manu Temmerman-Uyttenbroeck <man...@gm...> wrote:=20 Ok Brian. If I'll find the change I'll check in the change tonight. I hope it won't break any code though...=20 Hmm on second thought... I won't check it in. Could you maybe make some testing for this? If you can assure me that it won't break anything, then I'll check it in. =09 =20 Manu. =09 =20 =09 On 3/21/06, Brian @ AJP <br...@aj...> wrote:=20 If you follow the W3C recommendation for HTML and XHTML you will find that an identifier must begin with a letter, not a number or underscore, so the ASP.Net 'standard' hidden fields do use invalid HTML, and so you can expect all ASP.Net pages to fail this validation test. (I don't know why Tidy doesn't highlight "__EVENTTARGET" and "__EVENTARGUMENT" - maybe there's a switch in it that turns a blind eye to it because it knows it's Microsoft.)=20 =20 I suggested a fix for the anthem-generated element IDs by simply changing a couple of lines of code in manager.cs, but didn't press it because fixing it seemed pointless in light of the major Microsoft invalidations.=20 =20 Now I'm thinking it should be fixed while we know about it and how to fix it. The alternative is to carry on with known invalid generated IDs. If Microsoft (newly committed to 'compatibility' and 'standards') issues a patch to the ASP.Net framework that fixes their invalid IDs, then Anthem would be left out in the cold and would be to blame for invalidating otherwise valid mark-up. =20 What does the team think?=20 =20 =20 =20 Brian Lowe, AJP Interactive w: www.ajpi.co.uk <http://www.ajpi.co.uk/> e: br...@aj... f: 07075 167630 =20 _____ =20 From: ant...@li... [mailto:ant...@li...] On Behalf Of Manu Temmerman-Uyttenbroeck Sent: 21 March 2006 06:32 To: Roberto Cc: ant...@li... Subject: Re: [Anthem.NET-users] Anthem generated code and HTML Tidy =09 =20 =09 Brian Lowe asked the same question 11th of February. This was my answer then: =20 Your pages are invalid because of id attributes that start with "__", correct? If so, then I'm a little bit confused. In the url you pasted is that the name and id attributes can only start with letters. Every generated aspx=20 page contains following html elements: =09 <input type=3D3D"hidden" name=3D3D"__EVENTTARGET" id=3D3D"__EVENTTARGET" value=3D3D"" /> <input type=3D3D"hidden" name=3D3D"__EVENTARGUMENT" id=3D3D"__EVENTARGUMENT" value=3D3D"" />=20 =09 Does this mean that every generated aspx page is invalid? If so, then I would putting 'fixing' this in Anthem on the bottom of the priority list. If I'm wrong, then sorry... Brian? Could you pls let me know your=20 comment on this? =09 So I have the same question again. The 2 hidden fields generated by asp are also seen as invalid? =20 Manu. =09 =20 On 3/21/06, Roberto <ro...@lt...> wrote:=20 Hi Guys =20 I was using the latest builds of Anthem.NET, but I suspect the error has been there for a while... It seems u can't validate a page using HTML tidy with Anthem controls since the control names generate ID's such as ID=3D3D"__Button1__" which I = think is not allowed in the spec. Below is an example of the like that gives me a warning in HTML tidy even though it's not an error it would be cool if it could be fixed.=20 =20 Does anyone have a fix for this? <span id=3D3D"__Button1__"><input type=3D3D"submit" name =3D3D"Button1" value=3D3D"Start Ajax" onclick=3D3D"AnthemButton_Click(this,'Button1',true,'Getting info',false,Button1_PreCallBack,Button1_PostCallBack,null,true,true);ret urn false;"=20 id=3D3D"Button1" /></span><span id=3D3D"ProgressSection" style=3D3D"visibility:hidden;" ><img src=3D3D"images/indicator.gif" border=3D3D"0" style=3D3D"vertical-align:middle; padding-left:5px; padding-right:2px;"=20 alt=3D3D"Progress Icon" />Please wait while retrieving information...</span> line 36 column 9 - Warning: <span> ID "__Button1__" uses XML ID synta =20 Regards Rob No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.2.6/286 - Release Date: 20/03/2006 =09 =09 =09 --__--__-- _______________________________________________ anthem-dot-net-users mailing list ant...@li... https://lists.sourceforge.net/lists/listinfo/anthem-dot-net-users End of anthem-dot-net-users Digest |
