@alireza, yeah, I’ve tried that and the result is the same empty iframe.
If I change the iframe src to /med/study-images/ohif/index.html,
I see a black screen AND app-config.js plus the various css and js bundles get loaded.
But, I don’t see a call being made to /studies in the network panel.
This is my public folder structure:
public/
├── ohif/
│ ├── index.html
│ └── ...
I also see a bunch of messages in the console panel like
Registering old name UINotificationService
Registering old name DisplaySetService
New measurement mapping added to source 'Cornerstone3DTools@0.1'.
...
This tells me that the iframe is able to locate ohif, load the index.html file, and load the styles/scripts referenced in the <head> section.
The app is indeed running (scripts are downloaded and I can debug & hit breakpoints). But in this case, it wasn’t going to the root ‘/’ route on initial load. When I navigate to it (by posting a message from the parent app to the child iframe), I can see the StudyList and everything else.