FLUID-3751: Redesign and implement the progress component demo

Metadata

Source
FLUID-3751
Type
Task
Priority
Critical
Status
Closed
Resolution
Fixed
Assignee
Justin Obara
Reporter
Justin Obara
Created
2010-09-22T18:06:06.955-0400
Updated
2010-11-19T12:53:13.686-0500
Versions
N/A
Fixed Versions
  1. 1.3
Component
  1. Progress

Description

Comments

  • Golam Chowdhury commented 2010-10-04T12:39:09.327-0400

    FLUID-3751.patch which cleaned up the progress.js by adding an string object to hold the strings that we use to display status of our progress in progress demo html page.

  • Justin Obara commented 2010-10-04T14:01:13.403-0400

    "Bug Parade Infusion 1.3"

  • Golam Chowdhury commented 2010-10-06T12:52:09.156-0400

    FLUID-3751.v2.patch: Resolves the repeat issues that we were having with latest Fire Fox 3.6.3 using NVDA2010.2 and JAWS10&11 on XP. We have removed the aria role from the main container "status-area" then we don't hear any more repeated value while progress is going as well no more repeats of the feedback after progress completed.

  • Golam Chowdhury commented 2010-10-07T10:07:54.911-0400

    Note: FLUID-3751.v2.patch includes all the changes in FLUID-3751.patch.

  • Golam Chowdhury commented 2010-10-07T16:11:38.967-0400

    FLUID-3751.v3.patch: This patch includes all the changes in FLUID-3751.patch and FLUID-3751.v2.patch. We have cleaned some codes in progess.js.

  • Golam Chowdhury commented 2010-10-08T12:13:46.484-0400

    FLUID-3751.v4.patch: This patch includes all the changes in FLUID-3751.patch, FLUID-3751.v2.patch, and FLUID-3751.v3.patch. We have re-factored some of the codes.

  • Golam Chowdhury commented 2010-10-08T14:03:32.877-0400

    FLUID-3751: Re-factor some of the code. We have added string object to hold the strings that we use to display status of our progress also resolved the repeat issues that we were having with the latest Fire Fox 3.6.3, NVDA2010.2 and JAWS10&11.

  • Justin Obara commented 2010-10-18T08:50:45.137-0400

    Colin, Golam, and myself walked through the code and reviewed the changes.

  • Golam Chowdhury commented 2010-11-08T11:32:21.900-0500

    FLUID-3751 need to remove aria-channel, and role=description attributes because they no longer present in ARIA spec.

  • Golam Chowdhury commented 2010-11-08T11:59:28.788-0500

    FLUID-3751.v5.patch remove aria-channel, and description role attributes because they no longer present in ARIA spec. We have added status role to replace with description role.

  • Golam Chowdhury commented 2010-11-09T10:02:18.447-0500

    FLUID-3751.v6.patch changed role to status, aria-relevant to text, and aria-atomic to false.

  • Justin Obara commented 2010-11-09T12:54:59.048-0500

    Reviewed and committed Golam's patch ( FLUID-3751.v6.patch ). Also sat down and tested it with him. It was working fine in firefox, but IE 8 still wouldn't read the status messages. We weren't able to find a way around that.

  • Golam Chowdhury commented 2010-11-18T12:19:46.048-0500

    FLUID-3751: Updated the demo to change aria-relevant attributes values and add "additions text" instead of "all".

  • Golam Chowdhury commented 2010-11-18T12:21:01.477-0500

    FLUID-3751.v7.patch in demo changed aria-relevant attributes values and added "additions text" instead of "all".

  • heidi valles commented 2010-11-18T15:32:21.527-0500

    After progress is complete, the live region text is read. Pressing tab then reads "Restart the Demo link". When you tab away from this link, and then back to it, the link is no longer read (says nothing when tab to it). It seems the reason is that NVDA changes modes when leaving the demo, and so when going back to it, it no longer reads the link text. Not sure if this is an expected NVDA behavior or not, but it doesn't seem related to our code. In fact, I think it's a firefox issue. http://groups.google.com/group/free-aria/browse_thread/thread/c7d93105884074df/e740ee9e58c35f1f

  • Justin Obara commented 2010-11-19T12:52:02.290-0500

    Above comment filed as FLUID-3859

  • Justin Obara commented 2010-11-19T12:53:13.685-0500

    The final patch has now found it's way into trunk. Any other issues should now be filed as new jiras.