Caitlin Main – Completely agree. I'm shocked that there's no official response from Atlassian regarding what data they relied on to arrive at this presumption. Further, little do they realize that features need to be backward compatible. This is breaking change for possibly thousands of users. Many of whom will only realize when things go for a toss. Talk about throwing the baby with the water!

"The rationale for this change, among others, was that pixel level control was overwhelming for most users making it hard to create beautiful and readable content easily across any screen."

I'm quite curious as to what the actual data on this response is. I feel like there had to be a better way to offer predefined image sizes to users who were "overwhelmed" by the (very simple?) old system that didn't involve gutting basic functionality that is integral to companies who use Confluence for custom standardized design documentation? My development teams are very disappointed and frustrated by this change. 

Kelvin Hill - Our company does the same, using Confluence for both internal documents and also as branded documentation on features and use for our clients. In order to demonstrate features, we use a lot of application screenshots, too. This loss is greatly affecting our ability to serve our customers. 

Tan Rong Wei, you were spot on when you wrote "provided you only have texts in the articles."

Sadly, we don't need a simple text editor. In addition to many company-internal text documents we collaborate on, we also use Confluence to prepare and export branded documentation for our clients. We have been working around the legacy editor's limitations and quirks for many years because it is sufficiently flexible to allow us to do so.

The new editor removes much of the functionality and also strips out the flexibility. In respect of this specific issue, we have consistently failed to display our images (many of which are application screenshots, which must be displayed at a specific resolution rather than a general size of x-small, small, medium, large, etc.) in the new editor in a consistently satisfactory way. It is immensely frustrating and causes us say no end of rude words about the decision makers at Atlassian.

While our frustrations have been acknowledged, I have yet to see much evidence of any action beyond empty acknowledgement.

It increasingly does look like they are abandoning the old editor simply because it is too buggy. To their credit, the new editor is a lot less buggy, and streamlined to use, provided you only have texts in the articles. 

Taking away the ability to re-size by pixel is a totally unacceptable loss of functionality. Anyone else going to the Summit? Maybe we can get an actual answer there? This is functionality we desperately need back.  

@Kelvin Hill The exact issue of what we are afraid of. We have already discussed if/when the old editor is taken away and the new editor no longer meets out criteria, the answer is not to adapt to the new editor, it will be to find a product that does what we want it to do. 

Currently the new editor is not an option for us with the image sizing options (or lack there of) available. Without being able to specify how large we want the image, the images are usually too large. 

Not something we will be working around. A complete blocker for our docs. 

Similar with table sizing/positioning and multiple other issues. 

Edit:

Also, the solution to purchase plug-ins to fix problems that weren't problems will not be acceptable. 

@Roz Turner. I only learned about the Fabric Editor in October/November 2019, but I understand it was made available to some folks almost a year ago. At the risk of angering the Atlassian gods, I suspect the fact that this issue has persisted for almost a year without anyone showing any interest in resolving it or even admitting that it is unacceptable doesn't bode well. I imagine it has been decided that we must learn to live with it or find an alternative product. They don't want to come out and say that directly, of course, so they simply maintain this ticket as "Gathering Interest" without assigning it to anyone. The Confluence user base is sufficiently large to warrant such complacency.

I'd like to add my voice to this as well as my vote. Of all the irritating changes made to the new editor, this is by far the worst. Our company uses Confluence extensively and the inability to resize images now means we have comedy-sized, stupidly large screenshots in our documentation which we can do nothing about.

Removing this option is a massive hindrance; instead of simplifying the editor, you're limiting users' options by removing something that already worked. Users should be given the choice as to whether they want to resize by grid, or by pixels. I'm fairly certain that removing key features is the least efficient way to retain customers. Please fix this.

@Julia Wester. Sadly, you've misunderstood the roadmap. I have included a screenshot below, but I suspect it won't attach correctly, so I will also explain in text.

Here are the roadmap column headings and the values for the Image sizing entry:

Feature: Image sizing
Legacy editor:  [green check mark] pixels
New editor: [green check mark] grid
Will it be available in the new editor: Available
Track the backlog: CONFCLOUD-67554 - Resize image by pixel on new editor - GATHERING INTEREST

