Skip to content

Instantly share code, notes, and snippets.

@MichaelDimmitt
Last active June 19, 2022 16:56
Show Gist options
  • Save MichaelDimmitt/cfecf19c0f280f304f971b6cb8b82529 to your computer and use it in GitHub Desktop.
Save MichaelDimmitt/cfecf19c0f280f304f971b6cb8b82529 to your computer and use it in GitHub Desktop.
investigate input date html element for chromium and waterfox codebases

Background

I wanted to understand why browsers using the newer <input type="time"/>

  1. had popups that I cannot debug in the browser.
  2. had popups that did not comply with the skip property.

Inspired by the following video from http203
I began my journey searching in the dark but initially heading in the right direction.

First lets start with other helpful links:

web platform tests: github
w3c for web standards: website, github, github/html repo

whatwg - Web Hypertext Application Technology Working Group
whatwg dom standard - github

the current official html web standard: whatwg html standard - github and the old w3c html web standard
^ why? after 2018 made a memorandum of understanding with whatwg to work jointly from the whatwg repos, so that is the location of the official standard for html at the moment.

w3c

you can see where all of the html element standards are defined here. link

whatwg

link to input element in the whatwg table of contents on their html working group page: link

Browsers

waterfox

code for input element in waterfox

chromium

  1. note: chromium has a code mirror on github but they do not have the standard pull request model
    1. it is hard to get the backstory / discussion around a feature. the way you would looking at a pr.
    2. to see the merged code the best strategy is to look at the commits in the branch.
    3. or get lucky and have a github issue point to a commit
    4. as happened in this case:
      1. issue
      2. commit
  2. Blink is the browser engine used by Chromium.
    1. It is located in src/third_party/blink. github link
    2. element in chromium

Conclusions:

  1. given that an issue related to spec of input element exist here: whatwg/html#2276
    1. I should search this repo's issues to see if the detail I want has been defined
    2. I should open an issue if it does not exist
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment