[Web API type definition issue] securitypolicyviolation event in WorkerGlobalScope should be typed as SecurityPolicyViolationEvent

Open
#2,123 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
api

Research direction

Start by comparing the WorkerGlobalScope securitypolicyviolation event with the linked MDN documentation and the existing SecurityPolicyViolationEvent definition. Trace how this Web API type is generated, then verify that the event exposes SecurityPolicyViolationEvent properties such as violatedDirective and blockedURI instead of only generic Event members.

Written by the indexing model from the issue text.

Description

lib.d.ts bug
Summary

Missing Type for SecurityPolicyViolationEvent in WorkerGlobalScope

Expected vs. Actual Behavior

securitypolicyviolation event in WorkerGlobalScope should be typed as SecurityPolicyViolationEvent

According to the MDN documentation, the securitypolicyviolation event in WorkerGlobalScope should provide a SecurityPolicyViolationEvent.

Currently, TypeScript types this event as a generic Event, which loses all the properties specific to SecurityPolicyViolationEvent such as documentURI, blockedURI, violatedDirective, effectiveDirective, etc.

It would be helpful if TypeScript provided proper typings so that developers can access these properties safely, for example:

self.addEventListener('securitypolicyviolation', (event: SecurityPolicyViolationEvent) => {
  console.log(event.violatedDirective);
});
Playground Link

No response

Browser Support
  • This API is supported in at least two major browser engines (not two Chromium-based browsers).
Have Tried The Latest Releases
  • This issue applies to the latest release of TypeScript.
  • This issue applies to the latest release of @types/web.
Additional Context

No response

Dominant language
TypeScript
Stars
740
Forks
474
Avg merge
2d 8h
Merged PRs (30d)
15

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/TypeScript-DOM-lib-generator

All issues in microsoft/TypeScript-DOM-lib-generator

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.