Improve tracking of TRACE_STYLE_INVALIDATOR_INVALIDATION origin |
||||||
Issue descriptionStyleChangeReasonForTracing and TRACE_STYLE_INVALIDATOR_INVALIDATION needs to be revisited to see if we can improve tracking the real origin of the invalidation. It's possible that most of the information is there, and that we can introduce tooling to connect scheduling of an invalidation set with the style invalidation it causes in the StyleInvaldator::Invalidate() step. We can possibly do this as a post-process script on trace.json data. This is related to issue 706758 .
,
Nov 15 2017
,
Nov 16 2017
Note to self: I don't think RuleSet invalidations are properly traced.
,
Nov 30 2017
,
Dec 6 2017
,
Dec 6
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 7
This was more like a TODO. Closing. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by bugsnash@chromium.org
, Nov 15 2017