View source for CSC/ECE 517 Spring 2016 M1603 Implement Common Parts of the CSSOM API

=='''Introduction'''==

Cascading Style Sheets ([https://en.wikipedia.org/wiki/Cascading_Style_Sheets CSS]) is a style sheet language used for describing the presentation of a document written in a markup language. Although most often used to set the visual style of web pages and user interfaces written in [https://en.wikipedia.org/wiki/HTML HTML] and [https://en.wikipedia.org/wiki/XHTML XHTML], the language can be applied to any [https://en.wikipedia.org/wiki/XML XML] document, including plain XML, [https://en.wikipedia.org/wiki/Scalable_Vector_Graphics SVG] and [https://en.wikipedia.org/wiki/XUL XUL], and is applicable to rendering in speech, or on other media. Along with HTML and [https://en.wikipedia.org/wiki/JavaScript JavaScript], CSS is a cornerstone technology used by most websites to create visually engaging webpages, user interfaces for web applications, and user interfaces for many mobile applications

==='''CSSOM'''===
CSSOM which is the CSS Object Model defines APIs (including generic parsing and serialization rules) for media queries, selectors, and CSS itself<ref>https://drafts.csswg.org/cssom/</ref>. The core features of the CSSOM are oriented towards providing basic capabilities to author-defined scripts to permit access to and manipulation of style related state information and processes. CSSOM aims at proving a way to access the CSS style classes and properties. One can even modify the CSS rules using this API. These changes can be targeted to affect individual elements or the whole webpage. <ref>https://github.com/servo/servo/wiki/CSSOM-student-project</ref>. CSSOM is actually a collection of all the CSS stylesheets found on a web page which is very similar to Document Object Model (DOM) but only stores collection of CSS instead of HTML. <ref>https://varvy.com/performance/cssom.html</ref>. CSSOM identifies which elements on your webpage require styling and modifies them. It is also used to optimize the speed at which webpages get loaded.
It is an integral part of the process that is used to display content on a webpage. The web browser first creates a DOM by examining the HTMLs, then creates a CSSOM by examining the CSS stylesheets. It then creates a render tree by comibining the DOM and the CSSOM and displays the webpage.<ref>https://varvy.com/performance/cssom.html</ref>.

==='''Rust'''===

We can organize different languages on a spectrum with control on one end and safety on the other. Languages like C and C++ fall on the end of the side of control, where as on the other side we have languages like Javascript, Ruby, Python, etc. What Rust does is stepping off this line. What it does is not a tradeoff between control and safety, but it provides you both the low level of control found in C and C++, and the high level of safety in JavaScript and Python. The three concepts that distinguish rust from other programming languages are: Ownership, Borrowing and lifetime. Ownership is how Rust achieves its largest goal, memory safety.<ref>https://en.wikipedia.org/wiki/Rust_(programming_language)</ref>

==='''Servo'''===

Servo is a project in [https://en.wikipedia.org/wiki/Mozilla Mozilla] research to write a parallel layout engine in Rust. It aims to achieve better parallelism, security, modularity and performance. Servo is built with Cargo, the rust package manager. It currently supports 64bit OSX, 64bit Linux, Android, and Gonk(Firefox OS).<ref>https://servo.org</ref>

=='''Project Description'''==

The project is to go through the following steps in a somewhat linear order:
*Compiling servo on a machine and making sure it runs on a specific url. Then emailing the mozilla mailing list to introduce the group.
*Creating a StyleSheet interface which represents an abstract, base style sheet. This creation requires a couple of steps :
**Adding a new IDL file (which contains specifications)
**Creating the Rust file which has implementations of the things specified in IDL.
**Listing the Rust file in mod.rs file.
*After that comes the creation of  a StyleSheetList interface. Which represents an ordered collection of CSS style sheets. And basically because it's another interface, again the .webidl and .rs files need to be implemented.
*Adding the attribute <code>stylesheets</code> to the <code>Document.webidl</code>. 
*In the three steps just mentioned some guidelines about implementation must be followed, like the return types of certain methods.
*Run the tests specified by the mozilla team.
*Finally updating the interfaces.html, and adding the new interface names.

The Subsequent steps are:
*making the <code>stylesheets</code> member of <code>Document</code> store the associated <code>Element</code> along with the actual implementation of <code>Stylesheet</code> and adding a member to <code>StyleSheet</code> for the associated element, and implement the <code>ownerNode</code> attribute of <code>StyleSheet</code> using this.
*create the CSSStyleSheet interface, containing an <code>Arc<Stylesheet></code> member. Add a method to <code>Document</code> that returns a new <code>CSSStyleSheet</code> instance for a particular index in the <code>stylesheets</code> member.
*creating the CSSRule interface which represents an abstract, base CSS Rule. It is done using the Webidl format.
*creating the CSSRuleList interface and implementing <code>CSSStyleSheet.cssRules</code> which is an array like object containing an ordered collection of CSS rules.
*implementing the <code>insertRule</code> and <code>deleteRule</code> methods of <code>CSSStyleSheet</code> to allow mutation of the contents of the vector in the <code>rules</code> member of the <code>Stylesheet</code>.
*creating the CSSStyleRule interface that extends the CSSRule interface and making <code>cssRules</code> return <code>CSSStyleRule</code> values for appropriate rules.

=='''Implementation'''==
==='''Initial Steps'''===
The following steps were followed to meet the project requirements as per this github page.
===='''Step 1'''====
We had to implement the StyleSheet interface for which we had to create two file: stylesheet.rs and StyleSheet.webidl and included stylesheet interface in the mod.rs file.
In the StyleSheet interface we avoided the three methods: ownerNode, parentStyleSheet and media as they could not be trivially implemented and the instructions were clear to avoid such methods.

===='''Step 2'''====
We had to implement StyleSheetList interface for which we had to create two file: stylesheetlist.rs and StyleSheetList.webidl and included stylesheetlist interface in the mod.rs file.
We used JS<Document> instead of [ArrayClass] as [ArrayClass] is not yet supported by Servo.
In the StyleSheetList interface we did not implement the getter as we do not have a list of stylesheets/scripts/dom.

===='''Step 3'''====
We had to implement a partial interface Document with an attribute as styleSheets. The declaration of the interface was done in Document.webidl and its implementation was done in document.rs file. The implementation returned a new instance of StyleSheetList referencing the current document.

===='''Class Diagram'''====


[[File:UMLinitial.png]]

==='''Subsequent Steps'''===

===='''Step 1'''====

We made changes in the <code>Document.rs</code> file to make the <code>stylesheets</code> member store the associated Element. We then implemented the ownerNode attribute in the StyleSheet inteface by making changes in the <code>StyleSheet.webidl</code> and <code>stylesheet.rs</code>. We declared <code>ownerNode</code> attribute in the .webidl and implemented it in the .rs file.

===='''Step 2'''====

We made a new interface named as <code>CSSStyleSheet</code>. In the <code>Document.rs</code> file, we created a method to return the <code>CSSStyleSheet</code> from the <code>stylesheets</code> member of the Document by giving a particular index as the input.

===='''Step 3'''====

As the next step, we created the <code>CSSRule</code> interface which has attributes like <code>type</code>, <code>cssText</code>, <code>parentRule</code> and <code>parentStyleSheet</code>. This interface has several constants like <code>STYLE_RULE</code>, <code>CHARSET_RULE</code> , <code>IMPORT_RULE, MEDIA_RULE</code>, <code>FONT_FACE_RULE</code>, <code>PAGE_RULE, MARGIN_RULE</code> and <code>NAMESPACE_RULE</code>.
This required us to create two files: <code>CSSRule.webidl</code> and <code>cssrule.rs</code>

===='''Step 4'''====

We created <code>CSSRuleList</code> interface by creating 2 files: <code>CSSRuleList.webidl</code> and <code>CSSRulelist.rs</code>. This interface has one attribute, length and a getter which returns the <code>CSSRule</code> at a particular index. We also implemented <code>CSSStyleSheet.cssRules</code>

===='''Step 5'''====

We made <code>rules</code> member of the <code>StyleSheet</code> type which contains a RefCell and implemented the <code>insertRule</code> and <code>deleteRule</code> methods of <code>CSSStyleSheet</code>.

===='''Step 6'''====

We created a new interface <code>CSSStyleRule</code> , by making 2 files: <code>CSSStyleRule.webidl<code> and <code>CSSStyleRule.rs</code>. The interface contains two attributes, namely, <code>selectorText</code> and <code>CSSStyleDeclaration</code> style. The <code>cssRules</code> was implemented to return <code>CSSStyleRule</code> values for appropriate rules.

===='''Class Diagram'''====

[[File:UMLsubs.png]]

=='''Design Principles'''==
In this mozilla project, we are asked to strictly follow the existing design patterns and coding conventions. The main aim of this project is to add and modify interfaces. Interfaces allow developers to follow a clean design principle wherein they do not have to program to classes. It is too easy to add a dependency on a class. In order to avoid that kind of dependency on the implementation i.e. classes, developers can program to interfaces. This type of design pattern is an architectural pattern and makes the code more modular and object oriented. Programming to an interface has a flavor of DRY principle because even if the underlying implementation changes, the handle to the implementation is an interface and that does not change. In this way, our mozilla project becomes more modular and object oriented. Servo has a utility of tests that checks the coding standards followed by Mozilla on this project. We will execute the following utility tests command.
<code>./mach test-tidy</code> Any issues encountered by executing this test can be flagged before generating the pull request. This ensures that the developers follow the coding standards.

=='''Testing'''==
Following are the steps to run all the tests:

# Install the pre-requisites required for servo as mentioned here
# Run the following commands

    cd
    git clone https://github.com/mohammed-alfatih/servo.git
    cd servo
    ./mach build --release
'''Note''': It may take around 30 mins to build
    ./mach test-wpt /tests/wpt/html/dom/interfaces.html
You will see that all tests pass as expected.

'''Note''': There were no predefined test cases mentioned for our project. So now you will see 0 testcases. As far as we know there is no way to test this from UI.

=='''Conclusion'''==
We have implemented the most commonly-used portions of the CSSOM API specification to increase Servo's compatibility with existing webpages <ref>https://github.com/servo/servo/wiki/CSSOM-student-project</ref>. We have created two interfaces, StyleSheet and StyleSheetList in our initial steps and as a part of our subsequent steps, we added four new interfaces: CSSStyleSheet, CSSRule, CSSRuleList and the CSSStyleRule interface. We have implemented only the obvious methods for these interfaces so that more advanced work can be done to make this CSSOM API fully functional keeping our work as the basis.

=='''References'''==
<references/>