29 messages in org.oasis-open.lists.officeRe: [office] Table Refresh Delay| From | Sent On | Attachments |
|---|---|---|
| Richard Schwerdtfeger | Jul 12, 2008 8:52 am | |
| Duane Nickull | Jul 12, 2008 8:30 pm | |
| Richard Schwerdtfeger | Jul 14, 2008 11:31 am |  .gif, .gif, .gif, 7 more |
| robe...@us.ibm.com | Jul 14, 2008 1:48 pm | |
| Duane Nickull | Jul 14, 2008 2:21 pm | |
| Richard Schwerdtfeger | Jul 16, 2008 10:55 am | .gif, .gif, .gif, 7 more |
| robe...@us.ibm.com | Jul 16, 2008 11:36 am | |
| Richard Schwerdtfeger | Jul 17, 2008 4:46 pm | .gif, .gif, .gif, 7 more |
| Malte Timmermann | Jul 18, 2008 2:07 am | |
| Dave Pawson | Jul 18, 2008 3:49 am | |
| Richard Schwerdtfeger | Jul 18, 2008 6:26 am | .gif, .gif, .gif, 7 more |
| Duane Nickull | Jul 18, 2008 9:23 am | .gif, .gif, .gif, 6 more |
| Peter Korn | Jul 18, 2008 10:36 am | |
| Duane Nickull | Jul 18, 2008 11:12 am | |
| robe...@us.ibm.com | Jul 18, 2008 11:50 am | |
| Warren Turkal | Jul 18, 2008 1:28 pm | |
| Duane Nickull | Jul 18, 2008 1:58 pm | |
| Warren Turkal | Jul 18, 2008 2:03 pm | |
| robe...@us.ibm.com | Jul 18, 2008 2:12 pm | |
| robe...@us.ibm.com | Jul 18, 2008 3:30 pm | |
| Peter Korn | Jul 18, 2008 3:44 pm | |
| Duane Nickull | Jul 18, 2008 4:10 pm | |
| Warren Turkal | Jul 18, 2008 4:41 pm | |
| Dave Pawson | Jul 18, 2008 11:00 pm | |
| robe...@us.ibm.com | Jul 19, 2008 7:30 am | |
| Richard Schwerdtfeger | Jul 20, 2008 6:16 am | .gif, .gif, .gif, 7 more |
| Dave Pawson | Jul 20, 2008 6:34 am | |
| Peter Korn | Jul 20, 2008 2:19 pm | |
| Malte Timmermann | Jul 21, 2008 5:35 am |
| Subject: | Re: [office] Table Refresh Delay | |
|---|---|---|
| From: | Malte Timmermann (Malt...@Sun.COM) | |
| Date: | Jul 18, 2008 2:07:42 am | |
| List: | org.oasis-open.lists.office | |
I don't agree on "require user agents to limit this to no more than 3 times a second".
I must admit that I don't believe a higher frequency would make any sense for anything, but People have different needs, and if someone for what every reason needs a higher frequency, the application should be allowed to support this.
It's something the author should avoid.
Malte.
Richard Schwerdtfeger wrote, On 18.07.08 01:46:
That is fine. This will just mean we will require user agents and authors to limit this to no more than 3 times a second which may cause epileptic seizures. If we did not have adequate justification for having this level of granularity we could avoid imposing this other requirement. ok?
Rich
Rich Schwerdtfeger Distinguished Engineer, SWG Accessibility Architect/Strategist Chair, IBM Accessibility Architecture Review Board blog: http://www.ibm.com/developerworks/blogs/page/schwer Inactive hide details for "Duane Nickull" <dnic...@adobe.com>"Duane Nickull" <dnic...@adobe.com>
*"Duane Nickull" <dnic...@adobe.com>*
07/14/08 02:23 PM
To
Richard Schwerdtfeger/Austin/IBM@IBMUS
cc
<off...@lists.oasis-open.org>, <offi...@lists.oasis-open.org>
Subject
Re: [office] Table Refresh Delay
Whether or not it is done 1000 times per second is not the issue. Giving developers and document writers the ability to control it via mlsecs would be nice to have for interactive documents. Transitions of content to highlight or change things (think MS PPT) should probably use a consistent model across all odf content. Make some sense? Aus mein Blackberry/from my Blackberry
----- Original Message ----- From: Richard Schwerdtfeger <sch...@us.ibm.com> To: Duane Nickull Cc: off...@lists.oasis-open.org <off...@lists.oasis-open.org>; offi...@lists.oasis-open.org <offi...@lists.oasis-open.org> Sent: Mon Jul 14 11:32:05 2008 Subject: Re: [office] Table Refresh Delay
Is milliseconds practical? Would a table really update every x milliseconds? I can't imagine network performance making this practical.
The problem area is >= 3 times per second. This will cause seizures. If the update rate were seconds this is not a problem.
If it were this fast I would do a two pronged approach:
* Tell authors to not set this to more than 3 times per second. * I would require that office agents provide a UI feature that allows the user to limit the refresh rate.
Rich
Rich Schwerdtfeger Distinguished Engineer, SWG Accessibility Architect/Strategist Chair, IBM Accessibility Architecture Review Board blog: http://www.ibm.com/developerworks/blogs/page/schwer "Duane Nickull" <dnic...@adobe.com>
"Duane Nickull" <dnic...@adobe.com>
07/12/08 10:29 PM
To
Richard Schwerdtfeger/Austin/IBM@IBMUS, <off...@lists.oasis-open.org>
cc
<offi...@lists.oasis-open.org>
Subject
Re: [office] Table Refresh Delay
I would highly recommend miliseconds but provide best practives to introdue warnings when use would result in seni-optimal UE's.
Sound logical?
D Aus mein Blackberry/from my Blackberry
----- Original Message ----- From: Richard Schwerdtfeger <sch...@us.ibm.com> To: off...@lists.oasis-open.org <off...@lists.oasis-open.org> Cc: offi...@lists.oasis-open.org <offi...@lists.oasis-open.org> Sent: Sat Jul 12 08:52:20 2008 Subject: [office] Table Refresh Delay
Can someone from the TC please tell me the units for: <table:refresh-delay> ?
Is this in seconds? This is very important for accessibility as if it is less than a second then there is a potential to cause seizures.
Whatever the answer, would someone please update the specification to reflect the actual units?
Thank you, Rich
Rich Schwerdtfeger Distinguished Engineer, SWG Accessibility Architect/Strategist Chair, IBM Accessibility Architecture Review Board blog: http://www.ibm.com/developerworks/blogs/page/schwer