I'm confused about whether onFocus/onBlur events should bubble in preact, like they do in React.

In this example using preact 10.0.0-beta.1 they don't bubble https://codesandbox.io/embed/5wxk9zk7lx

...whereas in the Preact repl they do bubble https://preactjs.com/repl

export default () =>(
  <div onFocus={() => console.log("FOCUS")}>
    <div>
      Focus this input
   

It would be nice to have a babel macro that automatically runs the babel plugin to remove the runtime. That way, this project would work out of the box with "zero" config tools like create-react-app.

I'm thinking it could be something like:

import {html} from 'htm/preact/macro'

This is similar conceptually to CSS-IN-JS libraries providing a macro for their tools. See https://e

General Information

• [+ ] Improvement
• [+ ] Feature

Description

It may be useful: High-quality C++ HTML parser from cobalt.foo project. CMake port of it can be found at https://github.com/blockspacer/skia-opengl-emscripten/issues/5 and https://github.com/blockspacer/skia-opengl-emscripten/blob/master/src/cobalt/cobalt_dom.cmake#L32

Some possible use cases:

• Create some

This issue is to announce that I'm working on implementing a Miso submission for Realworld. This is aiming to be the most comprehensive Miso example with pages, routing, auth, css, etc.

The only thing it's not gonna cover, at least initially, is full-stack development with shared types. I'll think about adding that (maybe in a separate example?) when

React has unmountComponentAtNode, preact has render(null, element), etc.

How would that work in Superfine?

patch(null, null, container) // ?

// or

unmount(container) //?

What is it expected from this operation?

• There seems to be a bug when navigating to the catch_all route but not contributors, ex. localhost:7878/test. The current implementation panics using both rocket and actix as server.
• Rocket currently has 404 for unknown routes and this should be added to the actix example as well.

Hello! Thanks again for making such an amazing little framework. preact-compat has been a dream to work with, and I'm excited to integrate. I've just run into one little issue, that I hope isn't a blocker, because the performance gains are tremendous! 🔥

I'll add as much code as possible, if it's relevant, note that our application runs fine in the browser, where this code isn't executed.

So

using the for attribute (matching the inputEl id)

It'd be neat to have a benchmark to test our diffing needs — perf is a feature, and we should be able to catch regressions.

Given this would need to run in the browser, we'd probably need some tooling around this. I was thinking it'd be cool to run a headless Chrome instance through puppeteer, and use the [nanobench](https://github.com/mafintosh/nano

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