The field set used by XML sitemap is sometimes shown collapsed, and sometimes not, depending on the page the field set is showed on.
It would be better if the field set would always be shown collapsed (or not collapsed).

Comments

Anonymous’s picture

Anonymous (not verified) commented
Priority: Normal » Minor
Issue tags: +User interface
Anonymous’s picture

Anonymous (not verified) commented
Status: Active » Postponed (maintainer needs more info)

I'm not seeing an issue with the visual affects. Can you provide a better explanation?

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

It's just a question of consistency; the code should use the same algorithm, to decide when the field set must be shown collapsed, or not.

Anonymous’s picture

Anonymous (not verified) commented

I don't see any inconsistency in the visual affects of the UI. Can you be more specific as to where there is inconsistency? Attach pictures if necessary.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

To say it in other words, the XML sitemap field is shown collapsed in some settings pages, but not collapsed in others; that is evident because the array containing the field definition sometimes includes '#collapsed' => TRUE, and sometimes not.

Anonymous’s picture

Anonymous (not verified) commented
Status: Postponed (maintainer needs more info) » Closed (won't fix)

I think I understand you. The visual presentation of each page has different scope with regard to collapsed or not. I don't see this as an issue.