CSC/ECE 517 Fall 2015/oss M1501 GSN: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 1: | Line 1: | ||
==Report CSS errors to the devtools, both stored and live== | |||
CSS errors are reported to the Firefox developer tools in this project. | CSS errors are reported to the Firefox developer tools in this project. | ||
Revision as of 19:02, 31 October 2015
Report CSS errors to the devtools, both stored and live
CSS errors are reported to the Firefox developer tools in this project.
Introduction
Servo is an experimental web browser layout engine. It is developed by Mozilla and written in Rust.It provides an API for hosting the engine within other software.
Rust
Rust is a programming language developed by Mozilla. It is used to design concurrent and safe systems.
Environment Setup
Pre-requisites
On Debian-based Linuxes:
sudo apt-get install curl freeglut3-dev\ libfreetype6-dev libgl1-mesa-dri libglib2.0-dev xorg-dev \ gperf g++ cmake python-virtualenv python-pip \ libssl-dev libbz2-dev libosmesa6-dev libxmu6 libxmu-dev libglu1-mesa-dev
On Fedora:
sudo dnf install curl freeglut-devel libtool gcc-c++ libXi-devel \ freetype-devel mesa-libGL-devel glib2-devel libX11-devel libXrandr-devel gperf \ fontconfig-devel cabextract ttmkfdir python python-virtualenv python-pip expat-devel \ rpm-build openssl-devel cmake bzip2-devel libXcursor-devel libXmu-devel mesa-libOSMesa
Cloning servo
git clone https://github.com/servo/servo
Building Servo
cd servo ./mach build --dev ./mach run tests/html/about-mozilla.html
Project Description
We will be adding the capability of exposing CSS errors to Servo. We will be using Firefox remote developer tools to inspect and debug the code in Servo.
Program Flow
- Ensure that Servo can compile and run the given tests.
- Choose a website that is compatible with Servo and attach the remote developer tools to it.
Initial steps:
- Build Servo
- Attach remote developer tools
- Making initial changes and build Servo
- Generate css error messages
- Process error messages and retrieve cached messages
- Integrate and build again
Subsequent steps:
- Generate messages which communicate the errors to the script thread.
- Process the messages and provide support for caching them and sending them to the devtools server if it exists.
- Provide the functionality to retrieve the cached css error messages whenever requested.