Shu-yu Guo

@michaelficarra All of the editorial choices in https://github.com/tc39/ecma262/pull/2821#issue-1299519833 seem to be strictly speaking unrelated to nailing down a definition of identity. It'd be easier to review some of those as...

One thing we can do is to make content-visibility a mobile-only style to aid Android readers, where the scrollbar discontinuity is less jarring.

> (Drive by comment: You could even grab these heights via puppeteer at a bunch of different screen widths and set them accordingly with media queries) I thought the problem...

Hm, on Chrome 87 on Mac I don't get a scrollbar at all anymore in the after (https://mathiasbynens.github.io/ecma262-layout-chunking/after.html#sec-string.prototype.replaceall) version. Is that supposed to be the case?

This is a great suggestion. I'm especially excited about generalizing suggestion 2 to explicitly list out all the vtables of the objects that override internal method. Will take a stab...

The conclusion from the editor call is that Uint53-string and Uint32-string are not good names. While more clarity could be useful here, until better names are proposed, the churn here...

> I don’t really like the term “identity” here, because to me, everything has identity, it’s just that there’s only ever one 3 - all 3’s are the same 3....

> Alternative is to put it in localStorage, so it's also preserved when you come back to it. That means it's not linkable, though. Maybe both?

> All used operations are defined This would need to be amended for AOs that are only called upstream, but at least it would force us to enumerate such AOs.

Yeah that strongly argues for codifying it in Annex B. Can't say I'd consider this to be high priority, but all other things being equal we should reflect reality.