Re: [w3ctag/design-reviews] Display Locking (#306)

@kenchris and I are looking at this during the Wellington face-to-face.

We filed a bunch of issues (above) on subtree visibility.

@kenchris is concerned about the name of `contain-intrinsic-size` being unclear, i.e., sounding more like a boolean than a property that sets an intrinsic size but only when containment is used.  (I'd still like to see the more general `intrinsic-size` property, though I don't recall right now what the issues blocking that were.)

We didn't get to look at the [`beforematch` event explainer](https://github.com/WICG/display-locking/blob/master/explainer-beforematch.md) as much as we should, but we should do so in the future.  Though in addition to the privacy concerns mentioned in that explainer (and perhaps others) I think we should think about whether this model might interfere with the development of future user-agent features that don't exist yet (compared to the existing find-in-page feature that is handled there).  Also, when starting to read that explainer I was expecting it to have a feature that allowed addition of content that had been excluded for performance reasons... whereas it actually doesn't seem to be about that sort of thing, but instead about content that the user couldn't currently scroll to, for example because it's in a collapsed section.  Or am I misunderstanding?

-- 
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/306#issuecomment-593727549