Viewformatting | Setting commandBarProps "primary" and "position" breaks "hide" key

[Tanddant]

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

Declarative list formatting

Developer environment

Windows

What browser(s) / client(s) have you tested

• 💥 Internet Explorer
• 💥 Microsoft Edge
• 💥 Google Chrome
• 💥 FireFox
• 💥 Safari
• mobile (iOS/iPadOS)
• mobile (Android)
• not applicable
• other (enter in the "Additional environment details" area below)

Additional environment details

Edge Version 142.0.3595.76 (Official build) (64-bit)

Describe the bug / error

I have some pretty long view formatting, which hides "Every button" except for the "automate", and "Export" buttons in the UI, so this is what I end up with ... all the "Kopi af...." are Quick steps triggering Power Automate

The relevant formatting here is:

...
{
  "key": "automate",
  "hide": false,
  "text": "Opret",
  "iconName": "Add",
  "primary": true
},
...
{
  "key": "export",
  "hide": false
},
...

However, as you can see the "primary is not taking affect on the automate button" 🤷 - however assigning it a position solves that

...
{
  "key": "automate",
  "hide": false,
  "text": "Opret",
  "iconName": "Add",
  "primary": true,
  "position": 1
},
...
{
  "key": "export",
  "hide": false,
  "position": 2
},
...

But that introduces an interesting issue, under each of the drop down all of the otherwise hidden buttons now appear, without any other changes to the view formatting

Steps to reproduce

1. Create a list
2. Hide all the fields (Formatting.json)
3. See that export Power BI is visible
4. Remove position from the two relevant buttons
5. Observe that it's now there

Expected behavior

No matter the position of the "group" all the keys that I've requested to be hidden should remain hidden.

[Ashlesha-MSFT]

Hello @Tanddant,
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.
If you don’t receive a reply within two working days, please use this escalation form to escalate.

[Ashlesha-MSFT]

We were able to reproduce the issue on our side as well. We've confirmed that when the position property is added to commandBarProps commands (which is necessary to make the primary styling work correctly), it breaks the hide property functionality, causing hidden buttons to appear in dropdown menus.

We've logged this as a bug and our engineering team is currently investigating it. At this stage, it appears that the position property is interfering with the visibility logic for command bar items.

Thank you for reporting this issue!