In this trivial repository you will find another file, index.html. Your task is to make a set of sequential changes to the page using either the native JavaScript DOM-related functions or jQuery (recommnded, and described below). There are some other files, too: index.js (explained in a second), style.css (style info for the file, a bit more i nthere than is really needed), and atomic-function-practice.html (see the bottom of this file for more info).
index.html contains the following tags in <head>:
<script
src="https://code.jquery.com/jquery-3.3.1.min.js"
integrity="sha256-FgpCb/KJQlLNfOu91ta32o/NMZxltwRo8QtmkMRdAu8="
crossorigin="anonymous"></script>
<script src="./index.js"></script>The second script tag loads javascript from the file index.js in this directory (./ means "look for the file in the current directory"). That file contains an empty function definition, and an instruction to call that function after the page has finished loading:
function runOnLoad () {
}
document.addEventListener('DOMContentLoaded', runOnLoad, false);You can experiment by running individual commands in the browser window, and then add the command to the function in your version of index.js.
- Set the text-color of all h2 elements to
red(or use a more exciting shade) - Set the background-color of all
ulelements to "gold" - Set the text content of the
h1element to "DOM Practice for JavaScript" - Set the text content of the second li only to
random noise - Add a new
pelement to the end of the first article only - Set the HTML content of that new element to
I am a paragraph with <em>italics</em> and <strong>bold</strong>. - Finally, remove these instructions from the DOM
Once you start to understand jQuery, these operations are not so hard. Remember:
- select elements by calling jQuery with a CSS-selector-like string. For instance,
$('div>p.main')will find allpelements that are direct children of adivelement and havea class ofmain. - it is also possible to call jQuery using an HTML element object rather than a string. We'll do this below.
- invoking that function (
$('div>p.main')) creates a jQuery object which has many powerful methods which you can now call by appending.methodNameto the object. We mostly use the following methods in our homework:$().css(property, value)will set the given CSS property value for all matching elements$().text(newValue)will replace the existing text content of the element withnewValue$().html(newHTML)is very similar, but will parse the text string and create any new HTML nodes as required- it is possible to iterate over the elements returned in a jQuery objet using either array-like notation such as e.g.
$()[3]to retrieve the fourth matching element in the DOM, or the array-likeeach()method which will perform an action for each matching element, e.g. ($().each(function () {this.method(something)})). The latter method is cool but involves a callback function - when retrieving and acting on individual nodes from the jQuery object one really tricky aspect is that the nodes themselves are not jQuery objects but native HTML objects. They have methods, but they are not jQuery methods. If you want to use jQuery methods on them, you will have to wrap the result in another call to jQuery. So for instance, if you want to set a CSS value for the 5th matching element on a query you will do something like this (read carefully!):
$($('p')[4]).css('font-family', 'Dingbats').
| Task | jQuery | "Vanilla" JS |
|---|---|---|
| Get all matching elements | $('selector') |
document.querySelectorAll('selector') |
| Get first matching element | $('selector').first() |
document.querySelector('selector') |
| Change CSS prop | $('selector').css('property-name', 'value') |
document.querySelector('selector').style.property-name = 'value' |
const matches = document.querySelectorAll('selector') |
||
for (const m of matches) {m.style.property-name='value' |
||
| Change Text Value | $('selector').text('new text here') |
document.querySelector('selector').textContent = 'new text here' |
const matches = document.querySelectorAll('selector') |
||
for (const m of matches) {m.textContent ='new text here' |
||
| Set inner HTML | $('selector').html('<tag>valid HTML here</tag>') |
document.querySelector('selector').innerHTML = '<tag>valid HTML here</tag>' |
const matches = document.querySelectorAll('selector') |
||
for (const m of matches) {m.textContent ='<tag>valid HTML here</tag>' |
||
| Append to an element | $('selector').append('<tag>valid HTML here</tag>') |
document.querySelector('selector').innerHTML += '<tag>valid HTML here</tag>' |
| Remove a node | $('selector').remove() |
let el = document.querySelector('selector'); el.parentNode.removeChild(el); |
For more extensive comparisons, see you might not need jQuery, Cheat Sheet for moving, and perhaps easiest to read, this Github Gist.
OK, let's talk about atomic-function-practice.html. In this file you Have a chance to practice slowly building up HTML using very simple functions. As an example we use a simplified verison of the cards that were generated in Assignment zero.
The goal is to build a card like this for each student (but we won't add the linebreaks and indents!):
<card class="card">
<header>
<h1>matt
</h1>
</header>
<main>
<p>some guy
</p>
</main>
<footer>
<a href="https://digitalhistory.github.io/dh-website/">A Project of HIS393
</a>
</footer>
</card>So let's think about this:
- for each card, we need to produce an HTML tag (
card) with attributes and content - the content is a group of other tags, themselves also containing tags.
- so there is an underlying task -- create tags -- which we can use repeatedly to generate the parts, and then assemble the whole card
- once we know how to do that, we can iterate across the array of all cards (it's called
allEntriesand defined in a script tag at the top of the file) and create all the cards, then append them to the right element in the html structure - the starter code in the file is a starting point; some sections are commented out to avoid syntax errors as you start out.
- I've provided, in particular, the function
letsTag. However, the code is very hard to read! That's on purpose. You will have to write a similar function in the assignment and I want you to go through the process of figuring out how to do it. Even if you decode my function -- not worth your time!!! -- it is unnecessarily convoluted and uses methods and concepts you have not been taught. If I see those methods in your code you'll be asked to write it again from scratch. - Try it out!!