As other posters note, a technical framework has never been required, but it is by far the easiest and most reliable way to ensure that the SCORM API remains accessible when moving between multiple pages.
If you do not use an iframe (supporting the API connection in the parent frame) and the user goes to the second page of your course, he will break the API connection and the course will no longer be able to communicate with the LMS.
The parent frame handles the LMS connection, while the child frame contains the contents of the course. A child frame (usually an iframe) can be maximized to fit the entire viewport, making the parent frame invisible and letting the child frame feel / behave like one HTML page.
RE: Adaptive layout, iframe is not an obstacle to creating flexible layouts. We do this all the time. Set the iframe to 100% width / height of the parent frame (overflow: hidden on the parent frame, overflow: automatically on the child frame so that the scroll bars appear as desired). For now, any responsive code you use in the iframe HTML file should work just as if it were NOT in the iframe. For example, if you use a media query for a stack of elements when the viewing area is small (for example, a tablet or phone), the multimedia query should work just fine. SCORM does not affect CSS, and the iframe has little effect on your CSS / design if the controls are good.
iframes are a large part of modern websites and are part of the HTML5 specification; iframe support is very reliable in all browsers and devices. Do not let this scare you.
source share