Minutes Telecon 2020-12-02
- On the next call the group will decide when to hold our next virtual F2F. Anyone with thoughts in can send them to the private list or come prepared to discuss on the next call
- The group discussed if creating a way to indicate content which is not currently visible should be searchable is a problem they want to solve before going into details of if the proposed content-visibility: hidden-matchable property is the right way to do it. (Issue #5595: Proposal: content-visibility: hidden-matchable).
- The main concern expressed with such a property is that it removes the optimizations allowed by visibility:hidden and display:none and could therefore be expensive to the browser.
- One suggestion to address it was to allow the content which is content-visibility:hidden-matchable to be lazy-indexed instead of being indexed on first load.
- Discussion on this and the rest of the issue will continue on GitHub
- Resolved: Have separate keywords for the visible and contained value vs initial value (Issue #5695: Apply containment on `content-visibility: visible` ; use `normal` as initial value)
- The name of the properties will be discussed further on GitHub and then brought back to the group.
- miriam introduced the current status on the discussion for 1 dimensional container queries (Issue #1031: Do we need size containment in a single dimension to enable container queries?).
- There are two different, and not necessarily mutually exclusive, solutions being discussed:
- The “pinky promise” solution where when you get the width of the container query you say that you won’t do any of the behaviors which would change the width later.
- The “plug the leaks” solution is to address issues as they’re discovered. Currently, there are only two known issues both of which have potential solutions. Given that people have been thinking about this for a while and only found two issues, it’s likely that there aren’t many more leaks which are unknown.
- Both solutions were discussed and both could be viable solutions. Discussion will continue on GitHub.
- Resolved: Invalid path strings make the syntax invalid at parse time (FXTF Issue #392: The computed value of offset-path: path(‘ ‘))
- Resolved: Empty path is considered invalid (FXTF Issue #392)
- The desire with spelling-error and grammar-error is to create some spec text which says UAs may take steps to prevent fingerprinting and give disallowing loading external resources as an example. Fantasai will draft up sample language for the group to discuss and resolve on. (Issue #5731: Privacy considerations for external resources)
- Resolved: The contain-intrinsic-size property takes 4 longhands, logical and physical, which have a normal value (Issue #5432: Allow specifying only one dimension for intrinsic sizing)
- A separate issue will be opened on github about if there is value in defining a ‘none’ property for contain-intrinsic size.
Full Meeting Minutes
« Previous article
Next article »