Philip Rogers

Thank you for taking the time to file this. You're absolutely right that this is a bug but I'm leaning towards keeping this bug for pragmatic reasons. Many (all?) folks...

Emil (eae) and I were looking at graphs today and they still seem to be inflated. Should this have been fixed or did this bug surface again?

A lot of them are over 100%: https://www.chromestatus.com/metrics/css/popularity For example, `display` is reported as being on ~150% of pages: https://www.chromestatus.com/metrics/css/timeline/popularity/4

Thanks for the quick response. If I understand correctly, this will be fixed when M69 is promoted to stable (near the end of this month)?

In https://crbug.com/647594#c17 it was found that ``, ``, ``, and `` are not included in elementsFromPoint by Chromium and Gecko. Elements with the equivalent `display` values (`display: table-row`, `display: table-row-group`,...

@tigt , that was definitely the case recently and I remember folks hitting issues with the cross browser support. It looks like things have changed recently though. I just checked...

It's not a complete veto for svg. The heuristic is based on the absolute number of non-convex paths. There are two ongoing projects in progress now that will likely remove...

WPT can use either `.html` or `.svg`, and [no-background.svg](https://github.com/web-platform-tests/wpt/blob/ea980464c32f84fcdfc1d13d3f04eef19cf298f2/svg/text/reftests/no-background.svg?short_path=117b5d6) is a random example of a `.svg` test in the WPT repository. Many of the SVG tests in WPT do use...

In addition to device pixel ratio, we also cannot test OS settings such as the OS font scale setting of the device.

I agree that the spec says that the border should be included. It looks like matching Safari/WebKit was one of the original reasons for this change in https://github.com/w3c/fxtf-drafts/pull/342.