This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 974
make use of intersectionObserver for tabs #10509
Milestone
Comments
ghost
added
the
sprint/1
label
Sep 13, 2017
cezaraugusto
added a commit
that referenced
this issue
Sep 14, 2017
cezaraugusto
added a commit
that referenced
this issue
Sep 14, 2017
cezaraugusto
added a commit
that referenced
this issue
Sep 15, 2017
cezaraugusto
added a commit
that referenced
this issue
Sep 15, 2017
cezaraugusto
added a commit
that referenced
this issue
Sep 19, 2017
syuan100
pushed a commit
to syuan100/browser-laptop
that referenced
this issue
Nov 9, 2017
- tabs can now respond beautifully to intersections - Also BEMify tabs Auditors: @bsclifton, @luixxiul fix brave#6716 fix brave#7301 fix brave#7730 fix brave#7765 fix brave#7925 fix brave#10123 fix brave#10509 fix brave#10544 fix brave#10582 fix brave#10611 fix brave#10838
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Test plan
#10691 (comment)
tabs rely on
getBoundingClientRect
for every tab opened, every tab set opened and every window resize. This is the biggest perf bottleneck in tabs and making use ofintersectionObserver
API will improve our performance considerably.This is a split of #10027.
Per last triage meeting I'm moving it to 0.20.x. Please do not change milestones.
The text was updated successfully, but these errors were encountered: