File under “Tiny little HTML5 useful tip.”
TL;DR
Apply this habit to all buttons contained within a form. Buttons outside of forms are just
buttons, not form controls.
Continue reading “TIP: Set “type” attributes explicitly on <button> elements”
File under “Tiny little HTML5 useful tip.”
Apply this habit to all buttons contained within a form. Buttons outside of forms are just
buttons, not form controls.
Continue reading “TIP: Set “type” attributes explicitly on <button> elements”
In a react/redux application:
jsx
capture its state by setting its vDom state with { [name]: !this.state.checked }
in a switch
statement
unit tests are jest
snapshot diffs
in typescript
className="bootstrap"
or className={style.injection}
incompatible
Making simple things hard in the front end again.
Sometimes in UI, it requires more brain power to understand “15 hours ago” than “2018-01-10 7:35PM”
– https://twitter.com/ghiden/status/951179673072881665
Hidenari has a point. Sometimes our UI could use a bit more precision. We as developers could be a bit more formal. But how to strike the right balance here?
User interface components in general are built with an expected user behavior. We used the jQuery-UI datepicker, to save time, but in an unusual way, which cost us a lot of time discovering what we’d missed. We re-learned a key insight, namely, month and year are navigation, not selection controls.
Continue reading “Using only Month and Year in jQueryUI Datepickers”
[originally posted 2013-08-11]
I used to maintain this blog on github using Hexo, a Node.js module supporting markdown. I’ve switched over to wordpress online once I found it supported markdown (in the Settings section) so I wouldn’t have to go through all the rebuilding and deploying for such simple things as fixing a typo.