Graphics And Rendering MCQs with Explanations

The code used to produce graphics on the client side is typically much smaller than the images themselves, creating a substantial bandwidth savings.

Web pages include images using the HTML img element.

One common use for image replacement is to implement image rollovers, in which an image changes when the mouse pointer moves over it.

When the amount of JavaScript code is so large that it effectively obscures the HTML, we call JavaScript as obtrusive.

The best suited option is document.image[] to find all img elements in the document.

The audio tag is used to include audio in the HTML document.

Both audio and video support a controls attribute.

The video tag does not contain a breadth property.

The parameter type of the Audio() constructor is any file type that contains audio to be played.

The canvas element has no appearance of its own but creates a drawing surface within the document and exposes a powerful drawing API to client-side JavaScript.

The canvas element is not supported by IE before IE9, but it can be reasonably well emulated in IE6, 7, and 8.

Most of the Canvas drawing API is defined not on the canvas element itself, but instead on a “drawing context” object obtained with the getContext() method of the canvas.

Call getContext() with the argument “2d” to obtain a CanvasRenderingContext2D object that you can use to draw two-dimensional graphics into the canvas. It is important to understand that the canvas element and its context object are two very different objects.

SVG describes complex shapes as a “path” of lines and curves that can be drawn or filled.

The beginPath() is used to begin a new path.

The closePath() method connects the last vertex back to the first, thereby creating a path.

There is no property called lineSize associated with the canvas object.

shadowBlur is used to check how crisp or fuzzy shadows are.

The saved coordinate system is restored by calling the method restore() associated with the canvas object.

A Rendering Engine is generally used for parsing and drawing all of the objects in the page.

The JavaScript Engine is generally used for interpreting the JavaScript.

The network layer is used to handle the HTTP requests.

The UI Layer takes care of the User Interface.

Webkit is what Chrome and Safari use, and is your target for most mobile web development since it is used as the layout or rendering engine for Android devices as well as mobile Safari for iOS devices and the Silk browser on Kindle Fires.

Gecko was first developed at Netscape, before the Mozilla Project spun out as its own entity, as the successor to the original Netscape rendering engine, back in 1997.

More tools than just browsers render HTML, including email clients and web components in other applications.

SpiderMonkey is the JavaScript engine made by Mozilla that is used in Firefox.

Opera uses Carakan, which was introduced in 2010.

Safari uses JavaScriptCore, sometimes called Nitro.

The interpreter can be shared with other properties, or embedded in other tools.

The total size of the page is important, not just because of the time it takes to download, but because the maximum size of an IP packet is 65535 octets for IPv4 and IPv6.

Once the TCP/IP connection has been established, the browser sends an HTTP GET request over the connection to the remote server. The remote server finds the resource and returns it in an HTTP Response, the status of which is 200 to indicate a good response.

The remote server finds the resource and returns it in an HTTP Response, the status of which is 200 to indicate a good response.

The Network Access layer controls the communication between the hardware in the network.

The Internet layer handles network addressing and routing, getting IP and MAC addresses.

The Transport layer is where our TCP (or UDP) communication takes place.

The Application layer handles the top-level communication that the client and servers use, like HTTP and SMTP for email clients.

This handshake consists of a Synchronize, Synchronize-Acknowledge, and Acknowledge message to be passed between the browser and the remote server. This handshake allows the client to attempt communication, the server to acknowledge and accept the attempt, and the client to acknowledge that the attempt has been accepted.

The four layers in the TCP/IP model are, in order from furthest to closest to the end user, the Network Access layer, the Internet layer, the Transport layer, and the Application layer.