- From: Greg Whitworth via GitHub <sysbot+gh@w3.org>
- Date: Sun, 24 Feb 2019 05:56:48 +0000
- To: public-css-archive@w3.org
Ok, so after discussing this at length with @atotic and taking into account the valid feedback from @bfgeek regarding stale information we've come up with two potential shapes this API can take. The question comes down to: **Do we only return the information for the box being observed, or do we return all potentially observable boxes but only fill in layout information of the box actively observed?** **Option A:** ``` entry = { target: <Element>, contentRect: {/* v1 for back compat */}, inline: 400, block: 400 } ``` **Option B:** ``` entry = { target: <Element>, contentRect: {/* v1 for back compat */}, contentBox: null, borderBox: { inline: 400, block: 400 }, scrollBox: null } ``` _Note: This does not show offset information by design as that will be discussed in issue #3550 - if we resolve to add the offsets those will go alongside `inline` & `block`, no matter which shape we decide on._ _Note 2: How fragmentation will be supported is being looked at in issue #3673 and we will adjust the shape further based on the outcome of that discussion_ -- GitHub Notification of comment by gregwhitworth Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3329#issuecomment-466737070 using your GitHub account
Received on Sunday, 24 February 2019 05:56:49 UTC