Web Apocrypha

In the previous lesson we have discussed how to create a platform independent Window class and expand it with platform specific (Linux) behaviors. If you missed it, you can read it here.

In the previous lesson we have discussed how to start with a minimal application based on Content API. If you missed it you can read it here.

In this lesson we show how to create a platform independent Window class. After that we will expand this with platform specific (Linux) behaviors.

Welcome to our first lesson on how to build a web browser!

We presume that you have already read the Introduction and have a Chromium repository set up as well. If you need more help setting up Chromium, here is what we did (when this guide was created the Chromium version was 47.0.2526.73).

We have decided to create a step-by-step guide to show you how to build your own browser based on the Content API. You might be familiar with our previous work on this topic. If not, you can start learning about the basics from here.

We have recently uploaded our first video about Sprocket. Check it out on YouTube!

If you don’t know Sprocket, here is a introduction about our Open Source experimental browser: http://browser.sed.hu/blog/20150714/sprocket-experimental-multiplatform-browser-based-content-api

We have recently created a summarized architecture overview about Chromium. Our purpose was that everyone who is interested in this topic could see how Chromium is built together and understand how it works. You can check it out here.

On behalf of the Sprocket team,

Edit Balint

Testing a web browser can be approached from several different angles. One can test performance, responsiveness, correctness of page layout or even the behavior of a web site in different user interactions.

This is a follow-up blogpost on our previous Sprocket intro. If you have not read it yet, you can check it out here.

Several months ago, a simple question was raised to us: How can one build a web browser? This was an interesting question not a trivial one to be answered in one sentence. So, at the University of Szeged we started to work on this issue to come up with a handy answer. This is how Sprocket was born. However, let us start from the beginning.

It's been a while since I last (and actually first) posted about Fuzzinator. Now I think that I have enough new experiences worth sharing.

More than a year ago, when I started fuzzing, I was mostly focusing on mutation-based fuzzer technologies since they were easy to build and pretty effective. Having a nice error-prone test suite (e.g. LayoutTests) was the warrant for fresh new bugs. At least for a while.