You could try to add an own prefix to the image created dynamically so
writeIdIfNecessary does render the id, couldn't you?

Bruno

2005/7/25, Sean Schofield <[EMAIL PROTECTED]>:
> Its definitely the writeIdIfNecessary (I was just looking up the svn
> blame to find the culprit when I read your message.)
> 
> I can see why in *most* cases we don't want to render an id unless one
> was explicitly provided.  In the tree2 case though we are creating
> components dynamically and they need ids that can be refrenced via
> javascript.
> 
> sean
> 
> On 7/25/05, Bruno Aranda <[EMAIL PROTECTED]> wrote:
> > I am the one who provided the patch to extend the graphicImage
> > component. As far as I recall I only put in HtmlImageRendererBase the
> > code that was in the HtmlImageRenderer class. So I am not sure what is
> > happening now. Maybe an issue with
> > HtmlRendererUtils.writeIdIfNecessary....
> >
> > Bruno
> >
> > 2005/7/25, Sean Schofield <[EMAIL PROTECTED]>:
> > > I noticed that UIGraphic components are no longer having their id's
> > > rendered in the HTML.  This is causing a problem with Tree2.  Martin,
> > > can you shed some light on the changes you made to this class?  Is
> > > writing the id a problem with the spec or is it something that
> > > accidentally got lost?
> > >
> > > Regards,
> > >
> > > sean
> > >
> >
>

Reply via email to