-
Notifications
You must be signed in to change notification settings - Fork 2k
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
UI: Fix rendering of DAS interstitial components #10094
Conversation
With the Ember update, when the will-destroy action is called to check the element height, its height is already zero. That seems strange but I didn’t look into it any further, as using did-insert to store the element lets us check its height before any other actions when a processing button is pressed.
Ember Asset Size actionAs of 8e1bc91 Files that got Bigger 🚨:
Files that stayed the same size 🤷:
|
Ember Test Audit comparison
|
99e3ad0
to
8e1bc91
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.
Nice quick fix!
this.cardHeight = element.clientHeight; | ||
cardInserted(element) { | ||
this.element = element; | ||
} |
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.
We do something like this in multiple places. It might be worth looking into something like ember-ref-bucket
at some point.
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.
agreed! This whole thing is more clunky than I’d like 😞
} | ||
|
||
storeCardHeight() { | ||
this.cardHeight = this.element.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 could technically go boom, but not with how storeCardHeight
is currently called.
With the Ember update, when the will-destroy action is called to check the element height, its height is already zero. That seems strange but I didn’t look into it any further, as using did-insert to store the element lets us check its height before any other actions when a processing button is pressed.
I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions. |
With the Ember update, when the will-destroy action is called
to check the element height, its height is already zero. That
seems strange but I didn’t look into it any further, as
using did-insert to store the element lets us use its height
before any other actions when a processing button is pressed.
Thanks to @lgfa29 for catching this.