[Bug] Text Layer example is broken (chrome)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 14.6k
- Forks
- 2.3k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 42
Description
Description
https://deck.gl/examples/text-layer (WebGPU) rendering issue )
Flavors
No response
Expected Behavior
The texts were rendered weirdlyy (see attachment)
Steps to Reproduce
open https://deck.gl/examples/text-layer and select webgpu
Environment
- Framework version: Deck.gl 9.4.0
- Browser: google chrome: Version 153.0.8010.37 (Official Build) (64-bit)
- OS: Windows 11
Logs
webgl-texture.ts:221 WebGL: INVALID_VALUE: texSubImage2D: no canvas
(anonymous) @ webgl-texture.ts:221
webgpu-adapter.ts:256 The powerPreference option is currently ignored when calling requestAdapter() on Windows. See https://crbug.com/369219127
(anonymous) @ webgpu-adapter.ts:256
7text-layer:1 Uncaught (in promise) Error: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue at the text-layer example and select WebGPU in Chrome on Windows. Start by examining the reported webgl-texture.ts:221 and webgpu-adapter.ts:256 messages, then verify that the text renders correctly without the reported texture error. Done means the example displays readable text in WebGPU.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- data-visualization, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100