Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-17621

Support EXIF orientation so that images are displayed with the expected orientation

    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      Images taken with rotated cameras, iPhones etc. are displayed without compensation for that rotation. This means users have to rotate the image and save it in another program beforing inserting into Confluence in order to have the image displayed as expected. Images contain EXIF information that will allow Confluence to do this rotation for the users automatically.

            [CONFSERVER-17621] Support EXIF orientation so that images are displayed with the expected orientation

            Sen Geronimo made changes -
            Workflow Original: JAC Suggestion Workflow 4 [ 3564617 ] New: JAC Suggestion Workflow 3 [ 4330056 ]
            Robert Massaioli (Atlassian) made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 665950 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow 2 [ 3180647 ] New: JAC Suggestion Workflow 4 [ 3564617 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3040094 ] New: JAC Suggestion Workflow 2 [ 3180647 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2537589 ] New: JAC Suggestion Workflow [ 3040094 ]

            Kathryn Moye added a comment - - edited

            Go to https://jira.atlassian.com/browse/CONFSERVER-32762 and see their message.  At least they explain what is going on.

            Except FF is reporting this is going to be deprecated!  CSS image-rotation

            Warning: This property is likely to be deprecated in the near future, with its functionality moved into properties on the <img> and/or <picture>elements, with the possible exception of from-image. The flip and {{<angle>}}values were made obsolete as of FF63.

            Kathryn Moye added a comment - - edited Go to https://jira.atlassian.com/browse/CONFSERVER-32762  and see their message.  At least they explain what is going on. Except FF is reporting this is going to be deprecated!  CSS image-rotation Warning:  This property is likely to be deprecated in the near future, with its functionality moved into properties on the  <img>  and/or  <picture> elements, with the possible exception of  from-image . The  flip  and {{<angle>}}values were made obsolete as of FF63.

            Stefan Baader added a comment - - edited

            Two questions:

            1. why those fotos were displayd correctly before (with CONF 5.10)?

            2. how can we fix now hundreds of pages where this issue occurs?

            Since we updated from CONF 5.10 to 6.9 we have that issue too. Hundreds of pages are impacted were fotos are now shown in wrong rotation. With the old release it was correctly displayed.

            Why is issue CONFSERVER-32762 closed as "fixed" for 6.2.2?

            Please reopen and solve that issue. And by the way: I don't see it as a minor issue. It has an impact on the usability and readability. We have a lot of documentation in Confluence and the manufacturing teams have an impact on their work. Nobody has time to manually rotate hundreds of fotos in hundreds of pages.

            Even open source systems like WordPress are able to handle the orientation of those fotos from iPhone and iPad. Why not that professional expensive application  Confluence?

            Stefan Baader added a comment - - edited Two questions: 1. why those fotos were displayd correctly before (with CONF 5.10)? 2. how can we fix now hundreds of pages where this issue occurs? Since we updated from CONF 5.10 to 6.9 we have that issue too. Hundreds of pages are impacted were fotos are now shown in wrong rotation. With the old release it was correctly displayed. Why is issue CONFSERVER-32762 closed as "fixed" for 6.2.2? Please reopen and solve that issue. And by the way: I don't see it as a minor issue. It has an impact on the usability and readability. We have a lot of documentation in Confluence and the manufacturing teams have an impact on their work. Nobody has time to manually rotate hundreds of fotos in hundreds of pages. Even open source systems like WordPress are able to handle the orientation of those fotos from iPhone and iPad. Why not that professional expensive application  Confluence?

            We have the same issue in our company (4000 users, some 100K of pages). After release update to 6.9 suddenly a lot of existing images in existing pages are rotated. This is very very very awful and bad. Can't understand why Atlassian is not able and/or not willing to fix that. Even open source web applications like WordPress have no problem handling those images.

            Christian Stampfer added a comment - We have the same issue in our company (4000 users, some 100K of pages). After release update to 6.9 suddenly a lot of existing images in existing pages are rotated. This is very very very awful and bad. Can't understand why Atlassian is not able and/or not willing to fix that. Even open source web applications like WordPress have no problem handling those images.
            Alex Yakovlev (Inactive) made changes -
            Link New: This issue is related to CONFSRVDEV-6854 [ CONFSRVDEV-6854 ]

            licinia added a comment -

            Not userfriendly at all: most of picture viewer now supports Exif orientation. All imported images from my mobile are wrongly displayed!

            licinia added a comment - Not userfriendly at all: most of picture viewer now supports Exif orientation. All imported images from my mobile are wrongly displayed!

              Unassigned Unassigned
              aprentice Andrew Prentice (Inactive)
              Votes:
              12 Vote for this issue
              Watchers:
              21 Start watching this issue

                Created:
                Updated:
                Resolved: