visgl / visgl/deck.gl

[Bug] Basic scripting example not working in chrome

Open
#9,731 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
14.6k
Forks
2.3k
Avg merge
2d 9h
Merged PRs (30d)
42

Description

Description

If I run the scripting example here locally, and try to open it in chrome, the example does not appear, and I get the following errors:

dist.min.js:2795 deck: Cannot read properties of null (reading 'luma') undefined onError @ dist.min.js:2795 start @ dist.min.js:2736 await in start Mh @ dist.min.js:2795 Fd @ dist.min.js:5460 (anonymous) @ reproduce_luma.html:24Understand this error dist.min.js:2794 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'luma')

The same example works perfectly on firefox.

Flavors
  • Script tag
  • React
  • Python/Jupyter notebook
  • MapboxOverlay
  • GoogleMapsOverlay
  • CARTO
  • ArcGIS
Expected Behavior

The example should run in chrome

Steps to Reproduce

Save: https://github.com/visgl/deck.gl/blob/9.1-release/examples/get-started/scripting/basic/index.html locally, edit the version number to latest, use http-server to run a local server, and open in the google chrome browser.

This codepen runs successfully for me in google chrome, so something about the scripting api?

Environment
  • Framework version: 9.1.14
  • Browser: 138.0.7204.49
  • OS: Ubuntu 22.04.5
Logs

dist.min.js:2795 deck: Cannot read properties of null (reading 'luma') undefined onError @ dist.min.js:2795 start @ dist.min.js:2736 await in start Mh @ dist.min.js:2795 Fd @ dist.min.js:5460 (anonymous) @ reproduce_luma.html:24Understand this error dist.min.js:2794 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'luma')

Contributor guide

Open the contributing guide

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.

Research direction

Start with examples/get-started/scripting/basic/index.html and reproduce the failure using http-server in Chrome with version 9.1.14 or latest. Compare the Chrome run with Firefox and the linked CodePen while tracing the reported luma error. Done means the scripting example renders successfully in Chrome without the reported TypeError.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
computer-graphics, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.