12 Matching Annotations
  1. Dec 2022
    1. stDeviation

      This should be stdDeviation. It tripped me up for a few minutes why it wasn’t working.

  2. Jan 2022
    1. A threshold of 1.0 means that when 100% of the target is visible within the element specified by the root option, the callback is invoked

      For example, if an element down the page is being scrolled on to the page, with 0 the observer would trigger as soon as the top edge of the element entered the area. With 1 the observer would trigger as soon as the bottom edge of the element entered the area.

    2. The first time the observer is initially asked to watch a target element.

      The provided callback needs to consider this.

    1. Some JS or a CSS animation causes a visual change, kicking off the rendering cycle.

      How about DOM changes too?

    1. more

      More than one could be pseudo elements, list markers, etc.

    2. zero

      I think this would be for stuff like <input type="hidden"> and other non-visual elements.

    3. In continuous media, the viewport is the viewing area of the browser window.

      Does paged media have a viewport?

  3. Dec 2021
    1. A couple of great use-cases for location state are: Telling the next page where the user came from and branching the UI. The most popular implementation here is showing a record in a modal if the user clicked on an item in a grid view, but if they show up to the URL directly, show the record in its own layout (pinterest, old instagram). Sending a partial record from a list to the next screen so it can render the partial data immediately and then fetching the rest of the data afterward.

      This is how Twitter will show a sign up modal + redirect you back when you click a link when you are signed out. (Open in a new tab to get past this.)

    1. That’s a pattern that repeats again and again: a solution is created in an imperative language and if it’s popular enough, it migrates to a declarative language over time. When a feature is available in a declarative language, not only is it easier to write, it’s also more robust.
    1. Tim Berners‐Lee assumed that most URLs would point to non‐HTML resources; word‐processing documents, spreadsheets, and all sorts of other computer files. HTML could then be used to create simple index pages that point to these files using links. Because HTML didn’t need to do very much, it had a limited vocabulary. That made it relatively easy to learn. To Tim Berners‐Lee’s surprise, people began to create fully‐fledged documents in HTML. Instead of creating content in other file formats and using HTML to link them up, people began writing content directly in HTML.

      index.html makes a lot of sense now.

  4. Oct 2021
  5. Aug 2021