I'm really put off by the wishy-washy pixel dimensions and aspect ratios. I have found about 15 different dimensions posted online - none of them are correct. Just give me a specified dimension in pixels and a "safe area" where to place important content. I think your current header platform is great for using the included photos but is totally unworkable if one is using custom graphics.
@Arshia Elahi - regarding your message on this thread:
We have heard your feedback regarding the header images, and we are currently working on a fix to this issue. Will keep you updated here.
I note that you posted it on 29 April but unless I've missed it there has been no further info from the Atlassian Team since then. The banners in my Confluence pages, which looked great until your 'Modernized Content Topper' was introduced, still look terrible - they are pixelated and cropped. It's clear from this thread that this issue continues to affect a significant number of users, and from what I can see this was first brought to Atlassian's attention as long ago as February this year, if not earlier. I'm sure I'm not alone in saying that I find it staggering that your team has not resolved the matter yet, or at the very least, provided your users with regular updates.
Can I request that Atlassian take the opportunity to provide now? If in fact a fix is not going to be implemented, I would like confirmation of that so that I can go and recreate all my toppers, which I have not done until now because I've been waiting for the fix you promised in April.
Atlassian Team members are employees working across the company in a wide variety of roles.
July 8, 2024 edited
@Marcus Schroenn Thank you for following up! There is an update in progress that will allow you to set your preference at the instance level, for fixed width or full width. We are finalizing the timeline, and will post here once completed. It should be within a month, or sooner.
I can confirm that this is working for us on Confluence Cloud. I won't even complain about the fact that I had to enable the new feature on each impacted document in order to recreate the original behavior, because I was only using header images on ~12 policy pages. But I do feel sympathy for the other poster who said something about this issue impacting a couple hundred pages.
I know prioritization of dev queues is complicated, but I'm still pretty amazed at how long it took for this feature to be released. Hopefully this stands as a cautionary tale for future consideration before deploying changes that remove functionality or alter behavior in ways that may have enormous impacts on existing users.
Thanks for the update! Is there any possibility to make the header a bit higher in size? Now, you really have to find the perfect picture in order to look good on the page.
Following Lee Schneider's comment above - I'm interested to know whether this feature Arshia Elahi of Atlassian announced in her post of 19 July has in fact resolved the issue of toppers getting cropped off/displaying at larger than the original size for other users:
We have recently implemented a feature to allow you to toggle between full and fixed width cover images.
It hasn't made any difference to my toppers. If I choose the 'Full Width' option, my toppers display massive - and heavily cropped on both the left and right. And if I choose Fixed Width, the scale of the banners is correct, as per my original design - but the sides are still heavily cropped off. So if this feature is intended to be the fix Atlassian promised, it hasn't fixed the issue in my case.
I haven't received responses to my emails to members of the Atlassian teams, hence this post. Is anyone else experiencing the same problem?
Now they have put the logo in front of the title on the space start page. So basically you have to live with the logo there or use an emoji.
It seems, there is no point in putting effort in the design of a Confluence page. Eventually, someone careless will pull the rug out from under you. What is wrong with these people?
@Arshia Elahi I have created a custom header in Canva for my page with a PNG file format. It uploads correctly, but when I refresh it disappears. Do you have a solve for this?
This is a weird design decision. It always crops your images to 800:147 aspect ratio (roughly 16:3), and then stretches it to the whole page. The 1800x140 logos that I made for my pages are now useless: they get cropped to 762x140 and are then stretched and pixelated to occupy half the screen. And if I select fixed size I end up with a 800x147 rectangle. Why?
I really like the feature BUT if it has sometimes it has a problem uploading the header and then nothing I can do will fix it. Sometimes it uploads a header I have created beautifully and it always resizes etc lovely!. But when it goes wrong I have to abandon headers on that page. It forces a stretch beyond the boundary of the page and crops the image, not matter the image or the image size. EVEN if I change it to fixed width, it will stretch and crop the image as if it has been stretched and cropped across and beyond the width of the page - DRIVING ME NUTS - please help
Hi All - I posted here 17 days ago. And no other comments have been made and no response has been provided, so there's that. The question I have is - why does the image get stretched beyond the page width. Can we have someone please provide a technical response as to what is happening under the hood? Last time I checked HTML there was pixels and percent for width 9it was a while ago, I admit), so what is going on - some feedback, response, acknowledgment would be appreciated.
Hey @Peter Herman - sorry to hear you are having issues.
For me it works great and my workaround is just load massive images and live with whatever it crops to for now - My pages are viewed on so many different devices and monitor/window sizes it would be a full time job to figure out the golden ratio that works for all.
Bear in mind this is a new tool and the teams been fairly active this year working in everyone's concerns. To be honest, there are more important fixes I would prefer these guys to be working on... but that's just my opinion.
I also hear your frustration at getting no answers on your first post, maybe thats because you didn't actually ask a question.
As your second post is more specific, I searched around and see that there are multiple threads out there all pointing here. If you want full width and don't want cropping I suggest designing your headers with white borders on the sides (like a print bleed) - you'll have to trial and error till you figure it out but this should solve your clipping issues.
Finally, If you want a response from the dev team you should probably tag the author. In this case @Arshia Elahi
Hi Arshia, can we get some sort of update as to what the underlying problem is with the "content topper" please. Any information would be appreciated. My observation is that sometimes it works great and header images are perfectly placed forevermore; and sometimes it doesn't and the image is stretched beyond the page edges and cropped. But when it doesn't work on a page, nothing on this Earth will make the page work ever again with any image. If we knew what the magic "first time on page" image load rules were, we would not have pages that were unrecoverable. Any information about what the problem is and why would be appreciated. ie: is it because of JPG rather than PNG? Does the first image have to be greater than or less than a certain size? Is it caused by the size of the image in kbytes? I have tried a range of tests and cannot find any consistent rules. Thoughts?
I've experienced the same/similar issues as you @Peter Herman
As regards responses or lack thereof from Atlassian, my experience: I posted my first comment on this thread on 4 April and received a response from @Alli Shea of Atlassian’s dev team the same day, requesting that I email screenshots of the issue. I did so but did not receive a response to my email - nor to any of my (three) follow-up mails, on which I also included @Arshia Elahi of the dev team. I did receive a response from Alli to my 8 July post on this thread, but not from any members of the dev team to my previous post of 6 August.
This banner issue is going to require a lot of rework on my part, and it seems for many other users who have posted on this thread, but a magic fix or rollback to the previous functionality seems very unlikely so I’ve pretty much accepted I’m going to have to redesign all my banners.
How to reset a Confluence page topper that has stretched: I used PowerPoint to draw a Tall Box (1395(w) x 882(tall) pixels), saved as a picture and loaded as a topper (can we call these headers?). It no longer stretched but place "tall" in the area, going high and low beyond boundary - ok so at least I had stopped the stretching.
What is the best height for a box: Again used PPT to create different sized boxes and saved as a picture (PNG). It seems 275 is a good full height (same width 1395)
Could my previous images be uploaded (without stretch) at 275 pixels: Tried to use the images at 275 height, fit the height but started stretching again.
What if I merged the 275 height box and my previous image: In PPT put my previous image over the 275 box, merged and saved as picture (PNG). Worked! Uploaded, did not stretch, full height.
Takeaway: Can work with it. But strange behaviour when an image has been composed from other images and saved as a banner image. But if go back to a basic object image, it seems to "calm it down" lol
72 comments