On 6/13/2007 3:59 PM, Adam Winer wrote:
On 6/13/07, Gabrielle Crawford <[EMAIL PROTECTED]> wrote:
Hi,

On 6/12/2007 9:36 AM, Adam Winer wrote:

> Does anyone have high-priority issues they'd like resolved
> for 1.0.1?
>
> I'd very much like to switch the default validation mechanism
> from ALERT to INLINE, as I think that's the "killer feature"
> for this release.

has this has any accessibility testing?

Good point - it hasn't.  We should consider forcing
alerts when in screen reader mode, and it'd be good to have
some accessibility testing otherwise.
Personally I think forcing alerts in screen reader mode should be fine for 1.0.1. Hopefully that's easy.

Thanks,

Gab

-- Adam

 

+1 to the rest

Thanks,

Gab

> We also need some real release notes,
> seein' as we're a grown-up project and all. :)  I'll give
> that a whirl.
>
> In addition, I'm thinking we should resolve at least:
>
> http://issues.apache.org/jira/browse/TRINIDAD-50
> ClassCastException in ExternalContextUtils
>
> ... but that we should postpone:
>
> http://issues.apache.org/jira/browse/TRINIDAD-35
> Dialog Framework to support 'iframe/lightweight' dialogs
> http://issues.apache.org/jira/browse/TRINIDAD-46
> Switch from IFRAMEs to XMLHttpRequest for non-fileupload requests
> http://issues.apache.org/jira/browse/TRINIDAD-51
> Support manually adding SetActionListener
>
> And @Jeanne, isn't
> http://issues.apache.org/jira/browse/TRINIDAD-49
> resolved?
>
> -- Adam


Reply via email to