I’m wondering if this functionality has (seemingly) been avoided due to the expensive nature of doing all of the compares necessary in posts and meta, to ensure nothing is being wiped that’s still in use.
Perhaps it’s not as straightforward as it seems. Nonetheless, should still be called out as such if that’s the blocker.
I can see that the initial document being loaded in the admin panel shows the field I want disabled as actually disabled with full semantics:
<input type="text" id="acf-field_5e4bf7cb12333-field_5e4bf7f212334-row-0-field_5e4bf8e320b2f" name="acf[field_5e4bf7cb12333][field_5e4bf7f212334][row-0][field_5e4bf8e320b2f]" disabled="disabled"/>
However, it appears as though some JavaScript is removing this prop configuration after the document is fully loaded. I haven’t tracked down the offending JavaScript, yet.
If I had to guess, this goes for the others in this thread. This is also on a latest/greatest WordPress instance with minimal plugins loaded. I don’t have anything being enqueued in the admin panel that would be doing this, to my knowledge.
Edit
Ok, got it:
prop (jquery.js?ver=5.3.2:7623)
access (jquery.js?ver=5.3.2:3990)
prop (jquery.js?ver=5.3.2:7590)
d (acf-input.min.js?ver=5.8.7:formatted:659)
(anonymous) (acf-input.min.js?ver=5.8.7:formatted:668)
each (jquery.js?ver=5.3.2:368)
each (jquery.js?ver=5.3.2:157)
i.enable (acf-input.min.js?ver=5.8.7:formatted:666)
enable (acf-input.min.js?ver=5.8.7:formatted:1762)
showEnable (acf-input.min.js?ver=5.8.7:formatted:1774)
show (acf-input.min.js?ver=5.8.7:formatted:4069)
render (acf-input.min.js?ver=5.8.7:formatted:4066)
onNewField (acf-input.min.js?ver=5.8.7:formatted:4012)
u (acf-input.min.js?ver=5.8.7:formatted:987)
i (acf-input.min.js?ver=5.8.7:formatted:920)
i.doAction (acf-input.min.js?ver=5.8.7:formatted:399)
acf.newField (acf-input.min.js?ver=5.8.7:formatted:1815)
acf.getField (acf-input.min.js?ver=5.8.7:formatted:1886)
(anonymous) (acf-input.min.js?ver=5.8.7:formatted:1894)
each (jquery.js?ver=5.3.2:368)
each (jquery.js?ver=5.3.2:157)
acf.getFields (acf-input.min.js?ver=5.8.7:formatted:1893)
r (acf-input.min.js?ver=5.8.7:formatted:1917)
u (acf-input.min.js?ver=5.8.7:formatted:987)
i (acf-input.min.js?ver=5.8.7:formatted:920)
i.doAction (acf-input.min.js?ver=5.8.7:formatted:399)
(anonymous) (post.php?post=245&action=edit:3365)
This is the call-stack I was able to grab after setting a break-point on the element being modify, regarding its disabled property.
This is indeed happening after the document is loaded.
