developit / developit/preact-compat-example
Chrome/FF developer tools element navigation is slow
- 主要语言
- JavaScript
- 星标
- 53
- 派生
- 15
- PR 合并指标
- 30 天内没有已合并 PR
描述
I've never seen this before so I'm not sure where the core issue is, but it seem to fit with this example as I created a preact app using `preact-cli` and `react-toolbox` so maybe you have some insight.
You can see the issue for yourself by navigation to [my app](https://fiday-4249d.firebaseapp.com/). You don't have to login, just open developer tools, select the Element panel, and start expanding elements. You should notice a long lag with the responsiveness of the element panel.
I don't see this problem with the `react-toolbox` components [page](http://react-toolbox.com/#/components) or the `preact-compact-example` [page](https://preact-compat-example.surge.sh/).
To attempt to isolate the issue I created a new app from preact-cli and only added the [`Snackbar`](http://react-toolbox.com/#/components/snackbar) example.
What I noticed was that importing components as shown seemed to be the problem.
In other words changing this:
```
import { Button, Snackbar } from 'react-toolbox'
```
to this
```
import { Button } from 'react-toolbox/lib/button'
import { Snackbar } from 'react-toolbox/lib/snackbar'
```
seemed to fix the problem.
However after following that pattern for every `react-toolbox` component I'm still seeing the issue. I did introduce changes at top level routes which obviously worked, but seemed to have diminishing returns and once I added the main app route back in it's back to being painfully slow.
贡献指南
这个仓库没有索引到贡献指南
调研方向
使用链接的应用在 Chrome 或 Firefox 开发者工具中重现延迟,然后将其与提到的 react-toolbox 和 preact-compat-example 页面进行比较。首先测试 issue 中显示的两种 import 模式以及所描述的 route 更改;没有指定源文件或测试,因此要完成这项工作,需要找出负责的 integration,并证明修复后元素导航具有响应性。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- javascript
- 领域
- frontend, performance
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 25/100