binaryage / binaryage/cljs-devtools

Rendering issue in devtools scope tree

Ouverte
#52 7 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
chrome-bug
Langage dominant
Clojure
Étoiles
1.1k
Forks
51
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

## Problem
We have recently noticed the following rendering issue with the devtools scope tree.

![image](https://user-images.githubusercontent.com/4626024/64827447-91c17280-d607-11e9-8116-647caffbc037.png)

## Environment / Observations

- this started happening a few weeks back.
- seems to happen intermittently although presently it is all the time.
- happens both on my Linux Ubuntu (Ubuntu 18.04.3 LTS) desktop and a colleague's Windows 10.
- Chrome Version 77.0.3865.75 (Official Build) (64-bit)
- Chrome restart does not clear it.
- Playing with docking position does not change anything.
- Sometimes I have seen it render some of the vars but not all of them if you resize the devtools scope panel.
- If you disable custom formatters in settings, it renders fine but alas back to raw JS data structures.
- Rendering same ds in console via `js/console.log` does the right thing and expandable tree renders perfectly.

This might be a cljs-devtools issue I see latest 0.9.10 was released over a year ago. I'm not sure but did dirac embed the devtools and is it possibly running a more up to date version ? (we don't use dirac at the moment, but if installing it instead of cljs-devtools would that solve it ?

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Piste de recherche

The issue names no source file or test; first reproduce the scope-tree rendering problem in Chrome with custom formatters enabled and compare it with console rendering. Done means variables render completely and correctly in the scope tree without disabling custom formatters, including after resizing the panel.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
clojure, javascript
Domaine
devtools
Type d'issue
Bug
Difficulté
4/5
Temps estimé
3-5 jours
Activité
À l'abandon
Clarté
À clarifier
Accessibilité débutants
30/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.