On Wed, Nov 12, 2014 at 12:36 PM, Dimitri Glazkov
wrote:
> Nevertheless, I am optimistic. I would like to have this discussion and
> hear your ideas.
>
OK. The following ideas are somewhat half-baked so don't judge me too
harshly :-).
Rapid deployment of experimental APIs in the browser clashes
LOL. Its the first one I've been able to get on for months. Shame is I
came back early from something personal for it (my phone was too
battery-low to get email so I didn't know it was cancelled).
Never mind, see you next week.
andy
After discussion with Janina, we've had enough regrets on a
On Wed, 12 Nov 2014, Mike West wrote:
>
> The CSP spec should just delegate to HTML here. If/when HTML defines
> sandboxing with regard to Workers, CSP will just start using those
> hooks.
>
> I'd agree, for example, that it does appear that sandboxing a worker
> into a unique origin could be i
I believe we should design this with multiple Ranges in mind. Otherwise
multiple selection requires a lot of work in javascript. Even if we don't
actually support multi-selection in V1, we should not block it for a future
spec.
-Original Message-
From: Joanmarie Diggs [mailto:jdi...@iga
Hi all.
The current draft of the Selection API states:
This specification follows non-Gecko engines in restricting
selections to at most one range, but the API was still originally
designed for selections with arbitrary numbers of ranges. This
explains oddities like the coexistenc
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25223
Jonas Sicking changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
After discussion with Janina, we've had enough regrets on and off list
that it seems we won't have quorum for today's IndieUI call. Therefore,
we will postpone the call to next week. The next IndieUI call will be:
Wednesday, 19 November
at the usual time.
Michael
On 11/11/2014 8:44 PM, Janin
+1
Mike West writes:
> The CSP spec should just delegate to HTML here. If/when HTML defines
> sandboxing with regard to Workers, CSP will just start using those hooks.
Reasonable, the issue also appears outside CSP: if I create a worker in
a sandboxed iframe, what should its origin be? (Or sho
The CSP spec should just delegate to HTML here. If/when HTML defines
sandboxing with regard to Workers, CSP will just start using those hooks.
I'd agree, for example, that it does appear that sandboxing a worker into a
unique origin could be interesting. It's not clear to me whether any of the
oth
On Thu, Nov 6, 2014 at 5:10 AM, Deian Stefan wrote:
> I am implementing CSP for Workers in Firefox, but like to get a
> clarification on workers and the sandbox flag. Currently, a Worker can
> inherit or be accompanied by a CSP header. As written, the implications
> of the sandbox directive on the
10 matches
Mail list logo
