from:"\"James Craig\""

Re: IndieUI Teleconference Agenda; 17 December at 22:00Z for 60 minutes

2014-12-16 Thread James Craig

Editor's Report topics:

Events spec:
- on hold until ETF determines Event structure

User Context:
- Several new features from IndieUI being incorporated into CSS4.
- Discussion with CSS WG re: adding MF security model. Shared, separate spec? 
Would affect both JS and CSS accessors.


> On Dec 16, 2014, at 12:32 PM, Janina Sajka  wrote:
> 
> Cross-posting as is now usual ...
> 
> What: IndieUI Task Force Teleconference
> When: Wednesday 17 December
>2:00 PMSan Francisco -- U.S. Pacific  Time (PST: UTC -8)
>4:00 PMAustin -- U.S. Central  Time(CST: UTC -6)
>5:00 PMBoston -- U.S. Eastern  Time(EST: UTC -5)
>   10:00 PMLondon -- British  Time (BST: UTC +0)
>   11:00 PMParis -- Central European Time  (CET: UTC +1)
>6:00 AMBeijing -- China Standard Time  (Thursday, 13 November 
> CST: UTC +8)
>7:00 AMTokyo -- Japan Standard Time(Thursday, 13 November 
> JST: UTC +9)
> Where:W3C Teleconference--See Below
> 
> * Time of day conversions
> 
> Please verify the correct time of this meeting in your time zone using
> the Fixed Time Clock at:
> 
> http://timeanddate.com/worldclock/fixedtime.html?msg=IndieUI+Teleconference&iso=20141217T1700&p1=43&ah=1
> 
> ** Preliminary Agenda for IndieUI Task Force Teleconference 17 December 2014
> 
> Meeting: IndieUI Task Force Teleconference
> Chair:Janina_Sajka
> agenda+ preview agenda with items from two minutes
> agenda+ End of Year Telecon Scheduling -- Reminder
> agenda+   Checkin with Web Apps' Editing TF [See below]
> agenda+ Editor's Report
> agenda+   `Events Spec Changes Vis a Vis Editing TF
> agenda+   User Context -- TPAC Followup
> agenda+   Reconsidering Our Timelines
> agenda+   Requirements & Use Cases Progress
> agenda+   Testing Conversation; Polyfills
> agenda+ User Context Issues & Actions 
> https://www.w3.org/WAI/IndieUI/track/products/3
> agenda+ Events Issues & Actions 
> https://www.w3.org/WAI/IndieUI/track/products/2
> agenda+Other Business
> agenda+   Be Done
> 
> Resource: TPAC Minutes
> Monday:   http://www.w3.org/2014/10/27-indie-ui-minutes.html  
> Tuesday:  http://www.w3.org/2014/10/28-indie-ui-minutes.html
> 
> Resource: Teleconference Minutes
> http://www.w3.org/2014/11/19-indie-ui-minutes.html
> 
> Resource: Web Apps Editing TF
> Editing Explainer:http://w3c.github.io/editing-explainer/
> User Intentions:  
> http://w3c.github.io/editing-explainer/commands-explainer.html
> Resource: For Reference
> Home Page:http://www.w3.org/WAI/IndieUI/
> Email Archive:http://lists.w3.org/Archives/Public/public-indie-ui/
> 
> Resource: Teleconference Logistics
> Dial the Zakim bridge using either SIP or the PSTN.
> PSTN: +1.617.761.6200 (This is a U.S. number).
> SIP: za...@voip.w3.org
> You should be prompted for a pass code,
> This is
> 46343#
> (INDIE#)
> 
> Alternatively, bypass the Zakim prompts and SIP directly into our
> teleconference.
> SIP: 0046...@voip.w3.org
> 
> Instructions for connecting using SIP:
> http://www.w3.org/2006/tools/wiki/Zakim-SIP
> Place for users to contribute additional VoIP tips.
> http://www.w3.org/2006/tools/wiki/Zakim-SIP-tips
> 
> IRC: server: irc.w3.org, channel: #indie-ui.
> 
> During the conference you can manage your participation with Zakim
> commands as follows:
>   61# to mute yourself
>   60# to unMute yourself
>   41# to raise your hand (enter speaking queue)
>   40# to lower your hand (exit speaking queue)
> 
> The system acknowledges these commands with a rapid, three-tone
> confirmation.  Mobile phone users especially should use the mute
> function
> if they don't have a mute function in their phone.  But the hand-raising
> function is a good idea for anyone not using IRC.
> 
> * IRC access
> 
> An IRC channel will be available. The server is
> irc.w3.org,
> The port number is 6665 (Note this is not the normal default) and
> The channel is #indie-ui.
> 
> * Some helpful Scribing and Participation Tips
> http://www.w3.org/WAI/PF/wiki/Teleconference_cheat_sheet
> 
> For more on the IRC setup and the robots we use for agenda and speaker
> queuing and for posting the log to the web, see:
> 
> - For RRSAgent, that captures and posts the log with special attention
> to action items:
> http://www.w3.org/2002/03/RRSAgent
> 
> - For Zakim, the IRC interface to the bridge manager, that will
> maintain speaker and agenda queues:
> http://www.w3.org/2001/12/zakim-irc-bot
> 
> - For a Web gateway to IRC you can use if your network administrators
> forbid IRC, see:
> http://www.w3.org/2001/01/cgi-irc
> 
> - For more on W3C use of IRC see:
> http://www.w3.org/Project/IRC/
> 
> -- 
> 
> Janina Sajka, Phone:  +1.443.300.2200
>   sip:jan...@asterisk.rednote.net
>   Email:  jan...@rednote.net
> 
> The Linux Foundation
> Chair, Open Accessibility:http://a11y.org
> 
> T

Re: IndieUI Teleconference Agenda; 12 November at 22:00Z for 60 minutes

2014-11-11 Thread James Craig

I’ll be about 30 minutes late tomorrow.



> On Nov 11, 2014, at 5:44 PM, Janina Sajka  wrote:
> 
> Cross-posting as before ...
> 
> What:IndieUI Task Force Teleconference
> When:Wednesday 12 November
> 2:00 PMSan Francisco -- U.S. Pacific (Standard) Time   (PST: UTC 
> -8)
> 4:00 PMAustin -- U.S. Central (Standard) Time(CST: UTC -6)
> 5:00 PMBoston -- U.S. Eastern (Standard) Time(EST: UTC -5)
>10:00 PMLondon -- British (Standard) Time(BST: UTC +0)
>11:00 PMParis -- Central European Time  (CET: UTC +1)
> 6:00 AMBeijing -- China Standard Time (Thursday, 13 November CST: 
> UTC +8)
> 7:00 AMTokyo -- Japan Standard Time(Thursday, 13 November 
> JST: UTC +9)
> Where:W3C Teleconference--See Below
> 
> * Time of day conversions
> 
> Please verify the correct time of this meeting in your time zone using
> the Fixed Time Clock at:
> 
> http://timeanddate.com/worldclock/fixedtime.html?msg=IndieUI+Teleconference&iso=20141112T1700&p1=43&ah=1
> 
> ** Preliminary Agenda for IndieUI Task Force Teleconference 12 November 2014
> 
> Meeting: IndieUI Task Force Teleconference
> Chair:Janina_Sajka
> agenda+ preview agenda with items from two minutes
> agenda+ Holliday Scheduling; November-January
> agenda+Checkin with Web Apps' Editing TF [See below]
> agenda+ Editor's Report
> agenda+Requirements & Use Cases Progress
> agenda+Testing Conversation; Polyfills
> agenda+ User Context Issues & Actions 
> https://www.w3.org/WAI/IndieUI/track/products/3
> agenda+ Events Issues & Actions 
> https://www.w3.org/WAI/IndieUI/track/products/2
> agenda+ Other Business
> agenda+Be Done
> 
> Resource: TPAC Minutes
> Monday:http://www.w3.org/2014/10/27-indie-ui-minutes.html
> Tuesday:http://www.w3.org/2014/10/28-indie-ui-minutes.html
> 
> Resource: Teleconference Minutes
> http://www.w3.org/2014/10/15-indie-ui-minutes.html
> 
> Resource: Web Apps Editing TF
> Editing Explainer:http://w3c.github.io/editing-explainer/
> User Intentions:
> http://w3c.github.io/editing-explainer/commands-explainer.html
> Resource: For Reference
> Home Page:http://www.w3.org/WAI/IndieUI/
> Email Archive:http://lists.w3.org/Archives/Public/public-indie-ui/
> 
> Resource: Teleconference Logistics
> Dial the Zakim bridge using either SIP or the PSTN.
> PSTN: +1.617.761.6200 (This is a U.S. number).
> SIP: za...@voip.w3.org
> You should be prompted for a pass code,
> This is
> 46343#
> (INDIE#)
> 
> Alternatively, bypass the Zakim prompts and SIP directly into our
> teleconference.
> SIP: 0046...@voip.w3.org
> 
> Instructions for connecting using SIP:
> http://www.w3.org/2006/tools/wiki/Zakim-SIP
> Place for users to contribute additional VoIP tips.
> http://www.w3.org/2006/tools/wiki/Zakim-SIP-tips
> 
> IRC: server: irc.w3.org, channel: #indie-ui.
> 
> During the conference you can manage your participation with Zakim
> commands as follows:
>   61# to mute yourself
>   60# to unMute yourself
>   41# to raise your hand (enter speaking queue)
>   40# to lower your hand (exit speaking queue)
> 
> The system acknowledges these commands with a rapid, three-tone
> confirmation.  Mobile phone users especially should use the mute
> function
> if they don't have a mute function in their phone.  But the hand-raising
> function is a good idea for anyone not using IRC.
> 
> * IRC access
> 
> An IRC channel will be available. The server is
> irc.w3.org,
> The port number is 6665 (Note this is not the normal default) and
> The channel is #indie-ui.
> 
> * Some helpful Scribing and Participation Tips
> http://www.w3.org/WAI/PF/wiki/Teleconference_cheat_sheet
> 
> For more on the IRC setup and the robots we use for agenda and speaker
> queuing and for posting the log to the web, see:
> 
> - For RRSAgent, that captures and posts the log with special attention
> to action items:
> http://www.w3.org/2002/03/RRSAgent
> 
> - For Zakim, the IRC interface to the bridge manager, that will
> maintain speaker and agenda queues:
> http://www.w3.org/2001/12/zakim-irc-bot
> 
> - For a Web gateway to IRC you can use if your network administrators
> forbid IRC, see:
> http://www.w3.org/2001/01/cgi-irc
> 
> - For more on W3C use of IRC see:
> http://www.w3.org/Project/IRC/
> 
> -- 
> 
> Janina Sajka,Phone:+1.443.300.2200
>sip:jan...@asterisk.rednote.net
>Email:jan...@rednote.net
> 
> The Linux Foundation
> Chair, Open Accessibility:http://a11y.org
> 
> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> Chair,Protocols & Formatshttp://www.w3.org/wai/pf
>IndieUIhttp://www.w3.org/WAI/IndieUI/
>

Re: IndieUI Teleconference Agenda; 1 October at 21:00Z for 60 minutes

2014-09-30 Thread James Craig

Regrets. We’ll be signing mortgage paperwork at this time.


> On Sep 30, 2014, at 3:22 PM, Janina Sajka  wrote:
> 
> Cross-posting as before ...
> 
> What:IndieUI Task Force Teleconference
> When:Wednesday 1 October
> 2:00 PMSan Francisco -- U.S. Pacific (Daylight) Time   (PDT: UTC 
> -7)
> 4:00 PMAustin -- U.S. Central (Daylight) Time   (CDT: UTC -5)
> 5:00 PMBoston -- U.S. Eastern (Daylight) Time  (EDT: UTC 
> -4)
>10:00 PMLondon -- British (Summer) Time (BST: UTC 
> +1)
>11:00 PMParis -- Central European Time  (CET: UTC +2)
> 5:00 AMBeijing -- China Standard Time  (Thursday, 2 
> October CST: UTC +8)
> 6:00 AMTokyo -- Japan Standard Time  (Thursday, 2 October 
> JST: UTC +9)
> Where:W3C Teleconference--See Below
> 
> * Time of day conversions
> 
> Please verify the correct time of this meeting in your time zone using
> the Fixed Time Clock at:
> 
> http://timeanddate.com/worldclock/fixedtime.html?msg=IndieUI+Teleconference&iso=20141001T1700&p1=43&ah=1
> 
> ** Preliminary Agenda for IndieUI Task Force Teleconference 1 October 2014
> 
> Meeting: IndieUI Task Force Teleconference
> Chair:Janina_Sajka
> agenda+ preview agenda with items from two minutes
> agenda+ Editor's Report
> agenda+Clipboard API http://www.w3.org/standards/history/clipboard-apis
> agenda+Checkin with Web Apps' Editing TF [See below]
> agenda+Testing Conversation; Polyfills
> agenda+Requirements & Use Cases Progress
> agenda+ TPAC Planning http://www.w3.org/2014/11/TPAC/
> agenda+ User Context Issues & Actions 
> https://www.w3.org/WAI/IndieUI/track/products/3
> agenda+ Events Issues & Actions 
> https://www.w3.org/WAI/IndieUI/track/products/2
> agenda+ Other Business
> agenda+Be Done
> 
> Resource: IndieUI Minutes
> http://www.w3.org/2014/09/17-indie-ui-minutes.html
> 
> Resource: Web Apps Editing TF
> Editing Explainer:http://w3c.github.io/editing-explainer/
> User Intentions:
> http://w3c.github.io/editing-explainer/commands-explainer.html
> Resource: For Reference
> Home Page:http://www.w3.org/WAI/IndieUI/
> Email Archive:http://lists.w3.org/Archives/Public/public-indie-ui/
> 
> Resource: Teleconference Logistics
> Dial the Zakim bridge using either SIP or the PSTN.
> PSTN: +1.617.761.6200 (This is a U.S. number).
> SIP: za...@voip.w3.org
> You should be prompted for a pass code,
> This is
> 46343#
> (INDIE#)
> 
> Alternatively, bypass the Zakim prompts and SIP directly into our
> teleconference.
> SIP: 0046...@voip.w3.org
> 
> Instructions for connecting using SIP:
> http://www.w3.org/2006/tools/wiki/Zakim-SIP
> Place for users to contribute additional VoIP tips.
> http://www.w3.org/2006/tools/wiki/Zakim-SIP-tips
> 
> IRC: server: irc.w3.org, channel: #indie-ui.
> 
> During the conference you can manage your participation with Zakim
> commands as follows:
>   61# to mute yourself
>   60# to unMute yourself
>   41# to raise your hand (enter speaking queue)
>   40# to lower your hand (exit speaking queue)
> 
> The system acknowledges these commands with a rapid, three-tone
> confirmation.  Mobile phone users especially should use the mute
> function
> if they don't have a mute function in their phone.  But the hand-raising
> function is a good idea for anyone not using IRC.
> 
> * IRC access
> 
> An IRC channel will be available. The server is
> irc.w3.org,
> The port number is 6665 (Note this is not the normal default) and
> The channel is #indie-ui.
> 
> * Some helpful Scribing and Participation Tips
> http://www.w3.org/WAI/PF/wiki/Teleconference_cheat_sheet
> 
> For more on the IRC setup and the robots we use for agenda and speaker
> queuing and for posting the log to the web, see:
> 
> - For RRSAgent, that captures and posts the log with special attention
> to action items:
> http://www.w3.org/2002/03/RRSAgent
> 
> - For Zakim, the IRC interface to the bridge manager, that will
> maintain speaker and agenda queues:
> http://www.w3.org/2001/12/zakim-irc-bot
> 
> - For a Web gateway to IRC you can use if your network administrators
> forbid IRC, see:
> http://www.w3.org/2001/01/cgi-irc
> 
> - For more on W3C use of IRC see:
> http://www.w3.org/Project/IRC/
> 
> -- 
> 
> Janina Sajka,Phone:+1.443.300.2200
>sip:jan...@asterisk.rednote.net
>Email:jan...@rednote.net
> 
> The Linux Foundation
> Chair, Open Accessibility:http://a11y.org
> 
> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> Chair,Protocols & Formatshttp://www.w3.org/wai/pf
>IndieUIhttp://www.w3.org/WAI/IndieUI/
>

Re: IndieUI Teleconference Agenda; 3 September at 21:00Z for 60 minutes

2014-09-03 Thread James Craig

Regrets. I've had another responsibility arise that will prevent me from 
attending today's conference call.


> On Sep 2, 2014, at 1:00 PM, Janina Sajka  wrote:
> 
> As before I'm cross-posting this IndieUI agenda As part of IndieUI's
> continuing open invitation continuing our conversation about working
> jointly.  Allow me to invite you to the next Indie-UI teleconference as
> detailed below.  Please feel free to join us on this call, or any
> following call.
> 
> 
> What: IndieUI Task Force Teleconference
> When: Wednesday 3 September
>2:00 PMSan Francisco -- U.S. Pacific (Daylight) Time   (PDT: 
> UTC -7)
>4:00 PMAustin -- U.S. Central (Daylight) Time   (CDT: UTC -5)
>5:00 PMBoston -- U.S. Eastern (Daylight) Time  (EDT: 
> UTC -4)
>   10:00 PMLondon -- British (Summer) Time (BST: 
> UTC +1)
>   11:00 PMParis -- Central European Time  (CET: UTC +2)
>5:00 AMBeijing -- China Standard Time  (Thursday, 4 
> September CST: UTC +8)
>6:00 AMTokyo -- Japan Standard Time  (Thursday, 4 
> September JST: UTC +9)
>7:00 AMMelbourne -- Australian Eastern (Standard) Time 
>  (Thursday 4 September AEST: UTC +10)
> Where:W3C Teleconference--See Below
> 
> * Time of day conversions
> 
> Please verify the correct time of this meeting in your time zone using
> the Fixed Time Clock at:
> 
> http://timeanddate.com/worldclock/fixedtime.html?msg=IndieUI+Teleconference&iso=20140903T1700&p1=43&ah=1
> 
> ** Preliminary Agenda for IndieUI Task Force Teleconference 3 September 2014
> 
> Meeting: IndieUI Task Force Teleconference
> Chair:Michael_Cooper
> agenda+ preview agenda with items from two minutes
> agenda+ Editor's Report
> agenda+   Checkin with Web Apps' Editing TF [See below]
> agenda+   Testing Conversation; Polyfills
> agenda+   Requirements & Use Cases Progress
> agenda+ TPAC Planning http://www.w3.org/2014/11/TPAC/
> agenda+ User Context Issues & Actions 
> https://www.w3.org/WAI/IndieUI/track/products/3
> agenda+ Events Issues & Actions 
> https://www.w3.org/WAI/IndieUI/track/products/2
> agenda+Other Business
> agenda+   Be Done
> 
> Resource: IndieUI Minutes
> http://www.w3.org/2014/08/20-indie-ui-minutes.html
> 
> Resource: Web Apps Editing TF
> Explainer:http://w3c.github.io/editing-explainer/commands-explainer.html
> Resource: For Reference
> Home Page:http://www.w3.org/WAI/IndieUI/
> Email Archive:http://lists.w3.org/Archives/Public/public-indie-ui/
> 
> Resource: Teleconference Logistics
> Dial the Zakim bridge using either SIP or the PSTN.
> PSTN: +1.617.761.6200 (This is a U.S. number).
> SIP: za...@voip.w3.org
> You should be prompted for a pass code,
> This is
> 46343#
> (INDIE#)
> 
> Alternatively, bypass the Zakim prompts and SIP directly into our
> teleconference.
> SIP: 0046...@voip.w3.org
> 
> Instructions for connecting using SIP:
> http://www.w3.org/2006/tools/wiki/Zakim-SIP
> Place for users to contribute additional VoIP tips.
> http://www.w3.org/2006/tools/wiki/Zakim-SIP-tips
> 
> IRC: server: irc.w3.org, channel: #indie-ui.
> 
> During the conference you can manage your participation with Zakim
> commands as follows:
>   61# to mute yourself
>   60# to unMute yourself
>   41# to raise your hand (enter speaking queue)
>   40# to lower your hand (exit speaking queue)
> 
> The system acknowledges these commands with a rapid, three-tone
> confirmation.  Mobile phone users especially should use the mute
> function
> if they don't have a mute function in their phone.  But the hand-raising
> function is a good idea for anyone not using IRC.
> 
> * IRC access
> 
> An IRC channel will be available. The server is
> irc.w3.org,
> The port number is 6665 (Note this is not the normal default) and
> The channel is #indie-ui.
> 
> * Some helpful Scribing and Participation Tips
> http://www.w3.org/WAI/PF/wiki/Teleconference_cheat_sheet
> 
> For more on the IRC setup and the robots we use for agenda and speaker
> queuing and for posting the log to the web, see:
> 
> - For RRSAgent, that captures and posts the log with special attention
> to action items:
> http://www.w3.org/2002/03/RRSAgent
> 
> - For Zakim, the IRC interface to the bridge manager, that will
> maintain speaker and agenda queues:
> http://www.w3.org/2001/12/zakim-irc-bot
> 
> - For a Web gateway to IRC you can use if your network administrators
> forbid IRC, see:
> http://www.w3.org/2001/01/cgi-irc
> 
> - For more on W3C use of IRC see:
> http://www.w3.org/Project/IRC/
> 
> -- 
> 
> Janina Sajka, Phone:  +1.443.300.2200
>   sip:jan...@asterisk.rednote.net
>   Email:  jan...@rednote.net
> 
> The Linux Foundation
> Chair, Open Accessibility:http://a11y.org
> 
> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> Chair,Protocols & Formats http://www.w3.

Re: User Intentions Explainer (was: List of Intentions)

2014-08-08 Thread James Craig

From: Julie Parent 
>  
>> This is a great list, and I agree it is the right starting point.
>> 
>> On Mon, Jul 21, 2014 at 6:12 PM, Ben Peters  wrote:
>>> * Activate / Invoke 
>>> 
>>>  * Expand
>>>  * Collapse
>>>  * Dismiss
>>>  * Media next/previous/start/stop/pause
>>>  * Rotate
>>>  * Zoom
>>>  * Value change
>> 
>> Is this the set from indie-ui?  I think we should make a decision if we are 
>> trying to cover these cases or not, as they do not make sense in the context 
>> of rich text editing and might be out of scope.

Sorry Julie, I didn't see your original email. Perhaps you removed the 
cross-posted lists? I'm on both IndieUI and WebApps, but didn't see it come 
through.

With the possible exception of the media events, all of the above events make 
sense in the context of editing. For example, in Word or Pages:

1. You can "expand" or "collapse" sections of a document.
2. You can "zoom" in on the document view. 
3. You can "rotate" an embedded photo or chart. 
4. You can "scale" a variety of elements by focusing on a corner handle (e.g. 
drag handle) and nudging it with arrow keys, or a mouse, or by touch. These can 
be modified in some apps. For example, option+arrow moves this handle by a 
smaller amount than unmodified arrow keys. This is a use case for either 
"scale" on the main object, or "value change" on the corner control.

>> It would help to have a list of arguments for/against merging with indie-ui?

I don't know if the arguments need to be about merging working groups. I don't 
care where the work happens, as long as it happens. I'd be fine with disbanding 
IndieUI if WebApps is ready to take up the work, but text editing is only one 
piece of it. IMO, it doesn't make sense to design one API for text editing, and 
another API for graphic manipulation, and another for form manipulation. 

One of the use cases that was deferred from the 1.0 version of IndieUI was to 
"mark" for some later action. For example, in a text editor, click in one spot, 
then shift+click in another to select a range of text. The next action (such as 
Delete) applies to the selection. On most desktop platforms, this works with 
text selection, but also on collections like table views: click then 
shift+click to select multiple songs in a music player, or multiple messages in 
an email inbox. 

INDIEUI-ACTION-25: Add markRequest with variant properties indicating 
"fromLast" (like Shift+click or select range from last mark) and "retainMarks" 
(like Mac Cmd+click or Win Ctrl+click meaning select in addition to)

https://www.w3.org/WAI/IndieUI/track/actions/25

Hopefully these examples demonstrate how overlapping the work is. It'd be 
tempting to limit the scope to text editing, but I feel that'd ultimately be 
short-sighted.

James

-- 
Indifference towards people and the reality in 
which they live is actually the one and only 
cardinal sin in design. — Dieter Rams

Re: [coord] Request for Inter-Group Coordination at TPAC

2013-11-08 Thread James Craig

Here’s the updated draft we’ll be discussing in Monday’s meeting. FWIW, It’s a 
ground-up rewrite since last week, so it’s still loaded with todos and 
editorial notes.
https://dvcs.w3.org/hg/IndieUI/raw-file/default/src/indie-ui-context.html#toc

I know many of you are traveling, so if you don’t have time to do a thorough 
review before then, I’d suggest spending 5 minutes to read the Introduction and 
then Section 1.1, including the example in 1.1.2 “Example restricted call to 
matchMedia”… Thanks for your consideration.

On Nov 1, 2013, at 7:59 AM, James Craig  wrote:

> + public-webapps
> 
>> On Nov 1, 2013, at 7:44 AM, James Craig  wrote:
>> 
>> Hi Art.
>> 
>>> On Nov 1, 2013, at 5:32 AM, Arthur Barstow  wrote:
>>> 
>>> To help WebApps prepare for the discussion, I think it would be helpful if 
>>> you would please provide some background information. For example, the URL 
>>> of the "IndieUI User Context specification", the "proposal for a new way 
>>> for user agents to restrict access to certain groups of media resources".
>> 
>> The new approach we’re hoping to discuss is pretty new, so these aren’t in 
>> spec form yet. I’m hoping to change that before TPAC.
>> 
>> The current editor’s draft still has the old key/value pair approach (which 
>> we’d decided to scrap), and can be found here:
>> 
>> https://dvcs.w3.org/hg/IndieUI/raw-file/default/src/indie-ui-context.html

Re: [coord] Re: Request for Inter-Group Coordination at TPAC

2013-11-01 Thread James Craig

+ public-webapps

> On Nov 1, 2013, at 7:44 AM, James Craig  wrote:
> 
> Hi Art.
> 
>> On Nov 1, 2013, at 5:32 AM, Arthur Barstow  wrote:
>> 
>> To help WebApps prepare for the discussion, I think it would be helpful if 
>> you would please provide some background information. For example, the URL 
>> of the "IndieUI User Context specification", the "proposal for a new way for 
>> user agents to restrict access to certain groups of media resources".
> 
> The new approach we’re hoping to discuss is pretty new, so these aren’t in 
> spec form yet. I’m hoping to change that before TPAC.
> 
> The current editor’s draft still has the old key/value pair approach (which 
> we’d decided to scrap), and can be found here:
> 
> https://dvcs.w3.org/hg/IndieUI/raw-file/default/src/indie-ui-context.html

[ime-api] Re: FYI: new WD of Input Method Editor API published

2013-08-16 Thread James Craig

On Aug 16, 2013, at 5:44 AM, Arthur Barstow  wrote:

> You may recall WebApps and PFWG discussed WebApps' Input Method Editor API 
> last April ([Mins]). As such, I wanted to let you know a new WD of that spec 
> was published on August 15: 
> 
> If you have any comments, please send them to the public-webapps @ w3.org 
> list.
> 
> -Regards, ArtB
> 
> [Mins] 
> 

This draft is much improved, but I still have one concern:

This code sample makes it clear you intend to do custom rendering of the 
suggestions list…

> // Render new suggeston list.
> for (i = 0; i < candidates.length; i++) {
> suggest.appendChild(document.createElement('li'));
> suggest.childNodes[i].textContent = candidates[i];
> }

But it's not apparent to me how you're alerting the user agent to avoid 
rendering the native candidate suggestions. It's also not clear to me how, 
depending on user preference, the user agent would respond to let the web 
application know that custom rendering is not allowed in this context or for 
this user. 

I'd expect something like this conditional to confirm with the UA that it's 
okay for the web app to do custom rendering of the candidates.

// check with the UA to see if web app can render custom suggestions list
if (target.inputMethodContext.preventDefaultRendering()) {
// Render new suggeston list.
for (i = 0; i < candidates.length; i++) {
   suggest.appendChild(document.createElement('li'));
   suggest.childNodes[i].textContent = candidates[i];
}
} // else custom rendering is disallowed by the UA

Re: IndieUI Teleconference Agenda; 17 December at 22:00Z for 60 minutes

Re: IndieUI Teleconference Agenda; 12 November at 22:00Z for 60 minutes

Re: IndieUI Teleconference Agenda; 1 October at 21:00Z for 60 minutes

Re: IndieUI Teleconference Agenda; 3 September at 21:00Z for 60 minutes

Re: User Intentions Explainer (was: List of Intentions)

Re: [coord] Request for Inter-Group Coordination at TPAC

Re: [coord] Re: Request for Inter-Group Coordination at TPAC

[ime-api] Re: FYI: new WD of Input Method Editor API published

8 matches

Site Navigation

Mail list logo

Footer information