1,295
edits
Line 47: | Line 47: | ||
| valign="top" | Layout-flush reporting | | valign="top" | Layout-flush reporting | ||
| valign="top" | Certain DOM APIs --- e.g., <tt>offsetLeft</tt> --- require a "layout flush" to bring layout up to date. Flushes can be very expensive; unnecessary use of these APIs (or use at the wrong time) can slow down web applications dramatically, but it's hard for Web developers to detect the problem or fix it. Firebug and other tools should receive reports of layout flushes and include them in profile data or console logs, along with the Javascript stack trace associated with each flush. This requires a small amount of core engine work to report the flushes, plus work to actually expose them in Firebug. | | valign="top" | Certain DOM APIs --- e.g., <tt>offsetLeft</tt> --- require a "layout flush" to bring layout up to date. Flushes can be very expensive; unnecessary use of these APIs (or use at the wrong time) can slow down web applications dramatically, but it's hard for Web developers to detect the problem or fix it. Firebug and other tools should receive reports of layout flushes and include them in profile data or console logs, along with the Javascript stack trace associated with each flush. This requires a small amount of core engine work to report the flushes, plus work to actually expose them in Firebug. | ||
| valign="top" | [[User:Roc|roc]] | |||
| valign="top" | [[User:Roc|roc]] | |||
| valign="top" | | |||
|- | |||
| valign="top" | Implement CSSOM RangeView.getBoundingClientRect/getClientRects | |||
| valign="top" | Currently there is no standards-based way to discover the bounds of a substring of a DOM text node. The [http://www.w3.org/TR/cssom-view/ CSSOM spec] defines a way, but no browser implements it yet. We should implement it. | |||
| valign="top" | [[User:Roc|roc]] | | valign="top" | [[User:Roc|roc]] | ||
| valign="top" | [[User:Roc|roc]] | | valign="top" | [[User:Roc|roc]] |
edits