Frame viewer tracing is broken with crrev.com/1812763002 |
||
Issue descriptioncrrev.com/1812763002 changes the way we handle content for pseudo and non-pseudo elements to bring us in line with other browsers. This breaks frame viewer, which was relying on the previous behavior. The change was expected to regress some chrome-specific sites, so the correct solution here is to update frame viewer code to be in line with the new "correct" behavior.
,
Apr 12 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/e9790b84effa64e1607e9d3013a33d426877cf21 commit e9790b84effa64e1607e9d3013a33d426877cf21 Author: catapult-deps-roller <catapult-deps-roller@chromium.org> Date: Tue Apr 12 21:21:12 2016 Roll src/third_party/catapult/ c8c258091..880f85740 (4 commits). https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/c8c258091b54..880f857409f8 $ git log c8c258091..880f85740 --date=short --no-merges --format='%ad %ae %s' BUG= 602363 TBR=catapult-sheriff@chromium.org Review URL: https://codereview.chromium.org/1877203005 Cr-Commit-Position: refs/heads/master@{#386807} [modify] https://crrev.com/e9790b84effa64e1607e9d3013a33d426877cf21/DEPS
,
May 26 2016
|
||
►
Sign in to add a comment |
||
Comment 1 by vmp...@chromium.org
, Apr 11 2016