-
-
Notifications
You must be signed in to change notification settings - Fork 84
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
If the contentSize is not known after the ember-native-collection is #141
base: master
Are you sure you want to change the base?
Conversation
This also closes issue #137 |
+1 |
1 similar comment
+1 |
Nice addition, but will need tests before we can consider merging it. Mind doing so? |
README.md
Outdated
* Returns the position of the item | ||
*/ | ||
positionAt(itemIndex, clientWidth, clientHeight) { | ||
return { x, y}; |
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.
nit: funky whitespace consistency
addon/components/ember-collection.js
Outdated
} | ||
if (this._scrollIndex !== scrollIndexAttr && (this._clientWidth || this._clientHeight)) { |
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.
this area is quite complicated, it may be worth extracting to a function so it is easier to unit test.
I will look to it, next week.
…On Wed, May 10, 2017 at 9:10 PM Stefan Penner ***@***.***> wrote:
Nice addition, but will need tests before we can consider merging it. Mind
doing so?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#141 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGwv8iiAyOXHnZSBQPSeoJXDBYrpaiRsks5r4guIgaJpZM4L_FJa>
.
|
@stefanpenner do the changes @pieter-v made suffice or...? |
@pieter-v i'm going to roll my sleeves up and try to get this to be mergeable. My plan was to fork your branch, pull the latest changes from master and handle all conflicts then. Should I make a pr to this branch in your own forked repo so you can review/accept? |
@Luiz-N That is great, thanks
…On Mon, Nov 27, 2017 at 7:55 AM Luiz-N ***@***.***> wrote:
@pieter-v <https://github.com/pieter-v> i'm going to roll my sleeves up
and try to get this to be mergeable. My plan was to fork your branch, pull
the latest changes from master and handle all conflicts then. Should I make
a pr to this branch in your own forked repo so you can review/accept?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#141 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGwv8ge7_g9NLHsV6RxUzx0L05FEukshks5s6lzKgaJpZM4L_FJa>
.
|
inserted into the DOM, then retrieve it from the layout
inserted into the DOM, then retrieve it from the layout
fixes issue #140