Images pasted to Wiki cannot be enlarged

[Tarek Faham]

When pasting an image into Wiki, it works, but if the image is a screenshot, there is no way to see the image clearly since it is scaled down. I hope you can add a way to zoom into the Wiki or enlarge the pasted images.

Tarek

[#2]

I have just pasted a screenshot in a Wiki in Teams and I can resize it with no problems

[#3]

How did you resize? What is the exact version you are using?

Tarek

[#4]

I have this same issue. Were you ever able to resolve?

[#5]

I just tried now, and I noticed that a handle will appear on the image when you click on it. This allows you to expand the image. Also, you can zoom in/out by pressing ctrl and use the mouse wheel to control zoom level.

Tarek,

[#6]

The image resizer does not work for me either. Windows 10 desktop or Chrome browser

[#7]

Here is my version (Windows Desktop):

You have Microsoft Teams Version 1.1.00.25457 (64-bit). It was last updated on 9/26/18.

Check your version from Your Account (Picture) -> About -> Version.

[#8]

I'm having the same issue at the latest Team version here (Version 1.1.00.25457, 64 bits, 26/09/2018.). New images I paste into the wiki can't be resized, but older ones (pasted a few weeks ago) can be. Really strange and no clue on how to solve it.

[#9]

Unfortunately although I see the little handle, it doesn't seem to do anything. I'm on Mac OS 10.13.6 on and have tried it both in chrome Version 69.0.3497.100 and in the Mac desktop application Version 1.1.00.26352.

[#10]

Same thing here. I'm facing the issue on Edge and on the Windows app.

[#11]

Actually, you guys are right !!! When I paste new image, there is no way to change its size. The size handle will show, but it will not work.

The old images can be resized.

I will try to paste new image, and check in few days to see if it will work. Maybe it takes time to be ready for resizing.

Tarek

[#12]

I've waited more than one hour and still nothing. If I look at the Wiki folder in SharePoint, all the pasted images are there with original resolution, so it's certainly something in the interface, as they are being uploaded fine. 

[#13]

I am having the same issue with the Wiki images. It is completely worthless to put tutorials in my Wiki if the images are tiny and a user can't read them. How do we get this fixed asap.

[#14]

Another issue appeared as I was fiddling with this matter, is that the WiKi item will get locked, and then you have to force unlock. The strange thing is that there is no way you can lock WiKi item manually.... it gets locked as part of a bug or issue.

[#15]

Is this discussion enough to inform Microsoft about the potential bug? I continue working with a few wikis here assuming it'll be fixed someday, but if not... I need to change strategy. Anyone from Microsoft here?

Regards. 

[#16]

I'm seeing this issue too. One of the sections on a page I created is locked...by me... and I cannot access or unlock it despite the fact that it says I'm the one working on it.

[#17]

In case they want to fix, better provide desired behaviour.

As a WiKi user/author, when pasting an image, allow the image to show as a thumbnail, then when you click on the image, it will expand/zoom to show in full resolution. Also, allow zooming in/out.

If you anyone has feedback, please suggest modification.

Tarek

[#18]

Being able to click and see the actual size of the image is great, but the functionality that's broken here is more basic than that. The wiki is auto-resizing images on its own and will not allow the manual resizing of that displayed image or thumbnail even if there is available space within the wiki page. I would like to be able to manually resize those images to use all available width before there's a need to click and enlarge.

[#19]

I agree with you Danielle. Writing it down as an user story or something would be great had we been talking about a new feature, but this is a bug. I can confirm that three or four weeks ago we could resize pictures in Teams wiki. Indeed, images pasted before the bug can still be resized. So, unless this is a feature change (which I doubt), we should consider it a bug. Regards. 

[#20]

I suggest to specify the requirements, and let them implement accordingly. Weather it's a bug or missing feature, the bottom line is that it's not meeting our needs.