2cc471f8ea
When mobile viewport is enabled, we have two viewports: the visual (inner) viewport and the layout (outer) viewport. The clip of the visible viewport is not in the paint property tree, so we need to apply the clip separately. The clip was mistakenly removed in crrev.com/824480. Also fix a bug before crrev.com/824480: the current scroll offset of the visual viewport was not considered when applying the visual viewport clip, which caused invisible shifts reported and visible shifts not reported. Bug: 1141739 Change-Id: I425718b1fdfb2689a7f2948c561101d0b476eb7f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2593180 Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Reviewed-by: Steve Kobes <skobes@chromium.org> Reviewed-by: Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#837853}
Chrome Speed
Contact information
- Contact: speed@chromium.org
- Escalation:
- benhenry@chromium.org (TPM)
- File a bug: template
- Regression postmortem: template
User Docs
- How does Chrome measure performance?
- My CL caused a performance regression! What do I do?
- I want Chrome to have better performance
- Perf sheriffing documentation
- I want to add tests or platforms to the perf waterfall
Core Teams and Work
- Speed domain area experts: These mailing lists and bug triage rotations provide expertise into specific domain areas of Speed: memory, power, loading, responsiveness, binary size, data usage, and browser UI.
- Chrome Speed Operations: provides the
benchmarks, infrastructure, and releasing oversight to track regressions.
- Benchmark-specific discussion: benchmarking-dev@chromium.org
- Performance dashboard, bisect, try jobs: speed-services-dev@chromium.org
- Chrome Speed Metrics: provides a set of high-quality metrics that represent real-world user experience, and exposes these metrics to both Chrome and Web Developers.
- General discussion: speed-metrics-dev@chromium.org
- The actual metrics: speed launch metrics survey.