If you simply view the Image sizing entry in the table without checking the column headings, it looks like pixels and grid sizing are supported in the new editor. Currenly, only grid-based image sizing is available in the new editor, and it produces terrible results if you attempt to align an image in any way other than the default or resize it. I remain shocked that the many glaring bugs with images remain unresolved.

If we are really lucky, image sizing by pixel will be added to the new editor at some point.

I am so confused about how resizing is marked as available: https://confluence.atlassian.com/confcloud/confluence-cloud-editor-roadmap-967314556.html?_ga=2.79383252.1187993251.1579073416-313053509.1570455679 I just added an image to a page (not in a table) and can't find the option at all - not to mention it added hundreds of pixels of padding above and below my image and pushed content so people have to scroll. Just WHERE do I find this ability to resize images?

No more  possible to design pages including small pictures or icons.

Working myself in software industry, I can't believe introducing a so big regression in a product...

Please fix it ASAP !

The option to edit image settings (resize, paragraph position) with the new tool is not accessible for images in a table.

They need to be resized/positioned outside of the table, then moved.

This feels like a bug, and is a frustrating experience.

I doubt how many users are aware of this, Kyle. Obviously, Atlassian has not done any outreach to see if people care or not. Their policy seems to be shoot first and ask questions later. 

I think only 62 votes is not a lot. Doubt it's enough to force change/catch their eye.

Those who have taken the time to comment on this thread should get everyone they work with who is impacted by this problem to vote for the issue.

Can Atlassian bother to explain what the issue was with the old image resizing? We have a huge doc portal with custom image sizes. How do the wonderful folks at Atlassian expect me to handle this change? We either need to have differing image sizes for old and new docs or refactor the old images to suit the new editing experience. Is this a software company that thinks about backward compatibility or not? Please do not force your new editing experience on us without resolving the many kinks in the new editor!

The status of this ticket amazes me – "Gathering Interest" – really? You break existing docs and then find out how many users are impacted?

This doesn't even make sense. I copied four images that are exactly the same size (80 pixels) on an old page in Confluence and tried copying them over into a page in the new editor, into a table.

The images re-size on their own when I paste them into the new page. I have no ability to drag to change the size to get them BACK to being all the same size. My only two options are to either deal with the inconsistent icon sizes, or delete the icons. 

Sizing images is the new editor is terrible; they snap to some arbitrary grid, and you can't shrink them below some unreasonably large size. I want the legacy image mgmt back!

Thanks, Kim. Your proposal has already been suggested by a number of frustrated users (including me) in a variety of threads. The problem we face, however, is that Atlassian has pledged to withdraw the old editor entirely at some point.

Personally, I wouldn't want to be in Atlassian's shoes right now. I, for one, have documentation I generate in Confluence that I deliver to paying customers. That content simply isn't supported by the new editor, so I cannot and will not migrate it. Does Atlassian expect me to delete the very content I have been creating in the tool we have been paying them to use for years? There is 0% chance I'm going to roll over without a fight.

Ladies and Gents

I have discovered that the original content has not been affected by these changes - its only when you create new content.  So that means I can resize my original work, no problem!

However, I also discovered that you can copy content and the old style resizing is available.  Simple interim resolution  -  take an original page, copy it, delete the original content and then you are free to add images and resize as before.

It works for me!

Kim

Hi.

I'm Angelina form Wafer stick manufacture in Indonesia.

I want to ask you related Confluence could features. Could we ask you email?  Or Could we invite you to do conference call with us to show how the confluence cloud working.

You can contact me by email a.qaspvsys2@seasonalsupplies.co.id

Thank you,

Regards,

Angelina

Communications with local Atlassian support personnel in my region yielded the following comments (theirs, not mine).

"However, we might be able to enable flags for particular elements/macros that your business requires it, this will be handled on a case-by-case basis and the flags availability. Please do let me know if you have any further feedback or concerns that I can share with the Product management team."

So I guess we'll just have to keep bugging their support with requests of features that are important to us. The local support personnel did promise me that the product management team will roll out the image resizing within tables for my site specifically. Not sure how that would work.

Tan Rong Wei. You are correct. Atlassian was concerned that users found resizing images too difficult, so it included almost no control for images in regular parts of a page and even less control for images in tables and layout panels. All you can do is insert a centre-aligned image into a table or layout panel.

You no longer need to waste time adjusting an image to the size you want. Instead, you can accept the size Atlassian decides you must have, and you can use the extra time searching for a better editor.

