[Bug 24351] New: [Shadow]: Event related target resolution algorithm should consider the case of multiple shadow roots.

2014-01-21 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24351

Bug ID: 24351
   Summary: [Shadow]: Event related target resolution algorithm
should consider the case of multiple shadow roots.
   Product: WebAppsWG
   Version: unspecified
  Hardware: PC
OS: All
Status: NEW
  Severity: normal
  Priority: P2
 Component: Component Model
  Assignee: dglaz...@chromium.org
  Reporter: hay...@chromium.org
QA Contact: public-webapps-bugzi...@w3.org
CC: m...@w3.org, public-webapps@w3.org
Blocks: 14978

Event retargeting algorithm for multiple shadow trees was fixed in
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23769.

In the next, we have to update the related target resolution algorithm slightly
for multiple shadow trees.

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



Re: I need some guidance.

2014-01-21 Thread aga
I take it this is about ordinary HTTP caching behavior, not about, 
say,

"appcache", correct?
Yes.

Also, it seems the issue is that you tell browsers not to cache a 
resource, and then expect it to be cached anyway.
I tell the browser to check for freshness on page load. I expect that 
the resource is cached in the current instance (before any new page 
refreshes occur). So, yes, I expect it to be cached on any subsequent 
request before a page request, but no, I expect it is not cached on any 
subsequent refresh.


In any case, a better forum for the problem might be a group 
specialising in HTTP caching questions.
That's just it.. is saving image data before a page refresh occurs 
considered "caching"?





[Bug 24349] New: [imports]: Import documents should always be in no-quirks mode

2014-01-21 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24349

Bug ID: 24349
   Summary: [imports]: Import documents should always be in
no-quirks mode
   Product: WebAppsWG
   Version: unspecified
  Hardware: PC
OS: All
Status: NEW
  Severity: normal
  Priority: P2
 Component: Component Model
  Assignee: dglaz...@chromium.org
  Reporter: dfre...@google.com
QA Contact: public-webapps-bugzi...@w3.org
CC: m...@w3.org, public-webapps@w3.org
Blocks: 20683

HTML Imports can provide a clean break from the subtle differences between
quirks and no-quirks modes by enforcing no-quirks mode for all imported
documents.
Effectively, this would be saving developers from having to type  at the beginning of each and every import.

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



[Bug 24101] Missing word in "Return the readAsText() method, but continue to process the steps in this algorithm"

2014-01-21 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24101

Arun  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

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



Re: [admin] Draft of updated charter available for review

2014-01-21 Thread Marcos Caceres

Quick notes, questions 

Is "File API: Directories and System" dead? Looks kinda dead (last updated 07 
March 2012). 

Streams should not be part of File - it's a generic API for any data. 

"UI Events" is linked to the wrong place. 

Drop the "currently not supported by web standards." from Gamepad 
description... as it's a bit of an oxymoron to have a standard for a standard 
that's not supported as a standard... standard :) 

Ooohhh! WebApps staking a claim over "Service Workers"! Nice :) 

URL API should point to http://url.spec.whatwg.org/

Can we please put an end to this whole snapshot nonsense:
https://dvcs.w3.org/hg/xhr/raw-file/tip/Overview.html

Maybe drop: "public-web-inte...@w3.org (archive) for discussion of the Web 
Intents specification"

-- 
Marcos Caceres


On Tuesday, January 21, 2014 at 8:36 PM, Arthur Barstow wrote:

> Hi All,
> 
> Although WebApps' current charter [Charter] does not expire until the 
> end of May, since it can take a while to agree on a new charter 
> (especially if new deliverables are proposed), I created a Draft [Draft] 
> today. A diff of the current charter vs. the draft is available at [Diff].
> 
> My intent was to reflect the current state of WebApps' work and I don't 
> think there are any major surprises.
> 
> Comments (as well as PRs) are welcome, especially if anyone has any 
> deliverables to propose.
> 
> -Thanks, ArtB
> 
> [Charter] 
> [Draft] 
> [Diff] 
> 






[admin] Draft of updated charter available for review

2014-01-21 Thread Arthur Barstow

Hi All,

Although WebApps' current charter [Charter] does not expire until the 
end of May, since it can take a while to agree on a new charter 
(especially if new deliverables are proposed), I created a Draft [Draft] 
today. A diff of the current charter vs. the draft is available at [Diff].


My intent was to reflect the current state of WebApps' work and I don't 
think there are any major surprises.


Comments (as well as PRs) are welcome, especially if anyone has any 
deliverables to propose.


-Thanks, ArtB

[Charter] 
[Draft] 
[Diff] 






[Bug 24102] Specify the targets for events

2014-01-21 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24102

Anne  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 CC||ann...@annevk.nl
 Resolution|INVALID |---

--- Comment #3 from Anne  ---
Reopening. A task source is not an event target. You should probably introduce
an IO task source for tasks. The event target should be the FileReader object
(at least for the events dispatched to it).

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



[Bug 24102] Specify the targets for events

2014-01-21 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24102

Arun  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |INVALID

--- Comment #2 from Arun  ---
Marking this bug closed, since there isn't a response to Comment 1.

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