Not every feature of
Visualforce makes sense in a dynamic context, so some components aren’t
available dynamically.
- The following standard Visualforce components don’t have corresponding dynamic representations
in Apex:
- <apex:attribute>
- <apex:component>
- <apex:componentBody>
- <apex:composition>
- <apex:define>
- <apex:dynamicComponent>
- <apex:include>
- <apex:insert>
- <apex:param>
- <apex:variable>
- If a dynamic Visualforce component refers to a specific sObject field, and that field is
later deleted, the Apex code for that field reference will still compile, but the page will
fail when it is viewed. Also, you can create references to global
variables such as $Setup or $Label, and then delete the referenced
item, with similar results. Please verify such pages continue to work
as expected.
- Dynamic Visualforce pages and expressions check attribute types more strictly than static
pages.
- You can’t set “pass-through”
HTML attributes on dynamic components.