LivelyKernel / LivelyKernel/lively.next
Timing problems in loading libraries from frozen code
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 90
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
**What would you like to achieve?**
I'm trying to load Google's chart libraries, and I'm hitting timeouts when the page is loaded. If I wait some time, on subsequent loads it works fine. But this leads to the question of just how do I make sure that we're getting the timing right. I'm also seeing (perhaps related) the following error:
`TypeError: Cannot read properties of null (reading 'halos')`
at
```
world.halos().forEach(function (h) {
return h.maskBounds = world.getHaloMask();
});
```
which corresponds to the source code
```
$world.execCommand("open browser", { packageName: "engageLively--galyleo-dashboard", });
```
But the real question is how to load safely
**How are you trying to achieve that**
**Alternative solutions**
If applicable, what other solutions have you tried?
**Additional Resources**
Please provide links to any custom code that might be necessary to grasp your problem. Screenshots of custom component, etc. are also appreciated.
**Version**: Please paste the lively.next commit on which the problem occurred here (use the copy button of the Version Checker in the bottom left corner).
c725a776b26bd744331765a4881ba4c0557d2fea
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
Start by reproducing the timeout while loading Google's chart libraries from frozen code, then inspect the reported $world.execCommand("open browser", ...) entry point and the world.halos() error. Determine the loading sequence and define completion as reliable library loading without the null-halos failure on the initial page load.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100