Change window.context API to avoid problematic terms

Description

Contributor guide

Tech stack

javascriptweb components

Domain

developer experience

Issue type

refactor

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-2 days

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

stale

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

clear

Prerequisites

JavaScriptAMP framework knowledgebackwards compatibility patterns

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

50

Research direction

Review the existing window.context API definition and all its usages across the codebase. Identify the new name to replace the problematic term, then implement an alias to maintain backward compatibility. Ensure tests pass and update documentation if needed. Check comments in the issue for any suggested naming or additional requirements.