edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: "Kevin Carhart" <kevin_carhart@fastmail.fm>
To: edbrowse-dev@edbrowse.org
Subject: Fwd: Re: question about FormData and Blob
Date: Thu, 25 Aug 2022 18:28:22 -0700	[thread overview]
Message-ID: <a8f84855-d4a8-466f-9e40-93f0cf18d518@www.fastmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2685 bytes --]

For the list.. we wrote to the author of FormData and he replied just to me, so I am sending it on.



----- Original message -----
From: "Jimmy Wärting" <jimmy@warting.se>
To: Kevin Carhart <kevin_carhart@fastmail.fm>
Subject: Re: question about FormData and Blob
Date: Thursday, August 25, 2022 4:59 AM

Hi kevin.

Yea maybe they are incompatible with each other. I'm a bit surprised that people still include Blob and FormData polyfills still to this day. All browsers, even NodeJS and Deno include a built-in Blob and FromData class natively nowadays.
I can play around with them and see if there is any issue when using them both together. but i'm a bit busy right now. I saw that edbrowse is actually running quickjs. and isn't actually running in an actual browser such as chrome, firefox or safari. 
I'm a bit impressed by what has been built and re-implemented in edbrowse to build a cli browser. It takes a lot to build a browser from the ground up and make everything spec compatible with new browser standard APIs poping in all the time now. 
I wouldn't even dare to take on such a huge job. I would just have built something with a headless browser and depend on the blink engine to do all the job and then use puppeteer to integrate with the browser programmatically through the command line. 

Den tors 25 aug. 2022 kl 11:44 skrev Kevin Carhart <kevin_carhart@fastmail.fm>:
> Hi Jimmy
> 
> I help develop a CLI browser project called edbrowse.. we implement the DOM and users can load websites in edbrowse.
> 
> And for a while now we have incorporated Eli's Blob.js.  Now we would like to do the same with your FormData.js.  But we are not sure if the two pieces of code will interoperate.  Is there a conflict between how yours and Eli's uses Blob?  Specifically, from yours we would use...
> 
> https://github.com/jimmywarting/FormData/blob/master/FormData.js
> 
> From Eli's we would use
> 
> https://github.com/eligrey/Blob.js/blob/master/Blob.js
> 
> Place them one after the next in a new js file and load it in at initialization-time.
> 
> From Blob.js we already have Blob, File, FileReader and URL as it says in the comment.
> We want to integrate this with your FormData implementation.  Is there some way we can "get the best of both worlds"?  It seems at the moment that when I include both without performing any extra steps, FormData is not recognized in the edbrowse console.
> 
> Whereas.. as a test of where we would like to get to, if I go to the firefox console and enter
> 
> FormData
> 
> It returns
> 
> function ()
> 
> thanks for the help
> Kevin
> 


-- 
MVH
Jimmy Wärting
jimmy.warting.se

[-- Attachment #2: Type: text/html, Size: 4473 bytes --]

                 reply	other threads:[~2022-08-26  1:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a8f84855-d4a8-466f-9e40-93f0cf18d518@www.fastmail.com \
    --to=kevin_carhart@fastmail.fm \
    --cc=edbrowse-dev@edbrowse.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).