forked from airbnb/epoxy
-
Notifications
You must be signed in to change notification settings - Fork 0
feat(visibility): introduce partial visibility state #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
mediavrog
wants to merge
13
commits into
master
Choose a base branch
from
838-partial-visibility
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
fbd42c6
initial commit
mediavrog 832f83d
rename threshold to thresholdPercentage
mediavrog 8a9f4a7
pass partial visibility threshold to child recycler views
mediavrog 09907bd
update kotlin sample to handle partial state; sample uses 75 percent
mediavrog 263ce39
introduce PARTIAL_IMPRESSION_INVISIBLE
mediavrog 2dbbec6
be more specific in doc about when threshold is met for PARTIAL_IMPRE…
mediavrog e36c934
remove debug statement
mediavrog ad020e3
kotlinsample: move partial state circle right next to visible
mediavrog b7a7ba0
basic tests for partial visibility
mediavrog a30c82f
test without partial viz
mediavrog 288ff35
remove unused reset of partial viz threshold
mediavrog d09a4a1
format code
mediavrog 0b6c6c2
disable partial impression via null and handle 0 like VISIBLE
mediavrog File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you look at the
FOCUSED_VISIBLE
it protect against component that are bigger than the view port.I was wondering if you want to implements the same protection?
The problem is, if one of the component is bigger than view port (or if threshold % bigger that view port) you will never receive a
PARTIAL_IMPRESSION_VISIBLE
event.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll have a look into
FOCUSED_VISIBLE
and it's protectionThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you think users would expect? I see some possible ways of dealing with this:
@eboudrant From your experience with epoxy in use and feedback so far, which of these behaviors (or which other suggestion) would be most appropriate?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another comment: I looked at the code for
FULL_IMPRESSION_VISIBLE
, which also does not handle the case if an element is bigger than the viewport. I tend towards keeping this same behavior for thePARTIAL_IMPRESSION_VISIBLE
as well as it would be consistent and predictable. (referring the list above it would be behavior1.
)In the case with
FOCUSED_VISIBLE
, the definition of what isfocused
gives some leeway for interpretation, so I think in that case having a fluid focused range is appropriate.