|
|
| Line 215: |
Line 215: |
| ! Comments | | ! Comments |
| |- | | |- |
| | Highlight JS that causes reflows to occur
| |
| | Gecko developers are able to point out statements that trigger reflows from code inspection. We can do better: {{bug|453650}} discusses adding notifications for timing reflows and calls that trigger a reflow. With this information, we can create a tool that obtains stack traces when reflows are triggered, and order the results by duration, and link this to specific triggering JS statements.
| |
| | [mailto:josh@joshmatthews.net jdm]
| |
| | Someone from devtools, with platform support
| |
| | C++ and JS required.
| |
| |-
| |
| | Highlight slow CSS selectors
| |
| | We have a wiki pages of ways to write CSS rules that take advantage of Firefox's internals: https://developer.mozilla.org/en/Writing_Efficient_CSS. If we could add timing data to CSS selector matching, we could use that information to profile rules on a page and display a profiling view that links to specific problematic rules.
| |
| | [mailto:josh@joshmatthews.net jdm]
| |
| | Someone from devtools, with platform support.
| |
| | C++ and JS required.
| |
| |} | | |} |
|
| |
|