myfaces-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Marinschek <martin.marinsc...@gmail.com>
Subject Re: Javascript getElementById Issues
Date Sat, 01 Jan 2005 21:42:52 GMT
I believe almost all components are available in an extended version
(due to several enhancements in MyFaces), so that shouldn't be to big
a problem.

regards,

Martin


On Sat, 1 Jan 2005 13:01:32 -0500, Sean Schofield
<sean.schofield@gmail.com> wrote:
> > Yes, Myfaces would still be following the spec for the behavior of
> > components if we did this.   However, we could only do this on our
> > extended component set, rather than the default set of components.
> > This is because the components under the javax.faces.component.html
> > package are part of the API, so we can't alter their behavior.
> 
> So this means that you cannot change the functionality of
> <h:inputText> for instance?  If so, that's a bit of a bummer but not
> the end of the world.
> 
> I suppose MyFaces could provide "extended" components for everything
> (including <h:inputText>) and just provide this functionality.  Would
> that be the plan?  Its my understanding that there is not currently an
> extended myfaces version for every component.  Would it be hard to
> provide 100% coverage (even if the only enhancemtn was styleId?)
> 
> The one drawback to not modifying the implentation of the standard
> components is that you are kind of locking yourself into myfaces.  Not
> really a huge deal I suppose because you could always use a
> refactoring tool to replace references to <myfaces:inputText> to
> <h:inputText> if the spec were ever to address this issue.
> 
> sean
>

Mime
View raw message