• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • None
    • Chrome 50.0.2661.26 beta (64-bit)
      Chromium 51.0.2673.0 (64-bit)

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

      Problem

      Using Chrome 50, Confluence editor will render half its height, causing UI usability problems, see the screenshot:

      Normally, the button bar would appear at the bottom of the browser, and the editor would take the full height. It works fine in Chrome 49 stable release and other browsers.

      Steps to reproduce
      1. Install Chrome 50.x
      2. Open Confluence and edit a page
      Cause

      The affected version of Chrome introduced the following bug that is related to the issue: display: table-row; doesn't work with height: 100%; .

      Workaround

      Apply the following stylesheet to Confluence Admin > Custom HTML > At end of the HEAD

      <style type="text/css">
      #content.edit
      { display: table-cell; }
      </style>
      

      Note: If the workaround appears to revert after a restart, but the custom HTML is still present, verify that there are no space level customizations in the affected area.

      Resolution

      Upgrade to a release that contains the fix (Confluence 5.9.7 or higher).

        1. CONF-41035-Footer.JPG
          CONF-41035-Footer.JPG
          101 kB
        2. ConfluenceRefinedThemewFix.png
          ConfluenceRefinedThemewFix.png
          32 kB
        3. image-2016-03-13-08-59-03-220.png
          image-2016-03-13-08-59-03-220.png
          79 kB
        4. MeetingBlueprint.png
          MeetingBlueprint.png
          42 kB
        5. MeetingNotes_5.9.6.png
          MeetingNotes_5.9.6.png
          17 kB
        6. render_error.png
          render_error.png
          108 kB
        7. screenshot-1.png
          screenshot-1.png
          199 kB

          Form Name

            [CONFCLOUD-41035] Editor shows at half height when using Chrome 50+

            Followup ... we should probably add Confluence 5.5 to the "Affected Versions" for this ticket, although the Workaround does not seem to work.

            Nevertheless, the solution in our case was suggested by Stephen Belknap's comment above. (Thank you Stephen!)

            When we upgraded Chromium from 50.0.2661.75 to a later build, 50.0.2661.102, this resolved the problem.

            Fred Bunting added a comment - Followup ... we should probably add Confluence 5.5 to the "Affected Versions" for this ticket, although the Workaround does not seem to work. Nevertheless, the solution in our case was suggested by Stephen Belknap's comment above. (Thank you Stephen!) When we upgraded Chromium from 50.0.2661.75 to a later build, 50.0.2661.102 , this resolved the problem.

            The Workaround seemed to have no effect for us ... we are still seeing the problem.

            We are still on Confluence 5.5 ... which I don't see listed under the "Versions Affected" on this ticket.

            Is it possible that the Workaround instructions would be different for Confluence 5.5?

            Fred Bunting added a comment - The Workaround seemed to have no effect for us ... we are still seeing the problem. We are still on Confluence 5.5 ... which I don't see listed under the "Versions Affected" on this ticket. Is it possible that the Workaround instructions would be different for Confluence 5.5?

            Nam Ho added a comment -

            Hi vernice.recomite,
            I think it still work except that your message modify style or structure of the editor.
            Please tell me if it doesn't.

            Regards,
            Nam

            Nam Ho added a comment - Hi vernice.recomite , I think it still work except that your message modify style or structure of the editor. Please tell me if it doesn't. Regards, Nam

            Hi, Nam.

            The workaround applied worked. However, we recently added a banner message for Confluence users and we changed the contents of "At end of the HEAD", so the workaround was rolled back.

            Will this still work with the message plus the workaround both in the "At end of the HEAD"?

            Thanks,
            Bam

            Bam Recomite added a comment - Hi, Nam. The workaround applied worked. However, we recently added a banner message for Confluence users and we changed the contents of "At end of the HEAD", so the workaround was rolled back. Will this still work with the message plus the workaround both in the "At end of the HEAD"? Thanks, Bam

            Fred Bunting added a comment - - edited

            @TedKim, when you say 'solution from Atlassian to upgrade", please state the version.

            Update: Never mind ... I see it is in the Resolution above (5.9.7).

            Fred Bunting added a comment - - edited @TedKim, when you say 'solution from Atlassian to upgrade", please state the version. Update: Never mind ... I see it is in the Resolution above (5.9.7).

            Teodore added a comment -

            I have also encountered this symptom, so got received a solution from Atlassian to upgrade confluence and workaround as commented in above.

            But,
            it happened in Chrome 50.0.2661.78m, but not happened in now 50.0.2661.94m........

            Maybe fixed automatically by updated....

            Teodore added a comment - I have also encountered this symptom, so got received a solution from Atlassian to upgrade confluence and workaround as commented in above. But, it happened in Chrome 50.0.2661.78m, but not happened in now 50.0.2661.94m........ Maybe fixed automatically by updated....

            I would check if your Theme is part of the issue. We are running Confluence 5.8.10 & RefinedTheme 5.0.3 and I've removed the CSS tweaks above, so far so good with just the Chrome 50.0.2661.87 m release.

            David Puchosic added a comment - I would check if your Theme is part of the issue. We are running Confluence 5.8.10 & RefinedTheme 5.0.3 and I've removed the CSS tweaks above, so far so good with just the Chrome 50.0.2661.87 m release.

            Eduardo Casarero added a comment - - edited

            Hi in my confluence 5.8.10 the problem happens not in edit mode, after login there is a blank space and we have to scroll down to see part of the page, running Version 50.0.2661.87. Is this related to this issues? or should I open a new one?

            thanks!

            Eduardo Casarero added a comment - - edited Hi in my confluence 5.8.10 the problem happens not in edit mode, after login there is a blank space and we have to scroll down to see part of the page, running Version 50.0.2661.87. Is this related to this issues? or should I open a new one? thanks!

            John Love added a comment -

            Version 50.0.2661.87 m works on 5.8.10, 5.8.18 & 5.9.6 too. This is great news.

            John Love added a comment - Version 50.0.2661.87 m works on 5.8.10, 5.8.18 & 5.9.6 too. This is great news.

            bels added a comment -

            I upgrade Chrome this morning and as of Version 50.0.2661.87 m it works on my Confluence instance, 5.5.1.

            bels added a comment - I upgrade Chrome this morning and as of Version 50.0.2661.87 m it works on my Confluence instance, 5.5.1 .

            Ray Crowley added a comment - New Chrome build coming: https://bugs.chromium.org/p/chromium/issues/detail?id=603507

            Julia Lahn added a comment -

            The following documentation is out of date. It still claims that the bug ony appears for Confluence Versions less that 5.1.3: https://confluence.atlassian.com/confkb/editor-window-is-small-when-using-google-chrome-365003598.html

            Julia Lahn added a comment - The following documentation is out of date. It still claims that the bug ony appears for Confluence Versions less that 5.1.3: https://confluence.atlassian.com/confkb/editor-window-is-small-when-using-google-chrome-365003598.html

            John Love added a comment - - edited

            David,

            The behavior above is interesting. It looks like that template in 5.8.x of Confluence is not playing nice with RefinedWiki. We also use RefinedWiki (4.2.18 in prod and 5.0.3) in test. I hadn't noticed this before the Chrome issue, but the Meeting Note template is actually flipping to a Confluence themed header when you are in Create mode. We have 5.9.6 of Confluence and 5.0.3 of RefinedWiki in a test instance and it does not have this issue.

            I think the hack that I posted yesterday works well with the Meeting Notes template.

            John Love added a comment - - edited David, The behavior above is interesting. It looks like that template in 5.8.x of Confluence is not playing nice with RefinedWiki. We also use RefinedWiki (4.2.18 in prod and 5.0.3) in test. I hadn't noticed this before the Chrome issue, but the Meeting Note template is actually flipping to a Confluence themed header when you are in Create mode. We have 5.9.6 of Confluence and 5.0.3 of RefinedWiki in a test instance and it does not have this issue. I think the hack that I posted yesterday works well with the Meeting Notes template.

            David Puchosic added a comment - - edited

            @Jonathan After the display table-cell fix, I had that issue with Custom HTML and moved our div to "At end of the HEAD" and that resolved our Dev annoucement. However, we are still having an issue with the Create Meeting Note blueprint displaying in a similar way. (Confluence 5.8.10, RefinedWiki 5.0.3, Chrome 50+). I'll explore some of these other fixes.

            David Puchosic added a comment - - edited @Jonathan After the display table-cell fix, I had that issue with Custom HTML and moved our div to "At end of the HEAD" and that resolved our Dev annoucement. However, we are still having an issue with the Create Meeting Note blueprint displaying in a similar way. (Confluence 5.8.10, RefinedWiki 5.0.3, Chrome 50+). I'll explore some of these other fixes.

            John Love added a comment -

            This is a complete hack, but we went with this work around as it works pretty well regardless of Admin login or regular user. It basically detects all of the common screen heights we use in the office and sets the edit window height appropriately. It may be too drastic for many, but we've had in place since late Thursday 4/13 in our production instance (5.8.10) with no complaints. Also using on test instances at 5.8.18 and 5.9.6. This should work for us until we have time to upgrade to 5.9.7 or later. The majority of our users use IE10, 11 or chrome and a few use Firefox. I personally use Safari from home with no issues.

            <style type="text/css">
            /* Temp fix for chrome */
            @media screen and (min-height:600px) {
            #content.edit {
            height: 600px !important;
            }
            }

            @media screen and (min-height:720px) {
            #content.edit {
            height: 720px !important;
            }
            }

            @media screen and (min-height:768px) {
            #content.edit {
            height: 768px !important;
            }
            }

            @media screen and (min-height:864px) {
            #content.edit {
            height: 864px !important;
            }
            }

            @media screen and (min-height:900px) {
            #content.edit {
            height: 900px !important;
            }
            }

            @media screen and (min-height:960px) {
            #content.edit {
            height: 960px !important;
            }
            }

            @media screen and (min-height:1024px) {
            #content.edit {
            height: 1024px !important;
            }
            }

            @media screen and (min-height:1050px) {
            #content.edit {
            height: 1050px !important;
            }
            }

            @media screen and (min-height:1080px) {
            #content.edit {
            height: 1080px !important;
            }
            }

            @media screen and (min-height:1200px) {
            #content.edit {
            height: 1024px !important;
            }
            }
            </style>

            John Love added a comment - This is a complete hack, but we went with this work around as it works pretty well regardless of Admin login or regular user. It basically detects all of the common screen heights we use in the office and sets the edit window height appropriately. It may be too drastic for many, but we've had in place since late Thursday 4/13 in our production instance (5.8.10) with no complaints. Also using on test instances at 5.8.18 and 5.9.6. This should work for us until we have time to upgrade to 5.9.7 or later. The majority of our users use IE10, 11 or chrome and a few use Firefox. I personally use Safari from home with no issues. <style type="text/css"> /* Temp fix for chrome */ @media screen and (min-height:600px) { #content.edit { height: 600px !important; } } @media screen and (min-height:720px) { #content.edit { height: 720px !important; } } @media screen and (min-height:768px) { #content.edit { height: 768px !important; } } @media screen and (min-height:864px) { #content.edit { height: 864px !important; } } @media screen and (min-height:900px) { #content.edit { height: 900px !important; } } @media screen and (min-height:960px) { #content.edit { height: 960px !important; } } @media screen and (min-height:1024px) { #content.edit { height: 1024px !important; } } @media screen and (min-height:1050px) { #content.edit { height: 1050px !important; } } @media screen and (min-height:1080px) { #content.edit { height: 1080px !important; } } @media screen and (min-height:1200px) { #content.edit { height: 1024px !important; } } </style>

            Jonathan added a comment -

            this is what the workaround produces when you have an active notification bar, like being logged-in with admin access:

            Jonathan added a comment - this is what the workaround produces when you have an active notification bar, like being logged-in with admin access:

            Nam Ho added a comment -

            smcdonald1123089805 the workaround works well in older versions of Chrome and other browsers

            Nam Ho added a comment - smcdonald1123089805 the workaround works well in older versions of Chrome and other browsers

            Does adding the workaround affect display in older versions of Chrome or any other browsers?

            smcdonald20 added a comment - Does adding the workaround affect display in older versions of Chrome or any other browsers?

            Michael Cohen added a comment - - edited

            One of our spaces has a layout in Main Layout that uses code like:

            
            

            $helper.renderConfluenceMacro("

            {excerpt-include:FOO:Foo Footer|nopanel = true}

            ")

            {/code}

            where "Foo Footer" is a page in FOO space that is used as a footer for all pages in the FOO space.

            This workaround generates a poor experience when editing pages with this footer - the footer is pushed over to the next 'page' instead of below the edit button (which is where it was previously). I attach "CONF-41035-Footer.jpg" as an example.

            Michael Cohen added a comment - - edited One of our spaces has a layout in Main Layout that uses code like: $helper.renderConfluenceMacro(" {excerpt-include:FOO:Foo Footer|nopanel = true} ") {/code} where "Foo Footer" is a page in FOO space that is used as a footer for all pages in the FOO space. This workaround generates a poor experience when editing pages with this footer - the footer is pushed over to the next 'page' instead of below the edit button (which is where it was previously). I attach " CONF-41035 -Footer.jpg" as an example.

            Verified that Cornell University the fix works with Confluence 5.6.6.

            Eric Gasior added a comment - Verified that Cornell University the fix works with Confluence 5.6.6.

            Thank you for the workaround, confluence24. The issue description has been updated to include this.

            Robert Chang added a comment - Thank you for the workaround, confluence24 . The issue description has been updated to include this.

            John Love added a comment -

            Excellent!

            John Love added a comment - Excellent!

            Excellent idea. Nice simple work around.

            Aaron Wyatt added a comment - Excellent idea. Nice simple work around.

            We believe we've successfully worked around this bug with Confluence 5.8.18 with about 3,000 spaces by adding the CSS "fix" to the Custom HTML "At end of the HEAD" section the admin console. It loads with every page. We have spaces with the Global Look and Feel theme as well as the older Documentation theme and spaces with custom style sheets, so this was the fastest way to fix them all for us. Because of our variety of themes and custom stylesheets, adding the fix to the global stylesheet only fixed a portion of our spaces.
            <style type="text/css">
            #content.edit {
            display: table-cell;
            }
            </style>

            CIT Commercial Applications added a comment - We believe we've successfully worked around this bug with Confluence 5.8.18 with about 3,000 spaces by adding the CSS "fix" to the Custom HTML "At end of the HEAD" section the admin console. It loads with every page. We have spaces with the Global Look and Feel theme as well as the older Documentation theme and spaces with custom style sheets, so this was the fastest way to fix them all for us. Because of our variety of themes and custom stylesheets, adding the fix to the global stylesheet only fixed a portion of our spaces. <style type="text/css"> #content.edit { display: table-cell; } </style>

            Max Pavlov added a comment - - edited

            But if one logs in as admin and tries to edit a page with this style on, the following "cell" will be spanned vertically:
            http://prnt.sc/asqm7k

            Max Pavlov added a comment - - edited But if one logs in as admin and tries to edit a page with this style on, the following "cell" will be spanned vertically: http://prnt.sc/asqm7k

            John Love added a comment -

            But 5.9.7 has been corrected?

            John Love added a comment - But 5.9.7 has been corrected?

            Hi Aaron,
            Indeed global CSS will only overwrite the global theme. Spaces using a different theme or their own custom CSS will need to have the workaround applied individually via Space Tools.

            Hi John,
            As far as I could see on the Chrome bug report, they will not fix this, as they regard it as intended behaviour:

            Comment 12 by dgro...@chromium.org, Mar 21, 2016
            Status: WontFix
            This behavior is intentional, closing as WontFix.

            Arthur Arnold (Inactive) added a comment - Hi Aaron, Indeed global CSS will only overwrite the global theme. Spaces using a different theme or their own custom CSS will need to have the workaround applied individually via Space Tools. Hi John, As far as I could see on the Chrome bug report, they will not fix this, as they regard it as intended behaviour: Comment 12 by dgro...@chromium.org, Mar 21, 2016 Status: WontFix This behavior is intentional, closing as WontFix.

            John Love added a comment - - edited

            50.0.2661.75 m exhibits the problem in our Prod 5.8.10, and test instances at 5.8.18 & 5.9.6.

            It's no longer a beta version issue.

            John Love added a comment - - edited 50.0.2661.75 m exhibits the problem in our Prod 5.8.10, and test instances at 5.8.18 & 5.9.6. It's no longer a beta version issue.

            When I apply the global custom CSS it seems to resolve the problem only for the current site theme-- in our case the Documentation Theme-- but not for other themes used by other spaces.

            Aaron Wyatt added a comment - When I apply the global custom CSS it seems to resolve the problem only for the current site theme-- in our case the Documentation Theme-- but not for other themes used by other spaces.

            The global stylesheet only applies to spaces where custom CSS has not been defined. You will still need to add the CSS fix to spaces that have their own stylesheets.

            You can get a list of these spaces with the following SQL query:

            SELECT bandanacontext, bandanavalue FROM bandana WHERE bandanakey = 'atlassian.confluence.css.resource.custom'

            Daniel Eads {unmonitored account} added a comment - The global stylesheet only applies to spaces where custom CSS has not been defined. You will still need to add the CSS fix to spaces that have their own stylesheets. You can get a list of these spaces with the following SQL query: SELECT bandanacontext, bandanavalue FROM bandana WHERE bandanakey = 'atlassian.confluence.css. resource .custom'

            Users at our company also complain about this issue with confluence 5.7.1 and chrome 50.0.2662.75 m.

            M Hoogenboom added a comment - Users at our company also complain about this issue with confluence 5.7.1 and chrome 50.0.2662.75 m.

            https://support.atlassian.com/browse/CSP-173301 with version 50.0.2661.66 beta

            Omar Raissi (Inactive) added a comment - https://support.atlassian.com/browse/CSP-173301 with version 50.0.2661.66 beta

            Branno (Inactive) added a comment - - edited

            max.milton1889578825,

            You had commented on a page that was deleted (in our Confluence Knowledge Base Space) asking about fixing the bug that causes the editor to render at half-height. There is a workaround located on this bug report but it will be fixed in 5.9.7 when it is released.

            Cheers,
            Stephen Brannen | Confluence Support

            Branno (Inactive) added a comment - - edited max.milton1889578825 , You had commented on a page that was deleted (in our Confluence Knowledge Base Space) asking about fixing the bug that causes the editor to render at half-height. There is a workaround located on this bug report but it will be fixed in 5.9.7 when it is released. Cheers, Stephen Brannen | Confluence Support

            I believe the real root cause to be this issue: https://bugs.chromium.org/p/chromium/issues/detail?id=594376

            jonah (Inactive) added a comment - I believe the real root cause to be this issue: https://bugs.chromium.org/p/chromium/issues/detail?id=594376

            Doug added a comment -

            Reproduced the problem.

            Chrome Canary - Version 51.0.2679.0 canary (64-bit)
            Confluence 5.9.5
            Windows 7 Pro SP1

            Doug added a comment - Reproduced the problem. Chrome Canary - Version 51.0.2679.0 canary (64-bit) Confluence 5.9.5 Windows 7 Pro SP1

            Takuya Otani added a comment - - edited

            Thanks nhoxuan, oh, thanks.

            Yes, that's much better (I thought I've tried display: table-cell, but apparently I didn't).

            Takuya Otani added a comment - - edited Thanks nhoxuan , oh, thanks. Yes, that's much better (I thought I've tried display: table-cell , but apparently I didn't).

            Nam Ho added a comment - - edited

            Thanks, takuya.otani1992178601. However I think we better use this:

            CSS snippet
            #content.edit {
                display: table-cell;
            }
            

            Nam Ho added a comment - - edited Thanks, takuya.otani1992178601 . However I think we better use this: CSS snippet #content.edit { display: table-cell; }

            Just FYI: I've applied the following styles via Stylish extension for workaround:

            CSS snippet
            #main .edit#content {
                height: calc(100% - 42px);
                width: 100%;
                position: absolute!important;
            }
            

            Hope it helps.

            Takuya Otani added a comment - Just FYI: I've applied the following styles via Stylish extension for workaround: CSS snippet #main .edit#content { height: calc(100% - 42px); width: 100%; position: absolute!important; } Hope it helps.

            Minh Tran added a comment - - edited

            randrade For your information about this bug, you could see more thing in https://jira.atlassian.com/browse/CONF-40673
            Yes, it is related to the Chromium bug https://bugs.chromium.org/p/chromium/issues/detail?id=594376

            Minh Tran added a comment - - edited randrade For your information about this bug, you could see more thing in https://jira.atlassian.com/browse/CONF-40673 Yes, it is related to the Chromium bug https://bugs.chromium.org/p/chromium/issues/detail?id=594376

            Latest OD but also have a local instance that shows the same issue and haven't upgraded versions so wondering if it's a latest chrome thing.

            Roberto Andrade added a comment - Latest OD but also have a local instance that shows the same issue and haven't upgraded versions so wondering if it's a latest chrome thing.

            Minh Tran added a comment -

            Dear roberto.andrade,

            Thanks for submitting the ticket
            Would you please let me know what affect version of Confluence that you met this issue?

            Thanks,
            Minh Tran
            Confluence BugMaster
            Atlassian

            Minh Tran added a comment - Dear roberto.andrade , Thanks for submitting the ticket Would you please let me know what affect version of Confluence that you met this issue? Thanks, Minh Tran Confluence BugMaster Atlassian

              nhoxuan Nam Ho
              f089a18c59c1 Roberto Andrade
              Affected customers:
              5 This affects my team
              Watchers:
              78 Start watching this issue

                Created:
                Updated:
                Resolved: