Just thought of something else that I should have included two posts ago. The way I was able to determine the condition and settings and what those settings were was by review of the source code on the page, by the described system response, and review of the Dynamic Dropdown class files.
The results of the review were that the select option id for the displayed Dropdown did not include id[x] related information but instead select-attrcomb. Searching the code for attrcomb I found that usage to be in the single select related class files (dropdown and radio). The fact that the page was displaying a single attribute, using a dropdown, and had that information in the source code indicates that the dynamic dropdown settings had been altered from the original install settings of being active only for multiple attributes (2). Per the original instructions of dynamic dropdowns (still available for download with the files from that package used and applicably altered, the single dropdown option was considered to not be appropriate to use for single attribute product. Instead the suggestion was to use the multiple dropdown option for single attributes.
That said, there are a few things to consider. 1) potteryhouse/jeking had come up with an alternative option name type that provided javascript/html modifications to the dropdown to successfully display out-of-stock related product. 2) because of their work, no or little further development has been made by me to offer the same functionality using the DD code where there were other factors/features needed for standard operation. 3) DD has been around for a long time and other developers have likely made their own functional version(s) of the applicable files therefore I have tried to minimize any modification(s) of those files and where instruction is provided (such as this post) advised of the recommended settings or in the case of the default install pushed the functional settings to the database. 4) when developing a new or improved version of DD options added those options to the selection list instead of modifying the existing options (see 3 above).
Again, yes improved instruction (or any at all) is needed to be included with the package. There exists instruction at https://github.com/potteryhouse that is forked to my storage area but needs to be updated. There also is assistance offered throughout and as discussed in the forum thread for Stock by Attributes v4 for older ZC 1.3.5-1.3.9 (title is a little misleading, but it is the right place). The package is approaching maturity to distribute for use on an operational level so I would expect it to be postable in the "near" future once the instruction is updated.
Hope this helps someone that has come across this thread. Mind you as discussed in the first couple of posts the cause was not blatantly obvious but now that the majority of information requested in the posting tips has been addressed, the solution is clear. Thanks for your time! :)
ZC Installation/Maintenance Support <- Site
Contribution for contributions welcome...