Table of Contents for
The Modern Web

Version ebook / Retour

Cover image for bash Cookbook, 2nd Edition The Modern Web by Peter Gasston Published by No Starch Press, 2013
  1. The Modern Web
  2. Cover
  3. The Modern Web
  4. Advance Praise for
  5. Praise for Peter Gasston’s
  6. Dedication
  7. About the Author
  8. About the Technical Reviewer
  9. Acknowledgments
  10. Introduction
  11. The Device Landscape
  12. The Multi-screen World
  13. Context: What We Don’t Know
  14. What You’ll Learn
  15. A. Further Reading
  16. 1. The Web Platform
  17. A Quick Note About Terminology
  18. Who You Are and What You Need to Know
  19. Getting Our Terms Straight
  20. The Real HTML5
  21. CSS3 and Beyond
  22. Browser Support
  23. Test and Test and Test Some More
  24. Summary
  25. B. Further Reading
  26. 2. Structure and Semantics
  27. New Elements in HTML5
  28. WAI-ARIA
  29. The Importance of Semantic Markup
  30. Microformats
  31. RDFa
  32. Microdata
  33. Data Attributes
  34. Web Components: The Future of Markup?
  35. Summary
  36. C. Further Reading
  37. 3. Device-Responsive CSS
  38. Media Queries
  39. Media Queries in JavaScript
  40. Adaptive vs. Responsive Web Design
  41. Viewport-Relative Length Units
  42. Responsive Design and Replaced Objects
  43. Summary
  44. D. Further Reading
  45. 4. New Approaches to CSS Layouts
  46. Multi-columns
  47. Flexbox
  48. Grid Layout
  49. The Further Future
  50. Summary
  51. E. Further Reading
  52. 5. Modern JavaScript
  53. New in JavaScript
  54. JavaScript Libraries
  55. Polyfills and Shims
  56. Testing and Debugging
  57. Summary
  58. F. Further Reading
  59. 6. Device Apis
  60. Geolocation
  61. Orientation
  62. Fullscreen
  63. Vibration
  64. Battery Status
  65. Network Information
  66. Camera and Microphone
  67. Web Storage
  68. Drag and Drop
  69. Interacting with Files
  70. Mozilla’s Firefox OS and WebAPIs
  71. PhoneGap and Native Wrappers
  72. Summary
  73. G. Further Reading
  74. 7. Images and Graphics
  75. Comparing Vectors and Bitmaps
  76. Scalable Vector Graphics
  77. The canvas Element
  78. When to Choose SVG or Canvas
  79. Summary
  80. H. Further Reading
  81. 8. New Forms
  82. New Input Types
  83. New Attributes
  84. Datalists
  85. On-Screen Controls and Widgets
  86. Displaying Information to the User
  87. Client-side Form Validation
  88. The Constraint Validation API
  89. Forms and CSS
  90. Summary
  91. I. Further Reading
  92. 9. Multimedia
  93. The Media Elements
  94. Media Fragments
  95. The Media API
  96. Media Events
  97. Advanced Media Interaction
  98. Summary
  99. J. Further Reading
  100. 10. Web Apps
  101. Web Apps
  102. Hybrid Apps
  103. TV Apps
  104. Webinos
  105. Application Cache
  106. Summary
  107. K. Further Reading
  108. 11. The Future
  109. Web Components
  110. The Future of CSS
  111. Summary
  112. L. Further Reading
  113. M. Browser Support as of March 2013
  114. The Browsers in Question
  115. Enabling Experimental Features
  116. Chapter 1: The Web Platform
  117. Chapter 2: Structure and Semantics
  118. Chapter 3: Device-Responsive CSS
  119. Chapter 4: New Approaches to CSS Layouts
  120. Chapter 5: Modern JavaScript
  121. Chapter 6: Device APIs
  122. Chapter 7: Images and Graphics
  123. Chapter 8: New Forms
  124. Chapter 9: Multimedia
  125. Chapter 10: Web Apps
  126. Chapter 11: The Future
  127. N. Further Reading
  128. Introduction
  129. Chapter 1: The Web Platform
  130. Chapter 2: Structure and Semantics
  131. Chapter 3: Device-Responsive CSS
  132. Chapter 4: New Approaches to CSS Layouts
  133. Chapter 5: Modern JavaScript
  134. Chapter 6: Device APIs
  135. Chapter 7: Images and Graphics
  136. Chapter 8: New Forms
  137. Chapter 9: Multimedia
  138. Chapter 10: Web Apps
  139. Chapter 11: The Future
  140. Index
  141. About the Author
  142. Copyright

