Re: [Anthem.NET-users] Anthem generated code and HTML Tidy

[Manu Temmerman-U. <man...@gm...>]

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...

Could you do this for me?

Manu.


On 3/21/06, Manu Temmerman-Uyttenbroeck <
man...@gm...> wrote:
>
>  Ok Brian. If I'll find the change I'll check in the change tonight. I
> hope it won't break any code though...
> 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.
>
> Manu.
>
>
>  On 3/21/06, Brian @ AJP <br...@aj...> wrote:
> >
> >  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.)
> >
> > 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.
> >
> > 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 Anthe=
m
> > would be left out in the cold and would be to blame for invalidating
> > otherwise valid mark-up.
> >
> > What does the team think?
> >
> >
> >
> >  *Brian Lowe*, AJP Interactive
> > w: *www.ajpi.co.uk* e: *br...@aj...* f: 07075 167630
> >
> >
> >
> >
> >  ------------------------------
> > *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
> >
> >
> >
> >  Brian Lowe asked the same question 11th of February. This was my answe=
r
> > then:
> >
> > *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 th=
e
> > name and id attributes can only start with letters. Every generated asp=
x
> >
> > page contains following html elements:
> >
> > <input type=3D"hidden" name=3D"__EVENTTARGET" id=3D"__EVENTTARGET" valu=
e=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
> > comment on this?
> > *
> > So I have the same question again. The 2 hidden fields generated by asp
> > are also seen as invalid?
> >
> > Manu.
> >
> >
> > On 3/21/06, Roberto <ro...@lt...> wrote:
> > >
> > >  Hi Guys
> > >
> > > 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.
> > >
> > > Does anyone have a fix for this?
> > >
> > > <span id=3D"__Button1__"><input type=3D"submit" name=3D"Button1" valu=
e=3D"Start Ajax" onclick=3D"AnthemButton_Click(this,'Button1',true,'Getting=
 info',false,Button1_PreCallBack,Button1_PostCallBack,null,true,true);retur=
n false;" id=3D"Button1" /></span><span id=3D"ProgressSection" style=3D"vis=
ibility:hidden;"><img src=3D"images/indicator.gif" border=3D"0" style=3D"ve=
rtical-align:middle; padding-left:5px; padding-right:2px;" alt=3D"Progress =
Icon" />Please wait while retrieving information...</span>
> > >
> > > line 36 column 9 - Warning: <span> ID "__Button1__" uses XML ID synta
> > >
> > >
> > >
> > > 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
> > >
> > >
> > >
> >
>