home.social

#iframes — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #iframes, aggregated by home.social.

  1. Google's AI Mode in Chrome is doing what iframes couldn't: Google AI Mode in Chrome embeds publishers inside its interface, overriding X-Frame-Options and CSP headers - the same protections it uses for its own sites. ppc.land/googles-ai-mode-in-ch #GoogleAI #Chrome #WebDevelopment #Iframes #XFrameOptions

  2. You know how you’re in the middle of a process and you refresh a web page and it loses state?

    So that sucks.

    With Kitten¹ – when using the new state-maintaining/class-based and event model-based component model – it’s easy to have flowing interfaces that animate between states, etc., that don’t lose state if you refresh the page (or open another tab).

    What you can’t do on the Web, however, is restore the state of any cross-origin iframes. (As you have no visibility into their contents to take a snapshot, etc.)

    This is something I ran into with the embedded Stripe component I’m using in Catalyst². Specifically, it has a success state that I want to restore so the interface, which uses selective disclosure and has animated to that step in the sign up process, doesn’t jump if you refresh it or look different if you open it in another tab.

    So what do you do if you’re obsessed with making things work as well as possible?

    Apparently, this:

    1. You go and manually save the Stripe iframe’s HTML and relevant CSS

    2. You notice that it is ~371KB in size and you sigh

    3. You use a combination of automated and manual methods to whittle that down to a 4.2KB HTML/CSS snapshot of the state.

    4. You make that into a Kitten component³ so you can set the bits that are dynamic⁴

    5. You make sure that it matches the original exactly using PixelSnap 2 guides⁵ (see screenshot; and yes, I told you I’m obsessed) :)

    6. Et voila!

    🤷‍♂️

    ¹ kitten.small-web.org
    ² catalyst.small-web.org
    ³ kitten.small-web.org/tutorials
    codeberg.org/project-catalyst/
    pixelsnap.com

    #Catalyst #SmallWeb #design #Stripe #iframes #stateRestoration #web #dev

  3. You know how you’re in the middle of a process and you refresh a web page and it loses state?

    So that sucks.

    With Kitten¹ – when using the new state-maintaining/class-based and event model-based component model – it’s easy to have flowing interfaces that animate between states, etc., that don’t lose state if you refresh the page (or open another tab).

    What you can’t do on the Web, however, is restore the state of any cross-origin iframes. (As you have no visibility into their contents to take a snapshot, etc.)

    This is something I ran into with the embedded Stripe component I’m using in Catalyst². Specifically, it has a success state that I want to restore so the interface, which uses selective disclosure and has animated to that step in the sign up process, doesn’t jump if you refresh it or look different if you open it in another tab.

    So what do you do if you’re obsessed with making things work as well as possible?

    Apparently, this:

    1. You go and manually save the Stripe iframe’s HTML and relevant CSS

    2. You notice that it is ~371KB in size and you sigh

    3. You use a combination of automated and manual methods to whittle that down to a 4.2KB HTML/CSS snapshot of the state.

    4. You make that into a Kitten component³ so you can set the bits that are dynamic⁴

    5. You make sure that it matches the original exactly using PixelSnap 2 guides⁵ (see screenshot; and yes, I told you I’m obsessed) :)

    6. Et voila!

    🤷‍♂️

    ¹ kitten.small-web.org
    ² catalyst.small-web.org
    ³ kitten.small-web.org/tutorials
    codeberg.org/project-catalyst/
    pixelsnap.com

    #Catalyst #SmallWeb #design #Stripe #iframes #stateRestoration #web #dev

  4. You know how you’re in the middle of a process and you refresh a web page and it loses state?

    So that sucks.

    With Kitten¹ – when using the new state-maintaining/class-based and event model-based component model – it’s easy to have flowing interfaces that animate between states, etc., that don’t lose state if you refresh the page (or open another tab).

    What you can’t do on the Web, however, is restore the state of any cross-origin iframes. (As you have no visibility into their contents to take a snapshot, etc.)

    This is something I ran into with the embedded Stripe component I’m using in Catalyst². Specifically, it has a success state that I want to restore so the interface, which uses selective disclosure and has animated to that step in the sign up process, doesn’t jump if you refresh it or look different if you open it in another tab.

    So what do you do if you’re obsessed with making things work as well as possible?

    Apparently, this:

    1. You go and manually save the Stripe iframe’s HTML and relevant CSS

    2. You notice that it is ~371KB in size and you sigh

    3. You use a combination of automated and manual methods to whittle that down to a 4.2KB HTML/CSS snapshot of the state.

    4. You make that into a Kitten component³ so you can set the bits that are dynamic⁴

    5. You make sure that it matches the original exactly using PixelSnap 2 guides⁵ (see screenshot; and yes, I told you I’m obsessed) :)

    6. Et voila!

    🤷‍♂️

    ¹ kitten.small-web.org
    ² catalyst.small-web.org
    ³ kitten.small-web.org/tutorials
    codeberg.org/project-catalyst/
    pixelsnap.com

    #Catalyst #SmallWeb #design #Stripe #iframes #stateRestoration #web #dev

  5. You know how you’re in the middle of a process and you refresh a web page and it loses state?

    So that sucks.

    With Kitten¹ – when using the new state-maintaining/class-based and event model-based component model – it’s easy to have flowing interfaces that animate between states, etc., that don’t lose state if you refresh the page (or open another tab).

    What you can’t do on the Web, however, is restore the state of any cross-origin iframes. (As you have no visibility into their contents to take a snapshot, etc.)

    This is something I ran into with the embedded Stripe component I’m using in Catalyst². Specifically, it has a success state that I want to restore so the interface, which uses selective disclosure and has animated to that step in the sign up process, doesn’t jump if you refresh it or look different if you open it in another tab.

    So what do you do if you’re obsessed with making things work as well as possible?

    Apparently, this:

    1. You go and manually save the Stripe iframe’s HTML and relevant CSS

    2. You notice that it is ~371KB in size and you sigh

    3. You use a combination of automated and manual methods to whittle that down to a 4.2KB HTML/CSS snapshot of the state.

    4. You make that into a Kitten component³ so you can set the bits that are dynamic⁴

    5. You make sure that it matches the original exactly using PixelSnap 2 guides⁵ (see screenshot; and yes, I told you I’m obsessed) :)

    6. Et voila!

    🤷‍♂️

    ¹ kitten.small-web.org
    ² catalyst.small-web.org
    ³ kitten.small-web.org/tutorials
    codeberg.org/project-catalyst/
    pixelsnap.com

    #Catalyst #SmallWeb #design #Stripe #iframes #stateRestoration #web #dev

  6. You know how you’re in the middle of a process and you refresh a web page and it loses state?

    So that sucks.

    With Kitten¹ – when using the new state-maintaining/class-based and event model-based component model – it’s easy to have flowing interfaces that animate between states, etc., that don’t lose state if you refresh the page (or open another tab).

    What you can’t do on the Web, however, is restore the state of any cross-origin iframes. (As you have no visibility into their contents to take a snapshot, etc.)

    This is something I ran into with the embedded Stripe component I’m using in Catalyst². Specifically, it has a success state that I want to restore so the interface, which uses selective disclosure and has animated to that step in the sign up process, doesn’t jump if you refresh it or look different if you open it in another tab.

    So what do you do if you’re obsessed with making things work as well as possible?

    Apparently, this:

    1. You go and manually save the Stripe iframe’s HTML and relevant CSS

    2. You notice that it is ~371KB in size and you sigh

    3. You use a combination of automated and manual methods to whittle that down to a 4.2KB HTML/CSS snapshot of the state.

    4. You make that into a Kitten component³ so you can set the bits that are dynamic⁴

    5. You make sure that it matches the original exactly using PixelSnap 2 guides⁵ (see screenshot; and yes, I told you I’m obsessed) :)

    6. Et voila!

    🤷‍♂️

    ¹ kitten.small-web.org
    ² catalyst.small-web.org
    ³ kitten.small-web.org/tutorials
    codeberg.org/project-catalyst/
    pixelsnap.com

    #Catalyst #SmallWeb #design #Stripe #iframes #stateRestoration #web #dev

  7. Hey #webDev folks!

    I have a #static site created with #Hugo.

    I would like to make it behave like a "one-page" web app, so that I can have a persistent audio player on the site that will not be interrupted by navigating the site.

    I'm open to using #iFrames, #ssi (server side includes), #ajax - whatever gets the job done.

    Any ideas welcome! Please BOOST for reach!

  8. Day 22 of the #30DayMapChallenge was "North is not always up" so I took this as an opportunity to play with #MapboxStudio, #html #iframes and positional locking

    Spinny interactive version can be accessed here:
    vikkiwalls.github.io/30-Day-Ma

  9. Day 22 of the #30DayMapChallenge was "North is not always up" so I took this as an opportunity to play with #MapboxStudio, #html #iframes and positional locking

    Spinny interactive version can be accessed here:
    vikkiwalls.github.io/30-Day-Ma

  10. Day 22 of the #30DayMapChallenge was "North is not always up" so I took this as an opportunity to play with #MapboxStudio, #html #iframes and positional locking

    Spinny interactive version can be accessed here:
    vikkiwalls.github.io/30-Day-Ma

  11. Day 22 of the #30DayMapChallenge was "North is not always up" so I took this as an opportunity to play with #MapboxStudio, #html #iframes and positional locking

    Spinny interactive version can be accessed here:
    vikkiwalls.github.io/30-Day-Ma

  12. Day 22 of the #30DayMapChallenge was "North is not always up" so I took this as an opportunity to play with #MapboxStudio, #html #iframes and positional locking

    Spinny interactive version can be accessed here:
    vikkiwalls.github.io/30-Day-Ma

  13. GPUs from all major suppliers are vulnerable to new pixel-stealing attack - Enlarge

    GPUs from all six of the major suppliers are vulnerab... - arstechnica.com/?p=1971213 #uncategorized #sidechannel #security #iframes #biz#gpus

  14. So I'm getting the weirdest error when I embed a #YouTube video in a #bootstrap modal on #Chrome (not Safari). Did YouTube change something or perhaps chrome? I know the postMessage function is a part of #iframes as I just recently learned how to use that. The error immediately stops when you open the modal and when you close the modal the error doesn't show up either.

  15. "iFrame Resizer" #JavaScript library enables the "automatic resizing of the height and width of both same and cross domain" #iframes to fit their contained content.

    davidjbradshaw.github.io/ifram

  16. 2 years without #uBlock - Here is what I think

    I use #AdGuard Home to collect and block domains.
    The cosmetic part is on Brave Browser end, which works, not as good as in #uBO but it is usable.
    #iframes blocking as well as URL re-writing is not yet implemented.

    Works well.

  17. #iFrames - It's just a completely broken technology. And yet I am forced to fix them at work nearly very two sprints.
    Why can't they just stop using/supporting it?

    #LegacyCode #Work #Programming #Web

  18. Gibt es eine Möglichkeit, #Mastodon #Hashtag #Feeds in #iFrames einzubetten so wie #timelineStreams mit #Mastofeed?

    Is there a way to embedd Mastodon Hashtag Feeds like timelines with Mastofeed?