Follow-up to FB23017010: Enhancement Request component for public Spaces API + compatibility bug timeline for Monitors key removal

UI Frameworks AppKit
CSJudd OP
Created 12h
Replies 1
Boosts 0
Views 49
Participants 2
This post is from the WWDC26 AppKit Q&A.

Received a response from Quinn @ DTS on FB23017010 regarding the com.apple.spaces plist restructure in Golden Gate. He confirmed no public Spaces API exists and suggested the plist change may be treated as a compatibility bug. He recommended filing an Enhancement Request for a proper API. Two follow-up questions for AppKit engineers: (1) Which Feedback component gets an ER for a public Spaces management API in front of the right team — AppKit, CoreOS, or Mission Control? (2) Is there any timeline visibility on the compatibility bug determination for the Monitors key removal?"

Replies  1
Boosts  0
Views  49
Participants  2
Frameworks Engineer OP
Apple
11h

AppKit is a good feedback component for a Spaces API request. Sorry, but I cannot provide any particular timeline for your compatibility issue, but it's with the right team.

That plist's structure and existence is considered an implementation detail and such details should not be relied upon.

Follow-up to FB23017010: Enhancement Request component for public Spaces API + compatibility bug timeline for Monitors key removal
First post date Last post date
 
 
Q