Expected behavior

In the Choo docs on Routing, in the section "Listening for Route Changes" implementing:

var html = require('choo/html')
var choo = require('choo')
var app = choo()

var app = choo()
app.use((state, emitter) => {            // 1.
  emitter.on('navigate', (route) => {    // 2.
    console.log(`Navigated to ${route}`) // 3.
  })
})

Should return a conso

We're not checking the validity of HTML for the demo page. This was noticed in #119.

It would be nice to have something added to check for HTML validity - either something that lints the HTML files, or something that makes the build task fail when HTML isn't valid.

I would be looking for recommendations on how to do this and would be open to any pull request that accomplishes the goal!

Pine crashed while editing a document. Not doing anything special, not inserting special characters or anything out of the ordinary I can think of..

crashlog.txt

Bug report - you can view the issue here: http://jsfiddle.net/bradhogan1983/sxwge12m/

When using the iframe option and clicking a link to open the modal, the modal opens instantly, but the iframe takes a second to load and while loading the modal container is just a small empty box. This happens on your demo as well as my local dev site. I'll also attach a screenshot of what I'm seeing on my

Let’s say you accidentally add find: ‘.’ or other invalid values. Now it would throw and not clean up properly.

Checking should happen somewhere around here

A try/catch should do the trick I think. In the catch block the cleaning up could happen (calling h.stop could not work, so manual

See #226

currently, while listening the only way to see if there are any bookmarks is if we check the bookmarks button. there should be some sort of a visual feedback on the seekbar
showing bookmarks.

In Safari the slide effect isn't very nice:

https://codepen.io/AndreKelling/pen/NoGQQr

Images just appear complete once they are fully slided in.

Safari: Version 12.0.2
Wallop: https://rawgit.com/peduarte/wallop/master/js/Wallop.min.js

Prerequisite for running on Debian:

$ apt install flex bison libelf-dev libssl-dev bc cpio libncurses5-dev xorriso wget make gawk gcc

Is kmod necessary?

When start clicking number buttons everything is ok, but if I start number with 0 this zero remains, while it should be overriten by the next non-zero number :)

some of this stuff is briefly mentioned in https://github.com/leeoniya/domvm#templates and easily overlooked, other stuff requires reading the code of the demos, and the rest is just plain missing. i think the list below represents a fairly thorough todo list for the docs.

does anyone have a good feel for how best to prioritize the items in terms of greatest impact?

cc @lawrence-dol @iamjohn

When a large text is displayed in siimple-steps-item-description, it breaks the steps item display:

But when the width of the siimple-steps-item is fixed:

Solut

Description what you'd like to happen:

Add single extra sentence to explain where show touches can be enabled into phone settings. An example for one brand will do.