Rick Byers

Talking more with @foolip, I think maybe "browser-specific" is fine as it is - it's what we want for our use case of talking to chromium teams about APIs they've...

Let's start tracking here the expressions we want: - `document.body.style` (just to make absolutely sure CSSStyleDeclaration shows up, though it's probably redundant) - `new DOMException()` - to work around Safari's...

BTW I appreciate that there's probably no good way to count each of the different methods on `runtime` as their own API (since `runtime` doesn't appear to be an instance...

As far as I can see, these APIs are exposed basically the same on Chrome and Safari. I think understanding why this difference exists is urgent (to understand the extent...

Ah, I forgot about that constant elimination heuristic - thanks. At some point we should document all these heuristics and the arguments behind them somewhere, I'm sure we'll keep wanting...

@foolip how many APIs do you expect this impacts? IIRC it's rather rare, so probably not very urgent to account for, right?

@arronei (Edge API catalog guy) says he's in the process of adding these to the Edge API catalog - about 701 symbols in all, 69 if you exclude `Symbol.toStringTag`.

+1. Especially now that Chrome is marking HTTP "Not secure". I find myself having to remember to manually add https:// prefixes to confluence URLs before I share them (for whatever...

@mattl having Edge Android would be cool, but if they're telling the truth about using unmodified blink then we shouldn't learn anything (should match Chrome Android exactly for the corresponding...

Yeah, that's the default configuration for Chrome, though should probably [be tweaked](https://bugs.chromium.org/p/chromium/issues/detail?id=392584). I think the fundamental issue here is that we don't run on Android (or in a mode where...