Ted Patrick

Ok I think I see the problem... The browser parses everything and if it sees HTML elements that are not closed, it adds them before innerHTML is called. Case: ```html...

The problem with using a Custom Element that subclasses HTMLScriptElement is that the browser parses the internal contents of the element before realizing it is a ``. Also with mutation...

We can add attributes to py-script (async,worker,scope), but we cannot do that to the script tag. We can detect if the contents of py-script have parsing issues and warn the...

The HTML DOM ignores newlines. Here is an example showing the newlines are preserved in DOM writing but the browser is simply not rendering this whitespace. Example ```html Press me!...

The browser has an **excellent** event system. It is a very effective way to handle plugin-like systems and the api is very small, supports custom events, and you have likely...

Reply to @antocuni > how do we sync between the various phases? The different phases allow you to listen in different locations. Sometimes you want to capture as events go...

It feels like display() has overlap with the Element api. ```python Element("#foo").write("My Grand Title") #vs display( "My Grand Title", "#foo" ) ``` It also feels like the output target here...

The plan was to stamp the version into Pyscript.js [here](https://github.com/pyscript/pyscript/blob/main/pyscriptjs/src/runtime.ts#L19) This then goes into `` and is easily readable anywhere python or js. If this PR works from that source...

ESLINT ==> Strict TypeScript ==> Not Strict This is the source of the ESLint warnings. In strict, Typescript shows 200+ warnings. Once things settle a bit, we will address in...

I do not think anything is wrong with CICD or ESLint, this is highlighting that we lack TypeScript types in many areas. If we fix this root cause, everything improves.