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 975
move frame hrefPreview
to a separate component
#10194
Labels
Milestone
Comments
NejcZdovc
added a commit
to NejcZdovc/browser-laptop
that referenced
this issue
Aug 3, 2017
Resolves brave#10194 Auditors: @bsclifton Test Plan:
NejcZdovc
added a commit
to NejcZdovc/browser-laptop
that referenced
this issue
Aug 3, 2017
Resolves brave#10194 Auditors: @bsclifton Test Plan:
35 tasks
NejcZdovc
added a commit
that referenced
this issue
Aug 5, 2017
Resolves #10194 Auditors: @bsclifton Test Plan:
NejcZdovc
added a commit
that referenced
this issue
Aug 5, 2017
Resolves #10194 Auditors: @bsclifton Test Plan:
dfperry5
pushed a commit
to dfperry5/browser-laptop
that referenced
this issue
Aug 18, 2017
Resolves brave#10194 Auditors: @bsclifton Test Plan:
This was referenced Sep 20, 2017
luixxiul
added
QA/checked-Linux
and removed
hackathon
Legacy label for a hackaton.
labels
Sep 20, 2017
This was referenced Sep 20, 2017
This was referenced Sep 21, 2017
This was referenced Sep 25, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Test plan
#10282 (comment)
link hovers trigger a re-render of the entire Frame component and can potentially be called quite frequently while moving the mouse over the page. We could eliminate that by splitting out the hrefPreview into a separate component so it isn't part of the frame props
The text was updated successfully, but these errors were encountered: