Jeremy - what type of use cases have you tried? I've been able to built fully functional code pages that the user can interact with via a code page that I embed as an iframe on a URL. One example is a custom grid-edit to replace the native one so I can employ searchable dropdowns, auto-fill, grid form rules etc, all of these with no issue. Depending on the link you're using probably determines the 'view' versus 'edit' capability as opposed to the limitation of the iFrame itself.
Chase, admittedly they have not been full code pages, they're native reports I've embedded, either on forms or dashboards. I've seen the code pages examples where we can make that work. This specific use case was a report that I wanted to use on a dashboard, without the header row and the wasted space on the left margin. The response below:
When any save of a record is attempted, as Mike mentions in his response, we just get a spinning wheel & hung page.
I've seen that when using the newer dashboards - but the same problem doesn't exist on the older homepages I've found. I've had use cases where it was a custom codepage splash screen with hyperlinks to native forms - but on the new dashboards when you open that link that security from iFrame kicks in an it hangs. On the older home pages that same splash page doesn't have the same behavior and works just fine. Not sure if that helps at all but it came back to mind as you mentioned it.
Chayce,
We are talking about using a formula URL that embeds an iframe in a form for a specific record, not any home pages.
