02-02-2018 11:51 AM
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
02-03-2018 07:27 AM
02-03-2018 10:17 AM
10-17-2018 01:55 PM
I have this same issue. Were you ever able to resolve?
10-17-2018 02:08 PM
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,
10-18-2018 06:25 AM
The image resizer does not work for me either. Windows 10 desktop or Chrome browser
10-18-2018 10:04 AM
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.
10-18-2018 11:02 AM
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.
10-18-2018 11:56 AM
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-18-2018 11:59 AM
Same thing here. I'm facing the issue on Edge and on the Windows app.
10-18-2018 12:25 PM
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
10-18-2018 12:58 PM
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.
10-22-2018 12:23 PM
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.
10-23-2018 07:22 AM
10-23-2018 07:37 AM
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.
10-23-2018 09:51 AM
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.
10-23-2018 11:26 AM
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
10-23-2018 11:33 AM
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.
10-23-2018 11:41 AM
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.
10-23-2018 12:01 PM
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.