So, any 'bug testers' here find out that you can't resize pictures using the grid snaps in table cells?

I put a picture in my table, and my mouse cursor just won't change to the resize icon.

Hi  - I agree totally with Tom  - I am struggling to create content now.  Also, when I put the content into PDF, the formatting is all distorted, making the document unreadable. 

Many thanks

Kim

Hello - we really need to be able to resize images using the pixel parameters/show original option that used to be available.

We use Confluence to create an Online User Guide for our software product and therefore we include lots of screenshots (images) in the pages we create. There was an option in the legacy editor which was "Show Original" - this is absolutely needed for us as it allowed the full screenshot do be displayed, rather than changing the size of it which loses clarity.

Equally, we used to use the pixel options too - I thought it was pretty clear and easy to use and you had much more control!

Many thanks.

Frankly, I don't know why I'm bothering to document another image-functionality faux pas because I haven't yet seen anyone from Atlassian actually honestly acknowledge the truly hideous state of image handling in the new editor, but I'm going to document it anyway.

I just began a new page of documentation for a set of procedures, but I had to abandon the new editor as soon as I inserted my first screenshot.

In the old editor, I am able to add a border to a screenshot with a simple button click. That option has been removed, of course, because it was allegedly too confusing for users (yes, really). You can't make this stuff up.

Sadly, I still need a border for my images because screenshots bounded by whitespace often look incomplete and potentially confusing without a single pixel border to contain the image. I now need to go through many manual steps to edit my screenshots with an image editor to add a simple border. And as if that weren't annoying enough, it's now actually a scary mistake to include a screenshot with a single pixel border because the new image handing functionality removes control of the image size from the user—and displays the image at some arbitrary size (unless you leave it centre-aligned, which doesn't suit my layout). That means I end up with a screenshot that is either larger or smaller than the original, and the one-pixel border has either been scaled up or down. Have you ever had something that makes you want to stamp your feet and shout? This is it.

Which substandard look should I opt for, I wonder.

@Kyle Peters. You make an interesting point. I reported previously that although there are no alignment options for images within table cells, it was possible in the new editor to align an image elsewhere in the page—and then copy/paste it into a cell and preserve the alignment. The resulting image size was a lottery, but it worked. It was functionality the developers had clearly overlooked in their focus on reducing the usefulness of image handling.

Sadly, I have just re-tested that process it in light of your comment, and it appears the developers have removed that workaround. I may be wrong, but I can no longer align images in table cells (other than the default of centre aligned).

If the developers have actually locked down that part of diminished image handling to prevent the workaround, it will say a great deal about Atlassian's disregard for its customers.

Atlassian will drag its feet over glaring bugs, but if you manage to find a workaround, Atlassian will focus on removing the workarounds before resolving the bugs. Unbelievable.

This is a big blow to the way my company uses the wiki.

We also seem to have lost the ability to change image alignment in a table. They are always center-aligned and it's super wonky looking.

Rick van Twillert, further to my previous comment, it only appears to be possible to have an image displayed at original size if you allow it to adopt its default centre alignment AND you do not (under any circumstances) touch the resize handles. Step away from the resize handles!

It is nothing short of perverse that Atlassian claims to have dumbed down the image-insert option because users found pixel-level image control too complex. Oh, the irony! The new image control is now so full of bugs, it is way more complicated for dumb users to achieve a half-decent result. I defy Atlassian to prove that users find the awful new approach better than what it replaced. It beggars belief.

At least give the option to display the original image size. Currently, when one places a confluence screenshot on a page it displays all blurred, like this:

Atlassian, you cant be proud of this right? With your design guidelines and all... This image looks like crap honestly. Please up the priority and fix this asap!

You are correct, Andreas. There are more things wrong with image control than right. I would be embarrassed to have released such substandard functionality.

The New Editor image handling is ridiculous (from a feature point of view) and on top buggy as hell! The comments here say it all.

I don't understand why this issue is of type "suggestion" it should be a "bug" with severity "catastrophic" 

Can't get enough of these image bugs? Try this...

I previously mentioned that once you have deliberately or accidentally clicked on the image resize bars (the vertical handles either side of an image), it will snap to the nearest set width and you can't return to the original image size without rolling back the page. Alternatively, if you left align a small image, it will display it as an enormous monstrosity.

Well, another bug partially comes to the rescue.

To return the image to almost its correct size, do the following:

1. Left align the image.
2. Use the right resize handle to reduce the image to its smallest available size.
3. Click the Make page fixed-width or Make page full-width option at the top of the page (depending on which you have selected).
4. Publish the page.

Don't expect miracles, but the image will appear far less awful than before. It isn't displayed original size, but it's an improvement. Thanks for that handy bug, Atlassian. 
 

@Frank Forsten. Sure, you're correct. I'm still working in the old editor, but I'm also trying (unsuccessfully) to prepare for Disaster Day by creating content in the new editor in advance of the forced switchover. It ain't lookin' pretty.

I've just left-aligned a 32-pixel-wide image in a new-editor page. After publishing, the image is displayed over 10 times larger than the original size. Do you know how bad an image looks when you scale it up by a factor of 10? You couldn't make this stuff up. The developers must be laughing themselves silly over the "fun" they are causing.

Want more bugs? Sure, go right ahead.

Let's say you have a small image you want to display wrapped or aligned left in a document. Go right ahead and try it. Get yourself an image that is 50 pixels wide. Insert it into a page and either wrap or align it to the left. Publish the page, and what do you see? BOOM! The image is now about 375 pixels wide (7.5 times wider than the original), and doesn't it just look amazing! Now then, where's that eye-roll emoji?

Found a work-around for the cloud version:

1. Take any old page, which is still "coupled" to the old editor. If there isn't any, take the page, which is initially generated when opening a new cloud account - that page is also "oldschool"
2. Copy that page and move it to the desired location. This copy is still coupled to the old editor

Of course that works as long as Atlassian pulls the plug off the old editor. But today it works and I can work.

I forgot to mention that Align Centre images are aligned left in the the PDF, too.

And an image will be displayed at its original size ONLY when it is centrally aligned. The moment you align or wrap left or right, BOOM, it snaps to the nearest unwanted size.

Align right also erroneously turns into wrap right in the PDF output. Yay!

After a few more minutes of testing, we have more image bugs.

Everyone please try the following:

1. Paste an image into a page. Hit enter and paste it again. Hit enter again and paste it a third time. That's three images displayed centrally.
2. Click on the second image and select Align Left.
3. Publish the page. At this point, you will discover the second image has been annoyingly resized to snap to its nearest vertical handles (unlike the top and bottom images), even though it still appears at its original size when you subsequently open the page for editing. Oops.
4. Now for the magic. Click the ellipsis and select Export to PDF. In the PDF output, the third image will be displayed over the top of the second unexpectedly larger image because align left is erroneously changed to wrap left in the PDF output. Double oops.

And the new editor is being rolled out now, right? 

I really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really wish I didn't have to perform elementary testing that Atlassian has clearly failed to do.

Here are the details of an images bug that was alluded to earlier. It took me seconds to reproduce it.

If you insert an image into a page, the image will be centre-aligned and presented at its correct size. You can even select any of the other alignment options (align left, align right, wrap left, wrap right), save the page, and retain the correct original size of the image. BUT DON'T YOU DARE TOUCH THE RESIZE HANDLES! If you do, the image will snap to the closest vertical sizing bars, and there's no way to return to the actual size of the image other than by reverting the page. Who had a lobotomy before coding that functionality, I wonder.

Sorry, Frank, but you need to read Avinoam's comment, above:

"The rationale for this change, among others, was that pixel level control was overwhelming for most users making it hard to create beautiful and readable content easily across any screen."

Atlassian would like us to believe that it was previously overwhelmingly difficult to work with images. Sadly, it's fake news, but you can be sure of one thing; the new editor certainly does now make it overwhelmingly difficult, nay impossible, to work with images. Great job, Atlassian.

Just switched from a on premise confluence to cloud version - I spent several hours the last two days to get used to the "improved" new editor. It is a mess! My goal is to present thumbnails of flipchart images in a neat way. No problem with the old editor, impossible with the new editor. No function to easily insert an already attached image file, no way to put several images in a row. Works like Instagramm but not like a pro wiki!

And I'm sure there is some "Atlassian is excited to announce the new editor"...

Guess I'm going back to HTML, much faster.

Laura. That's where you have misunderstood the new editor. It isn't intended to make your life easier.

Agreed with Andreas on the "ridiculous sizes" comment. There are many places in our documentation where we direct users to click a button by saying "click [button image]" - now when I attempt to use that method, the button appears larger than the original size and on a separate line. I have not yet found a scenario where the new cloud editor has made my life easier.

I think this new image sizing is a big mistake, because

a) it is not always working correctly, e.g. images snap to ridiculous sizes

