Cloud image sizing is fundamentally broken

[Norman Cates]

I am adding some icon size images to a page. 40px square.

When I add them, they come onto the page at a HUGE size. Hundreds of pixels square.

When I go to the options Original Size is selected. It is lying. The image is NOT showing at the original size.

I tried inline. That makes the images SMALLER than they actually are. (

I eventually found the option to "resize" the image, (After "Convert to Pixels") and I could enter 40px. But now there's the massive and annoying "Enter a caption" box that gets hugely tall because the icon is so small. And it pushes everything down the page until I'm not selecting the icon anymore.

I found (eventually) in the docs that Original Size apparently means "in its own block". 

Which is utterly wrong terminology. AND goes against what Original Size means in the Legacy Editor, where Original Size DOES give you the image at its ACTUAL size in pixels.

And If I may go back to "Convert to Pixels". The images are ALREADY PIXELS. That word choice is wrong.

Based on some context, I get the impression that if the image is not converted to pixels and just resized using the resize handles, its changing the percentage size of the image. I can only assume in relation to the section it's in. 

But no where does it give you a percentage indicator.

Neither does it give you a numerical value for the number of pixels the image is being resized to if its in that mode, and you're using the handles.

As far as I am concerned almost every UI choice here is wrong.

Also, the image does not scale proportionately when I resize the browser. It just stays exactly the same size.

So what exactly is the point of Convert to Pixels. It gives you nothing useful, except a box you can type your pixel size in.

And what is this blob format that images now show up in when we right click on them in the browser.

It DEFINATELY means we can't download the images. Nor can we link to them from elsewhere.

I can see that with Cloud Editor they have tried to make it simpler to use.

Laudable, but its gone far too far into "simple". And they are making decisions on our behalf as if we are idiot children.

Lowest common denominator gets you a grey sludge of mediocrity.

[Kris Klima _K15t_]

Hi @Norman Cates 

Can you, pls, share a screenshot and specify the image file type?

I was able to insert and adjust images into a Confluence page both as a regular 'big picture' and as an inline image. I also managed to convert a regular image to inline and back.

[Norman Cates]

The images are 40px x 40px PNG with transparent areas.

This is three of them, resized to 40 x 40 px, after using Convert to Pixels. And set to wrap left.

Below is an example of making the icon inline. Its a lot smaller than the actual icon size. 

And the inline image size can't be changed. So will always be tiny. I'm struggling to see the point.

The big image is what happens when we bring these icons in, or change it from inline to Original Size. 

I know that image handling can be tricky. But this isn't helping.

I think its trying for a few modes of image usage. 
Image in its own block, in the middle, left, right of the secton, and able to have text wrapped around it.

I get that. 

But inline as it stands is... not at all useful. Inline for images in HTML basically means that they are treated as characters on the line. So they can line up on the line, get moved across with text. And so on. A lot of the time, its not very useful. BUT in some situations its essential. Like if I want to line up 3 or 4 of these icons on a line, forming a block with them all touching. At their actual size. Can't do it with how images work at the moment.

Now, to be fair, the Legacy editor wasn't exactly slick in that area, but it did let inline images basically work,