@Elchi3 could I tempt you into preparing the content-side change for this, since you already did a whole lot of these and know all the bits to update?

I'm happy to help with the content work on this one but it runs into the same problem that I also ran into with crypto: The namespace is already occupied. (see #11518 (comment))

Here, performance also conflicts with the interface: https://developer.mozilla.org/en-US/docs/Web/API/Performance

Oh, I didn't realize this would happen, that MDN URLs are case-insensitive... any ideas for how to resolve this?

Oh, I didn't realize this would happen, that MDN URLs are case-insensitive... any ideas for how to resolve this?

No yet. One could have an MDN URL like performance_global. Other ideas?

Could we disambiguate "Performance (interface)" and "performance (property)" Wikipedia-style? One of them should probably be very minimal and just link to the other.

I'm not a big fan of disambiguation pages. I think the current Performance (interface) page is great and having a disambiguation in its place wouldn't be ideal, imo. Or where do you propose that such disambiguation would happen?

I agree the page with all the Performance members is the best place to land. How about https://developer.mozilla.org/en-US/docs/Web/API/Performance stays the same but https://developer.mozilla.org/en-US/docs/Web/API/performance_property is added?

Perhaps more radical would be to just have one page and not use the BCD for api.performance at all, since it should match api.Performance.

I agree the page with all the Performance members is the best place to land. How about https://developer.mozilla.org/en-US/docs/Web/API/Performance stays the same but https://developer.mozilla.org/en-US/docs/Web/API/performance_property is added?

I think this is a good idea.

@Elchi3 do you think this change would be trivial on the MDN side, or is something novel needed for the first some_property page?

I've exercised the change in mdn/content#9279. I think it could work as proposed.