-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
At least in Augular 7, it seems replace method will create a additional ".cropper-container"s elements #617
Comments
I guess it is a bug of your own code. |
Thanks for your reply. Uunfortunately, I do not think your guess of a bug in my code is correct. You can easily see the creation of a 2nd 'class="cropper-container cropper-bg"' by going to https://stackblitz.com/edit/angular-cropperjs-demo?file=src%2Fapp%2Fapp.component.ts and doing the following. Once at that stackblitz demo from the link above, then drop in the following code in the 'app.component.html' & 'app.component.ts', respectively, and open in your browser console (F12) and in the console; then find and open the <div class="cropper" element; the click the "Replace" button twice; and you will see the the new, additional <div class="cropper-container cropper-bg" get created. app.component.html code: <angular-cropper #angularCropper [cropperOptions]="config" [imageUrl]="imageUrl"> <img [src]="imgUrl"/> ` app.component.ts code: @ Component({ @ViewChild('angularCropper') public angularCropper: CropperComponent; constructor(){ cropMoved(data){ replace() { |
It is a "bug" or is there a necessary code step required to avoid the creation of additional ".cropper-container" elements?
Thanks,
MaccabeeY
The text was updated successfully, but these errors were encountered: