Microsoft/TypeScript

Wrong createElementNS() type definitions

Open

#24,269 建立於 2018年5月19日

在 GitHub 查看
 (5 留言) (0 反應) (0 負責人)TypeScript (48,455 star) (6,726 fork)batch import
BugDomain: lib.d.tsHelp Wanted

描述

Document.createElementNS() allows to create a few nonexistent SVG elements. In particular, this function has signatures that allow creating componentTransferFunction, textContent and textPositioning, but these correspond to SVG interfaces which do not have any real element associated.

This can be easily verified by running:

document.createElementNS('http://www.w3.org/2000/svg', 'textContent') instanceof SVGTextElement; // false
document.createElementNS('http://www.w3.org/2000/svg', 'text') instanceof SVGTextElement; // true

(Note that SVGTextElement implements SVGTextContentElement.)

貢獻者指南

技術棧
typescript
領域
frontend
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
TypeScriptDOM type definitions
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
60
研究方向
The issue is that `Document.createElementNS()` has overloads allowing creation of SVG elements like `componentTransferFunction`, `textContent`, and `textPositioning` that do not exist in SVG. The fix involves removing those incorrect overloads from the TypeScript DOM type definitions. The relevant file is `lib.dom.d.ts` in the TypeScript repository. Look for the `createElementNS` method signatures and verify against the SVG specification which elements are valid. Check existing comments for any additional context or suggestions.