Bug Tracker

Ticket #14645 (closed bug: fixed)

Opened 7 months ago

Last modified 7 months ago

Remove global exposure for CommonJS environments with a document

Reported by: timmywil Owned by: timmywil
Priority: blocker Milestone: 1.11/2.1
Component: core Version: 2.1.0-beta2
Keywords: Cc:
Blocking: Blocked by:

Description

Browser emulators still need the globals, but we can use the same check we use on load to limit global exposure for the most common CommonJS use cases.

Change History

comment:1 Changed 7 months ago by timmywil

  • Owner set to timmywil
  • Priority changed from undecided to blocker
  • Status changed from new to assigned
  • Component changed from unfiled to core
  • Milestone changed from None to 1.11/2.1

comment:2 Changed 7 months ago by Timmy Willison

  • Status changed from assigned to closed
  • Resolution set to fixed

exports/global: Do not attach global variables for most CommonJS environments

For CommonJS environments where the global already has a document, it is expected that if a global is needed, the user can attach the global.

Fixes #14645.

Changeset: e0fad093b63d2d197a9c59ccce8896d75a83c95e

Note: See TracTickets for help on using tickets.