b) it really limits the ability of Confluence to create visually pleasing pages

Just try creating a simple TOC style rows of an icon image followed by a text. Impossible! Tables would kind of work (but not really), but here you run into the problem that there is now way of hiding the table outlines

Very frustrating - Atlassian team please fix this!

PS: While fixing please add back the possibility that images can be links! How hard can it be? ... but this is probably another ticket.

@Avinoam - I've added a link with clearer examples of the sizing/resizing limitations users are running into.  Let me know if you can't access it and I can send you or one of the team the link directly.  Thanks! 

@Alan Gant, I fear the reverse is true. I believe you are the one who is missing the focus of Atlassian feedback. A decision has been made to dumb down the editor. It is being done in the interests of Atlassian under the pretence of helping its users.

I suspect Atlassian's grand plan is to disenfranchise all its savvy users (the ones who occasionally push Confluence to breaking point) and replace them with lower-caliber users who simply need access to a marginally glorified version of Notepad—the result of which will be that Atlassian reduces its support overhead, and dumb users remain contentedly coddled with a simple text editor.

If you point out a glaring bug, there may be some interest in resolving it at some point—but if you want to bring back functionality on Atlassian's kill list, forget it.

Avinoam, you seem to be missing the focus of all of the comments:  the ability to precisely set image size is not a burden, but a requirement!  Not all users of a Wiki are only trying to easily post information.  My company uses Confluence to create our printed documentation.  We must precisely set image sizes.  If this capability is not returned, we will have to abandon Confluence and find another platform.  We really do not want to do this!!!!!

If you still feel the need for quick and easy resizing, keep that functionality.  But provide a way for other users to precisely specify image size.

At this point, our use of Confluence is unusable.  Is there a way for me to raise the priority or criticality of this bug/regression?

I 100% agree with Chris and have expressed the same sentiment a number of times in multiple channels. I can't name another app I use that dumbs down image resizing in such a way.

Not sure I'd agree with the "quick" and "predictable resizing" parts of your statement @Avinoam Zelenko.
I am limited to a minimum size allowed when resizing images and many times the image does not stay at the size I attempted to resize it to.(jumps to a larger or smaller size) I have to adjust the size multiple times to get it to come close to something I actually want to publish taking up much more of my time to fuss with the image than in the previous editor.
 

We need control for exact sizes of images. Removing this feature is a huge loss of control. Please add it back.

 I agree, this is a huge loss of functionality that had previously been available.  This is a huge setback in in our use of Confluence as well.

On Monday Oct 28 in a Zoom meeting with Avinoam Zelenko, I reported that not only is the loss of fine image control a major hindrance, but image support in the new editor still includes several unresolved bugs. Is Atlassian doing its own testing, or is it relying its customers to perform all the testing? If so, can we please be reimbursed?

Bug 1 - left or right aligned/wrapped image sizing

If you left or right align or wrap an image and save the page, the image will be displayed expanded by about 400% in the saved page. The result is unusable.

Bug 2 - left or right aligned image in PDF export

If you left or right align an image in the new editor and export the page to PDF, the image will be WRAPPED/FLOATED left or right in the PDF (as if the wrap option had been selected), meaning the text flows around the edge of the image.

Bug 3 - left or right aligned/wrapped image in MS Word export**

Regardless of whether you left or right align or wrap an image in the new editor, when you export to MS Word, the image will left aligned (i.e., right align, left wrap, and right wrap are all replaced with left align).

Loss of this capability is a blocker for our use of Confluence.  If this capability is not returned, we will have to search for an alternate tool for our documentation.  Confluence has been a wonderful solution for us, but we are now forced to post-edit our documentation via Word export.  Prior to this change, we exported to PDF to distribute documentation to our customers.

This is a feature which was previously available and so not having it is a loss of functionality.  Not being able to set a specified image size is impeding our ability to design our Confluence pages to our needs. See also PSCLOUD-33439. 

 Also, copying and pasting the image sometimes results in the image randomly auto-sizing larger and it will not allow a reduction in size back to the original.