4 ms·
Seamless iframes: The future, today
- quink 14y agoSo, I saw this and opened up Chrome's Inspector. It's a slideshow. Advance with space or →.
- andyfleming 14y agoYeah. At first I thought I was supposed to inspect what I was viewing.
- andyfleming 14y agoVery interesting. I hadn't seen the seamless iframes before, but the idea of css cascading through could save some load time and make them a bit more responsive and useful.
- thinkbohemian 14y agoI would <3 this so hard if it was a blog post + demo rather than slides. Good info, just hard to get at.
- irickt 14y agoThe last slide points to this repo with slide content and code. https://github.com/benvinegar/seamless-talk https://github.com/benvinegar/seamless-talk
- nakedgremlin 14y agoThis is really good stuff. Lots of practical hints and methods to get seamless iframes kosher. Kinda curious to see the 'hastily written demo' (slide 38)...
- emp_ 14y agoA massive issue with iframes is the browser back button, if you click 10 things inside the iframe and hit back in the browser it will start to navigate the iframe history, not the parent and I do not know any way possible to have a normal navigation inside the iframe without filling the browser history with its pages.
- deleted 14y ago[deleted]
- unconed 14y agoWhat i don't get is why they made this one feature bundling all the new behavior, as opposed to letting you decide for yourself if you want css inheritance, auto sizing, auto targets, etc