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

Change default behaviour of enter to a new paragraph (new line, but with no margins). A user can press enter twice to create space between elements.

    • 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.

      When you type enter in the rich text editor, a paragraph is created – this should be a line break, two of which in succession should produce a paragraph.

      In a table, the paragraph is converted to a break, which is inconsistent.

      Multiple empty paragraphs should become escaped newlines (
      ), but don't.

      Most people don't know they can press SHIFT+ENTER to achieve this effect in the RTE. It's not discoverable.

            [CONFSERVER-5949] Change default behaviour of enter to a new paragraph (new line, but with no margins). A user can press enter twice to create space between elements.

            I'm shocked this hasn't been addressed. No one instinctively expects ENTER to add a newline and some magical empty line they can't even see of easily delete. Since the dawn of computing the expectation of pressing ENTER is getting one newline. This is very poor UI design.

             

            Paul.Paella added a comment - I'm shocked this hasn't been addressed. No one instinctively expects ENTER to add a newline and some magical empty line they can't even see of easily delete. Since the dawn of computing the expectation of pressing ENTER is getting one newline. This is very poor UI design.  

            Most people don't know they can press SHIFT+ENTER to achieve this effect in the RTE. It's not discoverable.

            To me, this is the main problem. The actual design is great, once you know it. I disliked the new editor passionately, until I learned this.. and now I love it! 

            Can we get creative and just think of a simple way to make this behaviour more discoverable for the average user? Knowledge is power, and it should also be a lot more cost-effective!

            Stephen Wrathall added a comment - Most people don't know they can press SHIFT+ENTER to achieve this effect in the RTE. It's not discoverable. To me, this is the main problem. The actual design is great, once you know it. I disliked the new editor passionately,  until I learned this.. and now I love it!  Can we get creative and just think of a simple way to make this behaviour more discoverable for the average user? Knowledge is power, and it should also be a lot more cost-effective!

            I would love this feature. Unfortunate.

            Karl Kuzbiel added a comment - I would love this feature. Unfortunate.

            Closed Won't Fix.

            So the most likely scenarios are:

            • someone in product or development strongly likes this feature and thinks that people who don't are idiots
              OR
            • the code is written so poorly that it makes what should be a relatively small change into an expensive fix

            So we have two likely possibilities:

            1. Someone's pride is more important than user satisfaction
            2. This is a poorly written product

            Either way this does not reflect well on Atlassian

            Deleted Account (Inactive) added a comment - - edited Closed Won't Fix. So the most likely scenarios are: someone in product or development strongly likes this feature and thinks that people who don't are idiots OR the code is written so poorly that it makes what should be a relatively small change into an expensive fix So we have two likely possibilities: Someone's pride is more important than user satisfaction This is a poorly written product Either way this does not reflect well on Atlassian

            Reopen this issue. This is profoundly annoying. The Jira interface in general is getting more cluttered and bulky by default. Please stop making our jobs harder, and please stop making it so difficult to change simple interface issues like these. If I had it my way, we'd be looking for an alternative to Jira right now.

            Benjamin Smith added a comment - Reopen this issue. This is profoundly annoying. The Jira interface in general is getting more cluttered and bulky by default. Please stop making our jobs harder, and please stop making it so difficult to change simple interface issues like these. If I had it my way, we'd be looking for an alternative to Jira right now.

            I found out that the right click paste as plain text (ctrl+shift+v) option does exactly what people want, pasting with single lines.
            Note that the keyboard macro ctrl+shift+v will paste double lines. 

            the keyboard macro =/= right click option macro. Another case of it's not a bug it's a feature.
            I hope this helps other people. 

            Marlon Leong added a comment - I found out that the right click paste as plain text (ctrl+shift+v) option does exactly what people want, pasting with single lines. Note that the keyboard macro ctrl+shift+v will paste double lines.  the keyboard macro =/= right click option macro. Another case of it's not a bug it's a feature. I hope this helps other people. 

            skromer added a comment -

            My gosh, agreed.  Amazingly annoying.

            skromer added a comment - My gosh, agreed.  Amazingly annoying.

            I have just started to use confluence and this is REALLY annoying that this can't be part of the formatting.

             

            How hard would it be given that it's already in the background code.  All Confluence would need to do is provide an option to adjust down to 1.5, 1.6, 1.7, 1.8, 1.9, 2.0 etc.

            I think it's a really poor feature to ignore and "not fix".

            Vixtro Projects added a comment - I have just started to use confluence and this is REALLY annoying that this can't be part of the formatting.   How hard would it be given that it's already in the background code.  All Confluence would need to do is provide an option to adjust down to 1.5, 1.6, 1.7, 1.8, 1.9, 2.0 etc. I think it's a really poor feature to ignore and "not fix".

            Jeff L added a comment -

            I am not sure what you mean by the behavior being difficult to implement.  At least in the Atlassian Jira context, removing the entire editing control and replacing it with a simple html edit control would offer far superior usability and would be simple both from a maintenance and initial implementation perspective.  Any "correct" version should use that as a minimum acceptable baseline.

            And by the way, in the Jira comment context, shift-enter and insert wiki markup are not options.  I would be thrilled if the problem could be solved as easily as that.

            Jeff L added a comment - I am not sure what you mean by the behavior being difficult to implement.  At least in the Atlassian Jira context, removing the entire editing control and replacing it with a simple html edit control would offer far superior usability and would be simple both from a maintenance and initial implementation perspective.  Any "correct" version should use that as a minimum acceptable baseline. And by the way, in the Jira comment context, shift-enter and insert wiki markup are not options.  I would be thrilled if the problem could be solved as easily as that.

            This behavior is poor UI. Atlassian chooses to burden users with editing each line (from copy & paste) and have clairvoyance that Shift-Enter is the magic keystroke. So much about content-management and editing is the final appearance; Atlassian's logic on this issue is obtuse.

            A better solution would be to standardize the behavior no matter how text is entered and then direct users on how to adjust the Paragraph line spacing in the CSS. Atlassian demonstrates again why upgrading bodes more penalty than gain.

            Greg Jaeger added a comment - This behavior is poor UI. Atlassian chooses to burden users with editing each line (from copy & paste) and have clairvoyance that Shift-Enter is the magic keystroke. So much about content-management and editing is the final appearance; Atlassian's logic on this issue is obtuse. A better solution would be to standardize the behavior no matter how text is entered and then direct users on how to adjust the Paragraph line spacing in the CSS. Atlassian demonstrates again why upgrading bodes more penalty than gain.

            I believe this should be addressed too. Keeping consistent formating after pasting from a plain text file is very un-intuitive for users.

            Raphael Carrier added a comment - I believe this should be addressed too. Keeping consistent formating after pasting from a plain text file is very un-intuitive for users.

            Please note a request for a compromise solution is now open. Please vote if you think it will help your users. I now copy paste most everything that goes into confluence using the Insert | Wiki Markup to avoid this.

            https://jira.atlassian.com/browse/CONF-27326

            Ethan Foulkes added a comment - Please note a request for a compromise solution is now open. Please vote if you think it will help your users. I now copy paste most everything that goes into confluence using the Insert | Wiki Markup to avoid this. https://jira.atlassian.com/browse/CONF-27326

            Sam Kenny added a comment - - edited

            But how do you insert a line of text directly under a heading? If I use shift enter the next line is also a heading. If I change this to paragraph then the heading above now changes to paragraph.

            Sam Kenny added a comment - - edited But how do you insert a line of text directly under a heading? If I use shift enter the next line is also a heading. If I change this to paragraph then the heading above now changes to paragraph.

            Hi Everyone,
            This issue has been open since 2006. We recently tried to tackle this problem when looking at launching Confluence 4.0 and spent a significant amount of time on the roadmap trying to find a feasible solution to the problem. Long-story short, we feel the cost to implement this is very significant and is not feasible given the amount of demand we have received for this feature request.

            I'm going to mark this issue as "Won't Fix" as we've removed it from our roadmap and isn't something we plan to do in the forseeable future. If something comes up again and we feel this is much more feasible we will re-visit this issue.
            Sherif

            Sherif Mansour added a comment - Hi Everyone, This issue has been open since 2006. We recently tried to tackle this problem when looking at launching Confluence 4.0 and spent a significant amount of time on the roadmap trying to find a feasible solution to the problem. Long-story short, we feel the cost to implement this is very significant and is not feasible given the amount of demand we have received for this feature request. I'm going to mark this issue as "Won't Fix" as we've removed it from our roadmap and isn't something we plan to do in the forseeable future. If something comes up again and we feel this is much more feasible we will re-visit this issue. Sherif

            Lulu Smith added a comment -

            It took me too long rooting around the help docs to learn that this behavior is by design, not just specific to my settings. Please do change the default. I agree, SHIFT+ENTER is not discoverable, and the existing default is a less-frequent use case than just creating a line break. Thanks.

            Lulu Smith added a comment - It took me too long rooting around the help docs to learn that this behavior is by design, not just specific to my settings. Please do change the default. I agree, SHIFT+ENTER is not discoverable, and the existing default is a less-frequent use case than just creating a line break. Thanks.

            Don Willis added a comment -

            Since this is a matter of taste, I think most people would consider it an improvement requests rather than a bug. I just spent way too long trying to find this issue because I assumed it was an improvement request.

            Don Willis added a comment - Since this is a matter of taste, I think most people would consider it an improvement requests rather than a bug. I just spent way too long trying to find this issue because I assumed it was an improvement request.

            Don Willis added a comment -

            Single newlines can actually be done in the RTE by hitting SHIFT-Enter.

            Don Willis added a comment - Single newlines can actually be done in the RTE by hitting SHIFT-Enter.

            Unfortunately this is a matter of taste/style. Maybe it needs to be a per-space or wiki-wide preference. I want WYSIWYG to use HTML paragraphs instead of <br> because it makes the resulting HTML more reasonable, instead of being one big paragraph with <br> <br> for double-spaced paragraphs.

            Just my opinion.

            Allan Pratt added a comment - Unfortunately this is a matter of taste/style. Maybe it needs to be a per-space or wiki-wide preference. I want WYSIWYG to use HTML paragraphs instead of <br> because it makes the resulting HTML more reasonable, instead of being one big paragraph with <br> <br> for double-spaced paragraphs. Just my opinion.

            David Reid added a comment -

            This is a MAJOR dissatisfier with our user community.

            Our user community's highest requirements in a Wiki are ease of use and minimal needless whitespace. (Ease of use since our user community wants a Wiki on par with email/word processing. Minimal whitespace since they don't want the page needlessly long).

            This behavior, creating a doublespace (paragraph) instead of a singlespace (line break), breaks both of these requirements.

            Help

            David Reid added a comment - This is a MAJOR dissatisfier with our user community. Our user community's highest requirements in a Wiki are ease of use and minimal needless whitespace. (Ease of use since our user community wants a Wiki on par with email/word processing. Minimal whitespace since they don't want the page needlessly long). This behavior, creating a doublespace (paragraph) instead of a singlespace (line break), breaks both of these requirements. Help

              smansour Sherif Mansour
              tom@atlassian.com Tom Davies
              Votes:
              8 Vote for this issue
              Watchers:
              33 Start watching this issue

                Created:
                Updated:
                Resolved: