Power Platform Community Forum Thread Details

Interested in inconsistencies and issues others have faced with the Power Pages designer.
I regularly run into strange behavior based on how it wraps content to hook in its editor.
Pages that work ont he portal are visually bugged on editor or do not allow editing in inconsistent ways.

Please feel free to post your your own odd behaviors you have noticed so we can raise some awareness to these bugs.

Not comprehensive but just today 2 main issues I run into often:

Image and SGV's issues if any style/class is applied to them.
The designer seems to add it's own wrapping element and overrides some styles such as adding width/height 100% causing images taking up whole screens on not appearing at all.
- Generally I found I could fix this by keeping img/svg tags with no styles or classes and applying those to a wrapper element such as a span.
Editable snippets not allowing editing, isolated todays issue down to a snippet inside a <h1> tage doesn't work.
Though it works fine in the legacy Portal design studio.
Editable snippets of "type" = "text" in the designer are edited like they are HTML which very quickly creates a mess in snippets that are intended to be plain text. Ideally the editor would limit to plane text editing on snippets.

Still in preview but the web template as components "using {% manifest %}" is pretty hard to use and inconsistent in editor.

Issues such as:

1. Always requiring hitting the + button (used to add not edit) before the edit custom component option shows up (often causing issues such as the add component controls pulling focus).
Should be more like the snippets and appear when the custom control is focused.

2. Criteria for components being considered "Advanced Component" which renders them non configurable from designer.

First example: should not be advanced and should work and has a work around.
Having a page copy with the following is blocked.

{% unless page.adx_partialurl == "example"%}
 {% include 'sample component' input1:'Why would you not let me do this?' %}
{%endunless%}

But having a page copy such as:

{% unless page.adx_partialurl == "example"%}
 {%editable snippets 'TEST' type:html liquid:ture%}
{%endunless%}

And then the snippet test with the following works:

{% include 'sample component' input1:'wow it works' %}

This is essentially the same thing with even more depth to it and it functions.

The design studio when editing should target updating inside the include tag and disregard the wrapping code.

Second example: This is more problematic but the editor does not consider it an "Advanced Component"

When a include tag is taking in a variable or liquid object and not a static configured value.
I have tested this and the designer lets you edit it and it breaks the include and changes developer configured values.

2 examples of this:

Assigned variable gets wrapped in quotes changing behavior

{% include 'sample component' myInputValue:aVariable %}

Ends up as

{% include 'sample component' myInputValue:"aVariable" %}

Pulling data from a collection or reference like snippets breaks the include more then just passing a string wrapped value

{% include 'sample component' input:snippets["snippet"] %}

Ends up as

{% include 'sample component' input:"snippets["snippet"]"["snippet"] %}

I am sure there are many other gotchas and would love to here about any others people have encountered and if they have work arounds. The knowledge of these issues can help us write code compatable with designer, know when to tell colegues or clients when pages are not designer freindly and hopefully raise awareness to Mocrosoft so the tooling can improve and mature the product further.

Been working with Portals for going on 9 years the recent changes are exciting and the designer is young.
I am confident many of these issues will be addressed but in the mean time lets make the limitations more clear to save headaches troubleshooting individually.

Categories:

General topics