Atle Wee Førre

@mgajda This package will not work with Elm 0.19 when "Native/Kernal whitelist" dissapears. This package is somewhat a wrapper of the firebase Javascript client, not a WEB API, so I...

Really like what I see happening now. Will the example also be migrated to 0.18? :)

Observation: If you add a package.json with browserslist in it the error seems to go away... ? ... "author": "", "license": "ISC", "dependencies": {...}, "browserslist": [ "last 2 Chrome versions",...

I faced the same issue today but found a workaround that works: https://github.com/elm/browser/issues/89#issuecomment-904493814

I faced the same issue today but found a workaround that works like I want: Add `Html.Events.preventDefaultOn "keydown" yourDecoder` to the outermost div To be able to pick up all...

**Update:** There was a slight problem with the proposed workaround. If an input on the page gets removed/destroyed focus is lost to document.body and the outermost div will not pick...

Thank you for fast response! the issue goes away if I remove this line from my elm-watch.json: ``` "postprocess": ["elm-watch-node", "postprocess.js"], ``` So seems related to uglify or the postprocess.js...

aha.. The error goes away if i replace my Input.text element with (text "test") Strange... ( I have no explicit centering going on any parents of that text input )

Here is a small example that crashes: **Main.elm** ``` elm module Main exposing (main) import Element import Element.Input as Input type Msg = NoOp main = Element.layout [] -- Converts...

It could be the other way around, API is correct and diagram is wrong? When you create a new project, a new "main" branch is also created with zero commits...