Seems to still be a problem in 7.5.1

We are running 5.9.1 and this issue is still present - please reopen the issue and do not mark the issue resolved until your customers state it is resolved.

Hi Atlassians,

I see a strange mix-up of  this issue and  CONF-15860 ( request for control option on insert-mode BLOCK/INLINE in  the user macro definition) which was closed as duplicate to this issue.
Is that really provided  by the resolve of this issue ?
I was referred to issue CONF-15860  because of an other problem which was reported there.

The problem is, that adding a (user) macro always adds a newline, despite the setting

<ac:parameter ac:name="atlassian-macro-output-type">INLINE</ac:parameter>

This is reported and well described  > 2 years ago in http://stackoverflow.com/questions/23767907/automatic-line-break-when-inserting-user-macro and still not solved for our 2000 user Confluence 5.9.7 !

Please create a new issue which clearly points out the problem and start to solve it!
Please don't solve issues by reason duplicate  and help customers to get their problems solved!**

Thanks for your support.

Best regards

Michael Kulas

Owen Sanico, Please could you reopen this as the issue is still present in 5.9.9.

Problem still there with 5.9.1 .....

We actually gave up on this, in fact we stopped using a lot of Atlassian products due to bugs that never seem to be fixed. I've seen many threads where they are reported to be fixed and we apply the upgrade / patch and find out its still broken. I'm tired of the broken promises.

As per Jon Jermiz's post, what's the status of this fix?

The issues is marked "closed" and the "Fix Versions" are 5.5.6 and 5.6. However, I'm running a 5.7 trial and inline macros are not working for me. For instance, I took the "inlinetest" attached to this bug and, after getting it to run, saw the same issue: the WYSIWYG editor still injects <p/> elements around the output of a BodyType=INLINE macro when said output is inside elements other than <p> (such as <h3> or <b>). Is this bug being tracked in a different issue? I did a bunch of checking around (not to mention WAY too much time trying to get it to work) and have not seen any info or status better than this closed bug report.

Hi jon.hermiz

Thanks for getting in touch. This issue will be made available in the next Confluence release. Upgrading to this once it's released is the best way to benefit from this fix.

Regards
Steve Haffenden
Confluence Bugmaster
Atlassian

Hello Atlassian Support,
Just a question from my end. How does this work now that the issue has been marked "Resolved"? Is there some sort of patch or upgrade we need to perform to get this fix?
Sorry for the newbie question we are fairly new to jira.

Thanks,
Jon

Hi jon.hermiz

Thanks for getting in touch again. As I mentioned in my previous comment this issue is currently being worked on and we hope to have this issue resolved in a coming release of Confluence. Unfortunately I am unable to give a firm date on exactly when this issue will be made available.

Regards
Steve Haffenden
Confluence Bugmaster
Atlassian