Sorry all. I forgot to notify that I figured it out. Our site shares the host with a couple others and they have added a client lib that hides the cq:tags fields for some business reason but did not code it so that it restricted this behavior to their site. I did not realize this until I set breakpo...

No. Because of version differences and other factors I haven't been able to resolve, I cannot open the dialog in my local instance and I am not cleared to change settings on the cloud services. I'm not sure minification would change anything other that provide the full name to variables. The actual ...

I don't know what a screenshot would do. It would only show that the field is not visible. It is a tag selector marked as allowing multiple selections. There is nothing in the dialog definition about showing or hiding fields based on a selection. When the dialog is rendered, the field's style attrib...

The company I am working with has been using commerce assets to create some content. In the scaffolding, they have a tag field that is used to get titles associated with an asset. When the dialog is rendered, this field is having the style="display: none;" attribute added to the field.   My question...

I do not see the same view as you have shown here for the folder properties. The policies tab is not shown in my new instance.

I understand that. I am checking FOLDER properties and the policies tab, where you select if the policies are inherited from the parent and if you are overriding them, which content fragments are allowed. 

I deleted the crx-quickstart folder and children. Restarted a new instance of AEM, stand alone, 6.5. The policies tab does not show to set which fragments is not displayed.

I could but I don't think it is caused by my code. It was working great in my previous instance and I don't have any custom overlays that should come into play.Checking properties on the We-Retail sample pages, the properties tab isn't there either.

The policy tab is not listed when I select the folder properties. I had this ability in the old instance on a VDI that crashed. Now I no longer see the properties tab to set which content fragment models are allowed.

Also, I had an old package with the content fragment definitions in it and there were policy nodes on the folders that specified which content fragments to allow. This doesn't seem to be working because the specified models are not shown when I try to create a new fragment.