If criteria 2 + 3 (the scroll-related ones) are removed, I don't see a big benefit in expanding the syntax beyond the current "none | strict" values. Being said, I'm not sure I fully understand the impact of those new generated content properties. Also, are there any problems with SVG-esque stuff, like imported clip paths? Say "#shape" was defined within a "contain: strict" element - could it be referenced outside that element? Charley On Fri, Dec 6, 2013 at 5:09 PM, Ojan Vafai <ojan@chromium.org> wrote: > On Fri, Dec 6, 2013 at 4:30 PM, Ojan Vafai <ojan@google.com> wrote: > >> On Wed, Dec 4, 2013 at 5:59 PM, Robert O'Callahan <robert@ocallahan.org>wrote: >> >>> On Thu, Dec 5, 2013 at 9:29 AM, Ojan Vafai <ojan@google.com> wrote: >>> >>>> On Tue, Dec 3, 2013 at 8:15 AM, Tab Atkins Jr. <jackalmage@gmail.com>wrote: >>>> >>>>> On Mon, Dec 2, 2013 at 7:36 PM, Robert O'Callahan < >>>>> robert@ocallahan.org> wrote: >>>>> > I believe restrictions 2 and 3 should be dropped. >>>>> >>>>> Let's let some of the engineers that asked me for this restriction to >>>>> chime in first. >>>>> >>>> >>>> I'm OK with dropping it. As an overflow property, it would have been >>>> nice to be able to implement the clipping purely at paint time, >>>> >>> >>> What is the benefit of that? >>> >> >> The benefit is not large. It would just simplify our implementation some. >> As I said, I'm fine dropping it. >> > >
Received on Wednesday, 11 December 2013 01:33:53 UTC