29 Matching Annotations
  1. Mar 2021
    1. Validating forms has notoriously been a painful development experience. Implementing client side validation in a user friendly, developer friendly, and accessible way is hard. Before HTML5 there was no means of implementing validation natively; therefore, developers have resorted to a variety of JavaScript based solutions.
  2. Feb 2021
  3. Nov 2020
    1. HTML contient un nombre arrêté d’éléments définis dans un standard, sans customisation possible

      Cette affirmation tend à ne plus être vraie: d’une part, les balises non spécifiées dans l’HTML5 «canonique» (ex. pour une balise que j’invente <bibliotheque></bibliotheque>, les navigateurs afficheront sans problème son contenu, à l’exception d’anciennes version de Microsoft Internet Explorer †); d’autre part on peut bel et bien créer des éléments avec la fonction JavaScript document.createElement('balise-speciale') (et cela est très fréquemment en usage aujourd’hui, particulièrement avec des frameworks comme Angular, React, Vue.js).

  4. Sep 2019
  5. Aug 2019
  6. Sep 2017
  7. May 2017
  8. Feb 2017
  9. Dec 2016
  10. Jul 2016
    1. The user agent should allow the user to manually trigger elements that have an activation behaviour, for instance using keyboard or voice input, or through mouse clicks. When the user triggers an element with a defined activation behaviour in a manner other than clicking it, the default action of the interaction event must be to run synthetic click activation steps on the element.
  11. Jan 2016
    1. working with forms somewhere in your HTML widget

      With LocalStorage, can open up some interesting possibilities.

    2. In 'Scroll view' mode, your widget might not display unless you have the widget set as 'anchored'.

      That might be the issue with the PhET simulation I added as a widget to an ePUB.

    1. Everything we do to make it harder to create a website or edit a web page, and harder to learn to code by viewing source, promotes that consumerist vision of the web. Pretending that one needs a team of professionals to put simple articles online will become a self-fulfilling prophecy.

      Humorous talk on website bloat by Maciej Cegłowski, creator of the Pinboard bookmarking service.

  12. Dec 2015
    1. The core set of functionality we've tried to capture in the HTML5 video compositor is the timing and synchronisation of the playback of videos and other media sources. The library allows you to cut together two separate videos near seamlessly, synchronise the playback of multiple videos in parallel and manage the pre-loading of videos in a just-in-time fashion.

      The BBC is open sourcing their experimental HTML5 Video Compositor. "This is an experimental JavaScript library for playing back dynamically modifiable edit decision lists (EDLs), and applying WebGL shader based effects."


    1. In Application Shell Architecture, the shell is served up by the Service Worker and then the content is delivered—often cached by the Service Worker—dynamically from its source through API requests.

      "Progressive Web Apps", an idea for better mobile performance using HTML5 Service Workers.

  13. Sep 2015
    1. cool-looking map

      Maps make a great case for SVG. There are some neat libraries and tools to play with SVG maps but, more importantly, maps make it easy to understand that an image can be semantic.

      A couple of weeks before Shepazu posted this, was playing with SVG maps of contemporary Africa’s political boundaries. (Especially those used on Wikipedia; including some which separate South Sudan.) Been teaching African Studies (on occasion) for years, and maps of the continent tend to become important quite quickly.

      Those SVG maps with which I started playing were pretty neat in several respects. The fact that they were vector drawings instead of bitmaps meant that they easily be resized without causing visual artifacts. More importantly, though, each country was drawn as a named outline, so it was possible to play with them as separate objects.

      One thing I was trying to do is create an animation which would show where each country fits in a region of the continent, using this United Nations geoscheme. Doing so, eventually noticed that Sudan and South Sudan had been classified as part of different regions, which is an interesting tidbit which could lead to useful classroom discussions.

      Haven’t retraced all the steps but, at some point, I’ve used a Public Domain map of Africa from Wikimedia Commons (itself based on another Public Domain map), and ended up creating a simple animated version using Tumult’s Hype commercial HTML5 editor.

      It’s flawed in many ways, but for someone with almost no background in this things, it’s a significant accomplishment.

      (Surely, the same could be done through SVG itself. Haven’t been able to learn how to do so.)

      Playing with those maps taught me quite a few things. For instance, the benefits of a well-tagged image. And some rudimentary notions of CSS-based animations. Or the limitations linked to selecting rectangular sections of an image (with a large overlap between Northern and Western Africa, for instance).

      Static Map of African Regions The experience also gave me all sorts of ideas. Such as annotating parts of a well-structured image. Or uses for Open Street Maps. Or ways to embed interactive content (including quizzes) in Open Textbooks.

      The key point, perhaps, and what led me to Schepers’s work (including this deeply insightful SVG-based presentation and interactive infographic about annotations) is that Open Standards can open up fascinating opportunities for learning.

      W3C Annotation Architecture proposal So nice to be working at a standards-happy learning technology non-profit!

  14. Aug 2015
  15. Jan 2014
    1. In all cases, one standard is clear: Each of these vendors is betting very heavily on HTML5-based applications as well as methods to make HTML5 compatibility the basis for their future. Whether made from Java or other language frameworks, HTML5 is the common thread that runs through each of these alternative mobile operating systems. Start with HTML5, and your applications’ portability is almost assured.

      Is there any other reasonable bet than HTML5?! Especially in the smartdevice realm where there is a rich set of HTML5-family features already enabled it makes less and less sense to make native applications except for special edge-cases. And any smartdevice competitors cannot possibly compete against iOS and Android on their own unique native app development format-- so HTML5 would seem the only reasonable place to focus development of new apps. Where Ubuntu succeeds is compatibility with an already well established Linux ecosystem.