Change window.context API to avoid problematic terms
We will still need to maintain backwards compatibility, so will likely alias to the new name.
to/ @ampproject/wg-monetization
I'd suggest adding window.coordinator as an alias for window.master
and computeInCoordinatingFrame for computeInMasterFrame
Hello, I took up to change computeInCoordinatingFrame to computeInMasterFrame. Didn't find any instances of window.master though. Could you please check my PR? https://github.com/ampproject/amphtml/pull/38107
Please ignore what I did, instead of creating an alias I just renamed it.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.
is this issue fixed
Oke
how can i work on this issue as I am new
hey how can I work upon this issue. Can you brief me about it?
refactor: add window.coordinator as alias to window.context for inclusive naming
Added window.coordinator as an alias to window.context to support more inclusive terminology, while maintaining backward compatibility.
Refs: #30789
Thanks for raising this, @calebcordry . I understand that we need to replace the ambiguous or we can say problematic window.context naming with a more inclusive term (e.g. aliasing it to window.coordinator) while preserving backwards compatibility. I’d be happy to implement this assign this issue to me and I’ll get started on a PR.
Can I solve this?
I think you can solve this
Hello, I’m new to contributing to this project and would love to take this issue as my first PR. Could I be assigned to it if this still open?
Hello, Is the issue resolved , I want to fix this issue.
Could I be assigned to it if this still open?
Replacing window.master with window.coordinator
Replacing computeInMasterFrame with computeInCoordinatingFrame
Maintaining backward compatibility by aliasing old names to new ones