-
Notifications
You must be signed in to change notification settings - Fork 350
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
Test scrollbar is ignored in width constraints (#762) #763
Test scrollbar is ignored in width constraints (#762) #763
Conversation
df8e23d
to
eacff06
Compare
This has been manually tested on Edge, Firefox, Chrome and Safari. |
bf5867d
to
f8495c7
Compare
1994d1b
to
95ee603
Compare
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 think avoiding the next(
is a bit tricky and may require some deep diving, but we should do that before landing this fix.
Thanks for the spike! I think test cases or understanding how this behaves in which browsers (and with what kinds of devices attached 😢) would be helpful.
scheduler.schedule( | ||
'affect', | ||
() => { | ||
next(() => { |
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.
Why is next
needed here?
This seems not ideal. The logic seems to be: When wrappedRows changes the UI will reflow, so the width constraints needs to be revalidated. There must already be something doing that though, or some other mechanism we can use besides an observer to make it happen. This is definitely a tricky bit.
e521327
to
557c94c
Compare
@mixonic My first version had wrong assumptions on those size types and that's why I needed to round the scale to get accurate result. This should be fixed now. I've added tests too to demonstrate the initial issue. However, I didn't change the observer yet. This will be my future task. Anyway it was just to give you updated status. |
557c94c
to
fd83fae
Compare
@mixonic |
@ctjhoa Do you think this issue is only relevant to older Ember versions? I'm surprised this test would only fail for 2.8 and 2.12. If you want to set up some time to pair or discuss please shoot me an email (address is on my profile) I'd happily set up the time. |
b0d82f6
to
fa73f30
Compare
@mixonic Tests are successful except ember-beta & ember-canary which fail but caused by those changes.
|
fa73f30
to
658838e
Compare
#762
This is a draft PR which doesn't include tests.
It's mostly to start discussion around the solution and the global design.