W3C

- DRAFT -

UAWG Conference Call 10 Aug 2006

10 Aug 2006

See also: IRC log

Attendees

Present
Jim_Allan, CKLaws, JR, DPoehlman, PPerente
Regrets
Chair
Jim Allan
Scribe
JR

Contents


 

 

<scribe> Scribe: JR

JA: XHTML 2.0 new draft released...

<jallan> XHTML 2 draft http://www.w3.org/TR/2006/WD-xhtml2-20060726/

JA: Lots of references to what user agents should and shouldn't do
... SUggest other gtoup members should review it

CL: Asked about a F2F

JA: Maybe in Boston in January as part of some W3C thing

Guideline 5. Ensure user control of user interface behavior

JA: Just a point...there are no P1's for this guideline

<jallan> ACTION: JA include no P1 comments in Guideline 5 on issues chart [recorded in http://www.w3.org/2006/08/10-ua-minutes.html#action01]

5.1 No automatic content focus change (P2)

JA: Under ex. techs. #4 (In JavaScript, the focus may be changed with myWindow.focus();) is a bit mysterious

<jallan> UAAG techniques Guideline 5 http://www.w3.org/TR/UAAG10-TECHS/uaag10-tech.html#gl-user-control-ui

<jallan> techniques are not about configuration.

PP: What about when focus moves in same viewport

JA: 5.4

JR: Some techs refer to situations diff that checkpoint calls for

CL: These aren't what people do...e.g. when new window opens it gets focus rather than not getting focus and showing an alert.

JA: Example tech would be extension to broser to do pop-up blocking

CL: THinks #1 is fine
... But default should be to move focus
... ex. popup to enter ID and password
... Need to clarify what is a duplicate view (#3)

<jallan> tech #3, duplicate browser instances (2 browsers), or HPR 2 views (graphic and text), as in a spreadsheet split view

JA: Mentions "Open in New Broswer" feature.

JR: IE already does the duplicate stuff as asked
... Maybe make distinction between duplicate and split

JA & JR: Read duplicate stuff as relevant because even though content focus has changed it is to the same point in a twinned doc

JA: #4 is a note
... #5 is HTML4 specific
... Also what about frames....eg. in nav frame select link...if new content is brought up, focus should move to new stuff
... So this is "explicit user request"

Viewport includes windows, frames, pieces of paper

JA: We should put note about frames in ex 1.

<jallan> ACTION: JA: write note about frames for technique 1 in 5.1 [recorded in http://www.w3.org/2006/08/10-ua-minutes.html#action02]

5.2 Keep viewport on top (P2)

<jallan> JR: is this something that is controled by the OS

JR: What if other viewport is in another app

<jallan> various applications have the feature "stay on top", what happens when several application use "stay on top", this seems to be an OS negotialtion issue

JA: We are only talking about user agent app viewports

<scribe> ACTION: JR to Write note for 5.2 clarifying that this covers only the user agent app. [recorded in http://www.w3.org/2006/08/10-ua-minutes.html#action03]

5.3 Manual viewport open only (P2)

JR: How does this handle isblank?

CL: HPR assumes that clicking on a link is an explit request

JR: So maybe a note needed to say its ok to open new viewport for the URL of the link...but not any other on_load viewports

<scribe> ACTION: JR to Write note for 5.3 clarifying that new viewport is ok on selecting link if the URL is the same [recorded in http://www.w3.org/2006/08/10-ua-minutes.html#action04]

<jallan> ACTION: JA: modifier key technique [recorded in http://www.w3.org/2006/08/10-ua-minutes.html#action05]

5.4 Selection and focus in viewport (P2)

JA: In page links...page should shift but focus must as well.
... Would like to see this scenario addressed.

CL: Prob is that browser can't move focus to things that can't take focus

JA: In IE there are some ways to get around...eg into table cell
... SHould we explicity note that we expect focus to follow internal navigation - "point of regard"

<jallan> ACTION: JA: 5.4 point of regard (in page focus) [recorded in http://www.w3.org/2006/08/10-ua-minutes.html#action06]

5.5 Confirm form submission (P2)

JR: Everything is forms in Webv apps.

JA: Thinks we should add not about "ENTER" being a problem
... Maybe also clarify that it is when pressing ENTER from somewhere that is not a button - e.g. a textbox

<jallan> 5.5 give example of form configuration 'enter on submit' is ok,

<jallan> ACTION: JA: example configuration for enter - form submission [recorded in http://www.w3.org/2006/08/10-ua-minutes.html#action07]

Summary of Action Items

[NEW] ACTION: JA include no P1 comments in Guideline 5 on issues chart [recorded in http://www.w3.org/2006/08/10-ua-minutes.html#action01]
[NEW] ACTION: JA: 5.4 point of regard (in page focus) [recorded in http://www.w3.org/2006/08/10-ua-minutes.html#action06]
[NEW] ACTION: JA: example configuration for enter - form submission [recorded in http://www.w3.org/2006/08/10-ua-minutes.html#action07]
[NEW] ACTION: JA: modifier key technique [recorded in http://www.w3.org/2006/08/10-ua-minutes.html#action05]
[NEW] ACTION: JA: write note about frames for technique 1 in 5.1 [recorded in http://www.w3.org/2006/08/10-ua-minutes.html#action02]
[NEW] ACTION: JR to Write note for 5.2 clarifying that this covers only the user agent app. [recorded in http://www.w3.org/2006/08/10-ua-minutes.html#action03]
[NEW] ACTION: JR to Write note for 5.3 clarifying that new viewport is ok on selecting link if the URL is the same [recorded in http://www.w3.org/2006/08/10-ua-minutes.html#action04]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.127 (CVS log)
$Date: 2006/08/10 19:07:29 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.127  of Date: 2005/08/16 15:12:03  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: JR
Inferring ScribeNick: JR
Default Present: Jim_Allan, CKLaws, JR, DPoehlman, PPerente
Present: Jim_Allan CKLaws JR DPoehlman PPerente
Got date from IRC log name: 10 Aug 2006
Guessing minutes URL: http://www.w3.org/2006/08/10-ua-minutes.html
People with action items: ja jr

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


[End of scribe.perl diagnostic output]