nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Issues of automatic page conversion to address before deprecation

Müller Miroslav

I open this discussion to address issues that need to be fixed before deprecation, since forced automatic conversion in the current state would lead to significantly degrading the usability of pages from the old editor.

We have identified the following:

Tables which have empty cells get all such cells filled with an additional newline when converted -> This leads to significant unnecessary vertical stretching of tables ⚠️. Manual removal of such individual newlines is labor intensive and time-wasting.
Header rows or columns get un-bolded -> Again, manual labor needed to bold the text again.
At some places, newlines between tables on a page get duplicated. -> Again this leads to unnecessary tall pages and they need to be deleted manually.

Our older projects have nearly all pages in the old editor and we need them for documentation. Any automatic conversion without manual fixing will lead to visual crippling of such pages and therefore degrade their usability⚠️.
We believe you do not want to lose your customers, so we hope you will address those issues before forcing the conversion. Thank you.

Comments

Joni Vanderheijden_i69ojy

Thanks @Müller Miroslav !

The first item was on our radar already, but hasn't been fixed yet. I've flagged the two other items to the team. Any additional information you have on 3. newlines between tables would be welcome.

Wherever possible we try to avoid manual effort on migration, we've already fixed some extra whitespace issues caused by the legacy editor.

Regards,

Joni

Trixie Johnson_uy8cr8

One of the biggest downfalls of the new editor is the wasted white space in left and right margins. Existing pages using legacy editor allow you to view much more information horizontally. At a minimum (& I agree with feedback already provided above!), please allow the full whitespace to be used before decommissioning our ability to continue using the legacy editor! A simple example is included below.

Whitespace Waste.jpg

Elle Ky_mfm1i3

Hi @Trixie Johnson

Thank you for sharing your feedback. We understand the concerns you shared and we're actively exploring solutions to address this issue. We have a relevant feature suggestion logged here: https://jira.atlassian.com/browse/CONFCLOUD-68780

We encourage you to "watch" the suggestion to receive updates on our progress.

Rebekka Heilmann _viadee_

[CLOUD-12503] Allow adding attachments from a page or space on Fabric editor - Create and track feature requests for Atlassian products.

Is this on the Roadmap? I am surprised that there haven't been any updates on Atlassian's side considering the significant number of upvotes. This should be fixed before enforced conversions.

Adding existing content to a page/making it visible got even more important with the deprecation of the Gallery macro and also hiding attachments further.

S_ Francoeur

Like Faivre Olivier in his comment here (https://jira.atlassian.com/browse/CONFCLOUD-78513?focusedId=3726574&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-3726574), we use Appfire's MultiExcerpt plugin for content reuse.
Among several other (broken) things, we discovered that it is impossible to nest a Content properties (aka Page properties) macro inside a Multiexcerpt macro in the new editor.

Please fix this before forcing conversion on us.

Thx

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

usability

conversion

issues

spacing