Anthony Pessy
Anthony Pessy
@miguelcobain The differences are the following: first render ```js position.top = existingOffsets.top /* 0 */ + originNodeRect.top /* 677 */ - (alignTargetRect.top /* 17 */ - openMenuNodeRect.top /* 0 */);...
Tried to reset the css properties of `containerNode` at the beginning of `calculatePosition` like so: ```js containerNode.style.top = ''; containerNode.style.left = ''; containerNode.style.transform = ''; containerNode.style.transformOrigin = ''; ``` So...
@offirgolan If you remember the kind of errors there was in the past, do you think I can be fine if I remove the `isDeleted` from dependent key as long...
I believe this is duplicate with #671 The working workaround for me at the moment is to pass `isTouched=errors.length`.
@jpschober In my code I do things like: ```hbs isTouched=(gt model.errors.property.length 0) ``` or ```hbs isTouched=(readonly isXXXInvalid) ```
Ins't there a less intrusive way to setup the duration for tests? In the service for instance as default configuration in test env?
@miguelcobain Didn't think of the usage of paper-toast directly, nevermind then :)
I face the same issue than @johnunclesam . The problem with your proposed solution @sbatson5 is that it will move the message with the top priority below the lowest priority...
I think the behavior is still here, I stumbled upon this ticket by accident and since there was no activity since March I figured that maybe nobody was bothered by...
Should this issue be filled [upstream](https://github.com/peec/ember-css-transitions/issues) ?