When starting a session using safaridriver, attempting to specify particular capabilities appears to not have an effect. The returned response from the webdriver server does not indicate that the specified capabilities were applied - it is the same every time. This behavior persists for all capabilities I've tried. The way I am providing capabilities seems consistent with the webdriver specification. Does safaridriver expect capabilities to be provided in another way, or is this a bug?
A couple examples:
Automatic profiling not applied
$ /usr/bin/safaridriver -p 8833
$ curl -X POST --data '{"capabilities":{"browserName":"Safari","safari:automaticProfiling":true}}' http://localhost:8833/session
{"value":{"sessionId":"96871DF1-C25D-4584-AE2C-1FF15C9CEFCB","capabilities":{"safari:platformVersion":"13.0","safari:automaticInspection":false,"webkit:WebRTC":{"DisableICECandidateFiltering":false,"DisableInsecureMediaCapture":false},"browserVersion":"16.1","strictFileInteractability":false,"browserName":"Safari","safari:useSimulator":false,"safari:automaticProfiling":false,"safari:platformBuildVersion":"22A380","acceptInsecureCerts":false,"setWindowRect":true,"platformName":"macOS","safari:diagnose":false}}}%
Page load strategy not applied
$ /usr/bin/safaridriver -p 8833
$ curl -X POST --data '{"capabilities":{"browserName":"Safari","pageLoadStrategy":"eager"}}' http://localhost:8833/session
{"value":{"sessionId":"56F6A934-3A93-4855-A5F1-E81A908AC6A4","capabilities":{"safari:platformVersion":"13.0","safari:automaticInspection":false,"webkit:WebRTC":{"DisableICECandidateFiltering":false,"DisableInsecureMediaCapture":false},"browserVersion":"16.1","strictFileInteractability":false,"browserName":"Safari","safari:useSimulator":false,"safari:automaticProfiling":false,"safari:platformBuildVersion":"22A380","acceptInsecureCerts":false,"setWindowRect":true,"platformName":"macOS","safari:diagnose":false}}}%