Re: IndieUI Teleconference Agenda; 23 July at 21:00Z for 60 minutes

2014-07-22 Thread Andy Heath
I can't be there (apols) but can I request an Agenda+ to look at potential 
other meeting days/times - I've mailed my availabilities to Janina and to Rich 
-Andy 

Sent from my iPhone

 On 22 Jul 2014, at 01:20, Janina Sajka jan...@rednote.net wrote:
 
 What:IndieUI Task Force Teleconference
 When:Wednesday 23 July
 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, 24 July 
 CST: UTC +8)
 6:00 AMTokyo -- Japan Standard Time  (Thursday, 24 July 
 JST: UTC +9)
 7:00 AMMelbourne -- Australian Eastern (Standard) Time  
 (Thursday 24 July 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+Teleconferenceiso=20140723T1700p1=43ah=1
 
 ** Preliminary Agenda for IndieUI Task Force Teleconference 23 July 2014
 
 Meeting: IndieUI Task Force Teleconference
 Chair: Janina_Sajka
 agenda+ preview agenda with items from two minutes
 agenda+ TPAC 2014 http://www.w3.org/2014/11/TPAC/
 agenda+ Editor's Report
 agenda+Prospects with Web Apps' Editing TF [See below]
 agenda+Testing Conversation
 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/07/09-indie-ui-minutes.html
 
 Resource: Web Apps Editing TF
 Minutes:http://www.w3.org/2014/07/11-webapps-minutes.html
 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  Formatshttp://www.w3.org/wai/pf
IndieUIhttp://www.w3.org/WAI/IndieUI/
 



Re: [HTML Imports] What is the imagined work flow?

2014-07-22 Thread Brian Di Palma
Correct, you wouldn't always want to add it to the document head.

Yes I see there would still be semantic issues...I guess the
safest/easiest way would be to have the developer state what type the
resources are.
How you would do that in a clean fashion I'm not sure...


On Wed, Jul 2, 2014 at 4:09 PM, Ryosuke Niwa rn...@apple.com wrote:
 On Jul 2, 2014, at 3:57 AM, Brian Di Palma off...@gmail.com wrote:

 I'm happy to hear that it seems natural to trigger resource loading
 within a module.

 For example, I could imagine adding a new syntax for loading an arbitrary 
 sub resource dependency.

 Absolutely. I think the platform could provide much better syntax then
 these examples.

 ```
 import '../style/index.css!';
 import spaApplicationTemplate from '../template/spaApplication.text!';
 ```

 As devs can't really create new syntax we are forced to work with the
 existing syntax.
 It's not pretty but the CSS/LESS/text etc plugins from SystemJS
 https://github.com/systemjs/systemjs/#plugins do the job.

 Possibly the right syntax would also address the semantic issues that
 were pointed out.

 It's not explict but the imported CSS was added to the document head,
 so maybe something like

 Do you really want to always add it to head though?  In the case of defining 
 your own element, don't you want to add it to your custom element's shadow 
 DOM?

 ```
 import '../style/index.css' into document;
 ```

 Would make it more explicit?

 ```
 import '../style/index.css' into customElementTemplate;
 ```

 Is another possibility.

 I think the semantics issue or rather ambiguity we pointed out is still in 
 the example above.  Unless we rely on mime type information provided by the 
 server, we can't figure out what kind of a  resource we're loading (is it 
 CSS, HTML, or JSON?).  We might want to be more explicit in that regard.

 - R. Niwa



[clipboard] Semi-Trusted Events Alternative

2014-07-22 Thread Ben Peters
Semi-trusted events in the Clipboard API spec [1] are a potential solution to 
an important problem- sites should be able to use the same infrastructure 
(clipboard events) with their own triggers (button with execCommand('paste') as 
browser initiated clipboard operations (like user presses control+v or uses the 
context menu's 'paste' option). However, I don't really know if 'semi-trusted' 
events are the solution. Users will almost certainly be using the keyboard or 
mouse with websites, so requiring an event to originate from keyboard or mouse 
doesn't seem to make them trusted at all. I know there has been some discussion 
of removing them from the spec [2]. What is the status of that?

As an alternative to semi-trusted events, perhaps we should have something 
similar to input type=file? Perhaps a new input type that must display a 
localized word for cut, copy, or paste, and must not be occluded by any 
other element, could trigger real, trusted clipboard events? I'm not sure how 
this would work, but it seems worth a discussion at least.

Ben

[1] http://www.w3.org/TR/clipboard-apis/#semi-trusted-events
[2] http://lists.w3.org/Archives/Public/public-webapps/2014AprJun/0086.html


[Bug 26394] [imports]: the |import| attribute returns null if the UA does not support imports?

2014-07-22 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26394

Morrita Hajime morr...@google.com changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||morr...@google.com
 Resolution|--- |FIXED

--- Comment #2 from Morrita Hajime morr...@google.com ---
Makes sense. It sounds like we don't have to mentions about that.
https://github.com/w3c/webcomponents/commit/5116d7cce28542e2476f0800d1a1e6ef3c38de28

-- 
You are receiving this mail because:
You are on the CC list for the bug.