Data Attributes

A further way that HTML5 extends the meaning that elements have is through the use of data attributes. These are user-defined attributes, the values of which are intended to provide information related to an element but without giving any extra semantic meaning to either machines or humans. Let me explain that in a little more detail.

Say you want to output a set of data, each item of which has two values—a name and a number (a unique database ID, for example). You want the name to be shown in the document, but you also want to make the number available for running scripts on. As it stands, no relevant attribute is available to store that information; you’d probably have to use a class:

<p class="id-123">Peter</p>

Data attributes were created for just this reason: associating data. They let you store that extra information without implying any extra meaning, as a class does. Each data attribute starts with the word data- and then a user-defined unique key; for our example, we could use this:

<p data-id="123">Peter</p>

The data attribute id is now associated with the value Peter. Although it gives no extra semantic meaning to the element, the attribute is available to provide context to other processes: perhaps information about this data is in an associated JSON file, so you can use JavaScript to look it up.

The Data Attributes API

So scripts can get at this data more easily, a simple DOM API is available that uses the dataset property. To get the value of a data attribute, use this property with the key of the attribute you’re querying:

var el = document.querySelector('p');
var id= el.dataset['id'];

Applied to this example markup, the returned result would be 123. You can also update attribute values with dataset:

el.dataset['id'] = 100;

Here’s an example that shows this at work:

var el = document.querySelector('p');
console.log('The ID is',el.dataset['id']);
el.dataset['id'] = 100;
console.log('Now the ID is',el.dataset['id']);

In this example, I perform three operations: first getting the id data, then setting it to 100, then getting it again, and each time logging the results into the console. The resulting output is shown in Figure 2-5.

Showing the results of data attribute manipulation with the API in the console
Figure 2-5. Showing the results of data attribute manipulation with the API in the console

jQuery and Data Attributes

If you use jQuery, interacting with data attributes is even easier (if you don’t know what jQuery is, I’ll explain it in Chapter 5; you can come back to this section after you’ve read it). Use the data() method for getting and setting data values:

var id= $(el).data('id');

This code is analogous to that shown in the previous section and would return the same value, 123.

One big advantage, however, is that, unlike dataset where all results are returned as a string, the data() method also parses the value of the attribute and converts it into the correct type; using the previous example, the type would be a number. But if you change the markup:

<p data-name="Peter">123</p>

And use the data() method again:

var name = $(el).data('name');

The value of the variable name is Peter, and its type is a string.

To see this in action, take a look at the example file data-attributes-jquery.html. In it, I’ve combined the two different data attributes in the same markup:

<p data-id="123" data-name="Peter">Gasston</p>

Using jQuery, I’ve logged each data attribute’s type into the console using JavaScript’s typeof operator:

var el = $('p');
console.log('ID:',typeof el.data('id'));
console.log('Name:',typeof el.data('name'));

The resulting output is shown in Figure 2-6.

Finding the type of the results using the jQuery data() method with data attributes
Figure 2-6. Finding the type of the results using the jQuery data() method with data attributes

Data Attributes in the Wild

Data attributes are so useful that some companies already take extensive advantage of them. Twitter was quick to adopt them, allowing them to be used as an option for adding a Tweet button to web pages. Certain parameters about the content are stored in a set of predefined attributes:

<a href="https://twitter.com/share" class="twitter-share-button" data-url="http://broken-links.com" data-via="stopsatgreen">Tweet</a>

By including a call to Twitter’s JavaScript elsewhere on the page, this element is replaced by a Tweet button using the supplied data. Many other social services, such as Facebook, Google+, and LinkedIn, use data attributes in the same way.