- From: Ian Clelland <notifications@github.com>
- Date: Thu, 01 Feb 2018 11:26:02 -0800
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 1 February 2018 19:26:29 UTC
My original rationale for making this separate from feature policy was that you might have a situation where: * the top-level page does not want to delegate any gestures it receives to its subframes * one of those subframes wants to delegate gestures that **it** receives to its own children By using feature policy as the mechanism for gesture delegation, that isn't possible. Once the feature is disabled by the top-level page, there is no way for a subframe to turn that feature on for itself or its own children. This is, I think, the right behaviour for most features -- for things like fullscreen, geolocation, or camera, you don't want subframes to be able to re-enable them once disabled. For an attribute like this, which is more about defining the relationship between a frame and its immediate children, it makes less sense as a restriction. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/199#issuecomment-362374568
Received on Thursday, 1 February 2018 19:26:29 UTC