Working with JIRA / Progress component a11y

[Justin Obara]

Hi Everett,

We cut our releases off of trunk, so you can work straight off of it.

https://source.fluidproject.org/svn/fluid/infusion/trunk/

Thanks
Justin

On 2010-08-18, at 8:17 PM, E.J. Zufelt wrote:

> Good evening,
> 
> I read the wiki page on contributing and everything is clear to me except for what version / branch of Infusion I should be writing patches against.  I will upload the patches to the list, as this is far easier for me than using JIRA.
> 
> If you can give me the svn path to what I should be patching that would be great.
> 
> Thanks,
> Everett Zufelt
> http://zufelt.ca
> 
> Follow me on Twitter
> http://twitter.com/ezufelt
> 
> View my LinkedIn Profile
> http://www.linkedin.com/in/ezufelt
> 
> 
> 
> On 2010-08-11, at 8:58 AM, Richards, Jan wrote:
> 
>> Hi Justin and Everett,
>>  
>> Sorry for the confusion! Yes, that’s the URL. I submitted a series of JIRAs on the components at:
>> http://build.fluidproject.org/infusion/demos/
>>  
>> Here are the JIRAs:
>> http://issues.fluidproject.org/browse/FLUID-3664
>> http://issues.fluidproject.org/browse/FLUID-3665
>> http://issues.fluidproject.org/browse/FLUID-3666
>> http://issues.fluidproject.org/browse/FLUID-3667
>> http://issues.fluidproject.org/browse/FLUID-3668
>> http://issues.fluidproject.org/browse/FLUID-3669
>> http://issues.fluidproject.org/browse/FLUID-3670
>> http://issues.fluidproject.org/browse/FLUID-3671
>>  
>> For the record, I’m not a regular screen reader user, so any additional comments/corrections you have would be much appreciated.
>>  
>> Cheers,
>> Jan
>>  
>> --
>> (Mr) Jan Richards, M.Sc.
>> jrichards at ocad.ca | 416-977-6000 ext. 3957
>> Inclusive Design Research Centre (IDRC)
>> OCAD University
>>  
>> From: Justin Obara [mailto:obara.justin at gmail.com] 
>> Sent: August 11, 2010 8:19 AM
>> To: E.J.Zufelt
>> Cc: fluid-work-request at fluidproject.org; Richards, Jan
>> Subject: Re: Working with JIRA / Progress component a11y
>>  
>> Hi Everett,
>>  
>> I agree, it is a good idea to have a url provided. It keeps track of and makes explicit where the issue was found. I think in this case, since this was filed during a bit of a testing sprint, that it was probably just missed when filling out the jira. Thanks for alerting us to this.
>>  
>> I believe the correct url for the Progress Component demo that was tested is  http://build.fluidproject.org/infusion/demos/progress/html/progress.html 
>>  
>> I've cc'd Jan here so that he can confirm it, and made a comment on the jira itself as well.
>>  
>> Thanks
>> Justin
>>  
>> On 2010-08-11, at 6:05 AM, E.J. Zufelt wrote:
>> 
>> 
>> Good morning,
>>  
>> I was taking a look at issues in JIRA this morning (a chore with a screen-reader), and I came across a progress bar issue:
>>  
>> http://issues.fluidproject.org/browse/FLUID-3671
>>  
>> The comments on testing were useful, but there was no information, that I could find, showing a URL for any example page where the testing was performed.  This makes it quite difficult to retest and confirm the posted results.
>>  
>> In this situation is it safe for me to assume that the problem is always experienced with the progress component, regardless of implementation, or is it likely that the information was just not posted to the JIRA?  Having a URL provided for issues would be useful for future testing and troubleshooting.
>>  
>> Thanks,
>> Everett Zufelt
>> http://zufelt.ca
>>  
>> Follow me on Twitter
>> http://twitter.com/ezufelt
>> 
>> View my LinkedIn Profile
>> http://www.linkedin.com/in/ezufelt
>>  
>>  
>>  
>> _______________________________________________________
>> fluid-work mailing list - fluid-work at fluidproject.org
>> To unsubscribe, change settings or access archives,
>> see http://fluidproject.org/mailman/listinfo/fluid-work
>>  
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20100819/c6bc4884/attachment.html>