https://github.com/thoughtscript/carbon_offsets

Carbon Credits and Offsetting
https://github.com/thoughtscript/carbon_offsets

cleantech greentech iframe javascript

Last synced: 3 months ago
JSON representation

Carbon Credits and Offsetting

• Host: GitHub
• URL: https://github.com/thoughtscript/carbon_offsets
• Owner: Thoughtscript
• Created: 2024-04-22T20:46:54.000Z (about 1 year ago)
• Default Branch: main
• Last Pushed: 2024-12-22T17:23:07.000Z (6 months ago)
• Last Synced: 2025-01-24T14:44:58.725Z (5 months ago)
• Topics: cleantech, greentech, iframe, javascript
• Language: CSS
• Homepage: https://thoughtscript.github.io/carbon_offsets/
• Size: 6.13 MB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# carbon_offsets

[![](https://img.shields.io/badge/mdn-iframe-orange.svg)](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe)

Just a fun page to track and host my carbon offsetting/credits.

> **Update:** I was invited to apply with this to a Startup Incubator recently (to be further developed into a Company/Product) but declined due to a lack of direct experience in that industry. (And, not out of interest! Greenwashing is a major challenge to help derisk the Decarbonization Industry.) 

Also, wanted to test the following:

1. I was unaware that `iframes` could be modified *after being rendered*. (*That it doesn't rerender or reload the page, for instance.*) Curious about how the `iframe` and `pdfviewer` interact on the page. I use them [here](https://www.thoughtscript.io/blog/000000000093) and [elsewhere](https://www.thoughtscript.io/papers/000000000006) but the *content is fixed* and *doesn't change once rendered*. 

1. Identifying and playing with some limits to testing `iframes`. For instance, using the Browser-based **Web Inspector** on Desktop will fail to correctly render the changing `iframe src`. However, when deployed to a host, the changes appear correctly. 

   

   i. This appears to be the case regardless of Browser/vendor.  

   ii. Not sure if that has to do with some shared PDF rendering tools/engine?  

   iii. (*I find PDF, Markdown, Parsing, and Text Rendering to be interesting topics - for instance: https://www.thoughtscript.io/ is a **Statically Generated Blog Framework***)

2. To better document my Net-Zero Carbon journey! I've been slowly amassing some certificates and want to host them and prove I'm going Net-Zero Carbon.

3. To better understand the differences in how browsers render injected PDF files. 

   

   i. For instance, **Microsoft Edge** `Version 124.0.2478.51 (Official build) (64-bit)` renders the corresponding **DOM Element** as:

    ```html

    


    


    

    ```


   ii. In **Brave** `1.65.114` however:

    ```html

    

        

    

    ```

   iii. Surprised that these differ so much but yet display the same test rendering issues.

 

## Tests

Per point **2.** above:

1. Desktop with Browser-based **Web Inspector** performs as expected - rendering each update correctly. The `iframe` appears as a `pdfviewer`:

    ![](test/desktop-browser-web-inspector-all-good.png)

1. Desktop with Browser-based **Web Inspector** doesn't perform as expected when emulating an `iPhone 14 Pro Max` - the clickable selections don't rerender correctly:

![](test/desktop-mobile-emulator-web-inspector-not-rendering.png)

1. However, the same deployment renders each change correctly on an actual `iPhone 14 Pro Max`:

    ![](test/actual-mobile-deploy-working.jpg)

> Interesting limitation of Browser Web Inspectors and Desktop emulation.