CSC/ECE 517 Fall 2016/M1652 Implement ImageMap Support Servo - Revision history

Sspatil4: /* Image Maps */

2016-12-03T00:40:11Z

Image Maps

← Older revision		Revision as of 00:40, 3 December 2016
Line 15:		Line 15:

	===Image Maps===		===Image Maps===
	"In HTML and XHTML, an [https://en.wikipedia.org/wiki/Image_map Image map] is a list of coordinates relating to a specific image, created in order to hyperlink areas of the image to different destinations (as opposed to a normal image link, in which the entire area of the image links to a single destination). Servo currently doesn't support Image maps at the moment.		In HTML and XHTML, an [https://en.wikipedia.org/wiki/Image_map Image map] is a list of coordinates relating to a specific image, created in order to hyperlink areas of the image to different destinations (as opposed to a normal image link, in which the entire area of the image links to a single destination). Servo currently doesn't support Image maps at the moment.

	==Scope==		==Scope==

Sspatil4 at 03:10, 10 November 2016

2016-11-10T03:10:54Z

← Older revision		Revision as of 03:10, 10 November 2016
Line 87:		Line 87:

	The above command will download and compile the dependencies and the test cases. You will see that all tests pass as expected (Testcases are prefixed by HTMLAreaElement)		The above command will download and compile the dependencies and the test cases. You will see that all tests pass as expected (Testcases are prefixed by HTMLAreaElement)

			The unit tests and test-tidy results can be seen in this [https://github.com/servo/servo/pull/13972 pull request].

	=== Testing From UI ===		=== Testing From UI ===
Line 92:		Line 94:
	At this stage, the project cannot be tested from the UI since the complete code has not been developed for image map support. However a check can be done as a test page is run successfully on servo after performing the build as mentioned above.		At this stage, the project cannot be tested from the UI since the complete code has not been developed for image map support. However a check can be done as a test page is run successfully on servo after performing the build as mentioned above.

	Run the following command after the project is ~~build~~:		Run the following command after the project is built:

	<code>		<code>
Line 99:		Line 101:

	==Pull Request==		==Pull Request==
	Here is our [https://github.com/servo/servo/pull/13972 pull request]. In the ~~link you can see all~~ code snippets ~~changed due to implementing the above steps, as well as~~ integration test progression ~~information~~.		Here is our [https://github.com/servo/servo/pull/13972 pull request]. The link shows the code snippets that have been modified along with integration test progression.

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

Sspatil4 at 05:32, 29 October 2016

2016-10-29T05:32:29Z

← Older revision		Revision as of 05:32, 29 October 2016
Line 99:		Line 99:

	==Pull Request==		==Pull Request==
	Here is our [https://github.com/servo/servo/pull/~~13971~~ pull request]. In the link you can see all code snippets changed due to implementing the above steps, as well as integration test progression information.		Here is our [https://github.com/servo/servo/pull/13972 pull request]. In the link you can see all code snippets changed due to implementing the above steps, as well as integration test progression information.

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

Sspatil4: /* Pull Request */

2016-10-29T04:02:50Z

Pull Request

← Older revision		Revision as of 04:02, 29 October 2016
Line 99:		Line 99:

	==Pull Request==		==Pull Request==
	Here is our [https://github.com/servo/servo/pull/~~8182~~ pull request]. In the link you can see all code snippets changed due to implementing the above steps, as well as integration test progression information.		Here is our [https://github.com/servo/servo/pull/13971 pull request]. In the link you can see all code snippets changed due to implementing the above steps, as well as integration test progression information.

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

Sspatil4: /* Step 2 */

2016-10-29T04:01:08Z

Step 2

← Older revision		Revision as of 04:01, 29 October 2016
Line 46:		Line 46:
	===Step 2===		===Step 2===

	Constructors were implemented for each variant that accept a string argument, [[https://html.spec.whatwg.org/multipage/infrastructure.html#rules-for-parsing-a-list-of-floating-point-numbers parse them into appropriate coordinates]], and return an appropriate Area instance. Different combinations of coordinates were analysed to specifically assess objects based on the input string.		Constructors were implemented for each variant that accept a string argument, [https://html.spec.whatwg.org/multipage/infrastructure.html#rules-for-parsing-a-list-of-floating-point-numbers parse them into appropriate coordinates], and return an appropriate Area instance. Different combinations of coordinates were analysed to specifically assess objects based on the input string.

	[[File:Servo_002.png]]<br />		[[File:Servo_002.png]]<br />

Sspatil4: /* Step 2 */

2016-10-29T04:00:54Z

Step 2

← Older revision		Revision as of 04:00, 29 October 2016
Line 46:		Line 46:
	===Step 2===		===Step 2===

	Constructors were implemented for each variant that accept a string argument, parse them into appropriate coordinates, and return an appropriate Area instance. Different combinations of coordinates were analysed to specifically assess objects based on the input string.		Constructors were implemented for each variant that accept a string argument, [[https://html.spec.whatwg.org/multipage/infrastructure.html#rules-for-parsing-a-list-of-floating-point-numbers parse them into appropriate coordinates]], and return an appropriate Area instance. Different combinations of coordinates were analysed to specifically assess objects based on the input string.

	[[File:Servo_002.png]]<br />		[[File:Servo_002.png]]<br />

Sspatil4: /* Testing */

2016-10-29T02:46:25Z

Testing

← Older revision		Revision as of 02:46, 29 October 2016
Line 67:		Line 67:

	# Install the pre-requisites required for servo as mentioned [https://github.com/servo/servo/blob/master/README.md here]		# Install the pre-requisites required for servo as mentioned [https://github.com/servo/servo/blob/master/README.md here]
	# Run the following commands		# Run the following commands to clone the repository and run the tests

	~~<code>~~
	cd
	~~</code>~~

	<code>		<code>
Line 82:		Line 78:

	<code>		<code>
	git checkout ~~-b test origin/overrideMimeType~~		git checkout master
	~~</code>~~

	~~To run the mach build~~
	~~<code>~~
	~~./mach build --release~~
	</code>		</code>

Line 95:		Line 86:
	</code>		</code>

	You will see that all tests pass as expected.		The above command will download and compile the dependencies and the test cases. You will see that all tests pass as expected (Testcases are prefixed by HTMLAreaElement)

	=== Testing From UI ===		=== Testing From UI ===
Line 106:		Line 97:
	./mach run tests/html/about-mozilla.html		./mach run tests/html/about-mozilla.html
	</code>		</code>

	==Pull Request==		==Pull Request==
	Here is our [https://github.com/servo/servo/pull/8182 pull request]. In the link you can see all code snippets changed due to implementing the above steps, as well as integration test progression information.		Here is our [https://github.com/servo/servo/pull/8182 pull request]. In the link you can see all code snippets changed due to implementing the above steps, as well as integration test progression information.

Sspatil4: /* Step 2 */

2016-10-29T02:26:27Z

Step 2

← Older revision		Revision as of 02:26, 29 October 2016
Line 48:		Line 48:
	Constructors were implemented for each variant that accept a string argument, parse them into appropriate coordinates, and return an appropriate Area instance. Different combinations of coordinates were analysed to specifically assess objects based on the input string.		Constructors were implemented for each variant that accept a string argument, parse them into appropriate coordinates, and return an appropriate Area instance. Different combinations of coordinates were analysed to specifically assess objects based on the input string.

	[[File:Servo_002.png]]		[[File:Servo_002.png]]<br />
	[[File:Servo_004.png]]<br />		[[File:Servo_004.png]]<br />
	[[File:Servo_005.png]]		[[File:Servo_005.png]]<br />

	===Step 3===		===Step 3===

Sspatil4: /* Design Pattern */

2016-10-29T02:24:53Z

Design Pattern

← Older revision		Revision as of 02:24, 29 October 2016
Line 32:		Line 32:
	==Design Pattern==		==Design Pattern==

	Design patterns are not applicable as our task involved ~~just~~ implementing a ~~method~~.		Design patterns are not applicable as our task involved implementing methods in a predefined object, namely HTMLAreaElement.

	==Implementation==		==Implementation==

Sspatil4 at 22:14, 28 October 2016

2016-10-28T22:14:28Z

← Older revision		Revision as of 22:14, 28 October 2016
Line 1:		Line 1:
	<font size="5">~~M1504~~: Implement HTML Image Map support</font><br>		<font size="5">M1652: Implement HTML Image Map support for Servo</font><br />
	[https://html.spec.whatwg.org/multipage/embedded-content.html#image-map] Image maps are an HTML technology that allows treating arbitrary areas in an image as separate hyperlinks. The goal of this project is to implement this missing feature on [https://en.wikipedia.org/wiki/Servo_(layout_engine) Servo].<ref>https://github.com/servo/servo/wiki/Image-maps-project</ref>		[https://html.spec.whatwg.org/multipage/embedded-content.html#image-map] Image maps are an HTML technology that allows treating arbitrary areas in an image as separate hyperlinks. The goal of this project is to implement this missing feature on [https://en.wikipedia.org/wiki/Servo_(layout_engine) Servo].<ref>https://github.com/servo/servo/wiki/Image-maps-project</ref>