Hello, Just to be clear, the components that need to be retested in regards to keyboard accessibility are InlineEdit (all variants) and UI Options. If you have already tested these components before the fix for FLUID-3590 went in, you just need to do the keyboard tasks from the state based tests.
Thanks Justin On 2010-04-09, at 4:52 PM, Justin Obara wrote: > The fix for FLUID-3590 has just gone in. All testing tasks are now open. > > Please also make sure to go back and redo any of the keyboard testing tasks > for components that you have already tested. > > Thanks for all the help > Justin > > On 2010-04-08, at 5:30 PM, Justin Obara wrote: > >> We are progressing towards a fix for our last remaining blocker, FLUID-3590. >> http://issues.fluidproject.org/browse/FLUID-3590 >> >> Hopefully the fix will be in place in a day or so. >> >> What this means for testing is that all of the reorderer tasks and any >> component that uses the keyboard a11y plugin will need the keyboard tasks >> rerun. >> >> You should probably focus on the UI Options and Uploader tasks to start with. >> >> Thanks for all of the help. >> Justin > _______________________________________________________ fluid-work mailing list - [email protected] To unsubscribe, change settings or access archives, see http://fluidproject.org/mailman/listinfo/fluid-work
