Browser in Javascript

 


A Proof-of-Concept Browser written in Javascript for minimal Web 2.0 browsing experience. This DOES NOT depend on any browser engine like Blink, Gecko or Webkit. Use an existing HTML rendering engine like netsurf or roll-out your own.

This uses QuickJS-ng for JS runtime, Linkedom for DOM API and curl for network downloads. Font decoration uses Terminal ANSI escape codes.

Since linkedom is an npm module, it needs to be converted to ES6 module for use with quickjs. 

npm install linkedom
npx esbuild node_modules/linkedom/esm/index.js \
    --bundle \
    --format=esm \
    --outfile=linkedom.bundle.js \
    --platform=neutral
   

  

Code

 

Lessons Learnt

  1. std.urlGet() only supports stateless downloads. For form posts, header manipulation and cookie management, curl is used.
  2. curl can generate HTTP status code with -w option. 

 

References

  1. Edbrowse, a Command Line Editor Browser 
  2. Chawan: TUI web browser

 

Comments

Post a Comment

Popular posts from this blog

Plan 9 : The Infinity Notebook

Image
  Plan 9 is an Operating System (OS) from Bell Labs which is a successor to UNIX. It builds on the learnings from the previous Operating systems. Network computing and graphics is an integral part of the OS rather than an afterthought. It is modular and portable - it comes with a cross compiler . It is available, under MIT License , which anybody can use, learn and tweak. Features Everything is a file. Small Kernel:  Around 5MB size which can be built in under 2 minutes.  Singular Grid: All the computers running Plan 9 OS and connected together act like a singular grid. So there's no need for remote access solutions like VNC or RDP. This cool video shows a small glimpse of the possibilities. Process Isolation: Processes run within their own namespaces and are isolated from each other. So you can run rio (the window manager) within rio. Applications like Browsers don't need complicated sandboxing. And a crashing program is unlikely to bring down the OS. No DLL Hell : ...
Read more

Plan 9 Remote File Access from Emacs

Image
  Plan 9 Operating System uses 9p protocol for file access. This is an Elisp implementation of the protocol. Plan 9 ( 9front distribution) is running in QEMU with NAT networking. Local port 12564 is forwarded to 9fs service port 564 in the virtual machine.   Code https://gitlab.com/atamariya/emacs/-/blob/dev/lisp/net/plan9.el   Troubleshooting Plan 9 connection Ensure you are booting with  -a tcp!*!564  parameters. (Tip: You can add these to your /n/9fat/plan9.ini) Ensure you have configured the network interface   ip/ipconfig   Ensure you have an IP address  cat /net/ndb  Ensure you are running cpu+auth server  cpurc  (Optional) Start graphics mode  screenrc   (Optional) Start window manager  rio   (Optional) List open connections  netstat    (Optional) Monitor network traffic  snoopy   (Optional) Debug authentication  auth/debug  (Optional)...
Read more

Plan 9: Quick Boot with UEFI

Image
 UEFI ( Unified Extensible Firmware Interface) provides a quick way to set up a Plan 9 terminal  on modern hardware .  EFI System Partition (ESP) is a FAT32 partition. You should be able to modify it in most of the operating systems.     Run mk in \sys\src\boot\efi . aux/aout2efi converts an a.out file to an EFI executable. Copy over the files bootx64.efi, 9pc64, plan9.ini  (for x86_64 hardware) to \EFI\plan9\ directory in the ESP. If you want it be the default OS , you can create a symlink \EFI\boot to \EFI\plan9. Remember to include the full path to the kernel in plan9.ini. bootfile=\EFI\plan9\9pc64       When bootx64.efi fails to find the bootfile (e.g. kernel is missing, plan9.ini is missing or path is incorrect), you can provide the arguments at > prompt   followed by a boot command . You can use EFI shell or efibootmgr on Linux to modify the EFI entries that are displayed during boot.   Test in QEMU Before running ...
Read more