Ozone - patch 1

This release fixes attribute spread for global html attributes.
This closes the gap between what the runtime does and what the typechecker says.

This change is a breaking change, since the behavior of this code changes from:
<img width="42" />
to
<img width="42" onclick="trait" />

$source = <img width={42} onclick="trait" />;
$target = <img {...$source} />; // ???

If you relied on this hhvm bug, sorry this behavior was never intended.

If you previously wrote:

<img {...$source} onclick={$source->:onclick} />;

you may now remove this workaround.

Ozone

This release requires sgml-stream v0.3.0 (Ozone)
No further changes have been made.

Oxygen - patch 2

This patch changes out the backend codegen. This release should be identical to patch 1, since we've kept the same html definitions. You may continue to use Oxygen - patch 1 without ill effect.

This codegen change makes it easier for the codegen itself to pass review and be open sourced.

Oxygen - patch 1

Removes the sgml-stream-interfaces requirement. Changes sgml-stream requirement to ^0.2. This allows you to install this package directly. With dev-master you would have to depend on sgml-stream-interfaces and sgml-stream directly, or set a minimum-stability requirement of dev.

No code changes.

Oxygen

This is the first release of html-stream-non-namespaced.

This repository is completely codegenned, since we publish html-stream-namespaced alongside it. We have not changed the codegen at all before building the open source version of html-stream. I hope I can open source the codegen code itself within the coming weeks. It is nothing special, but it would allow you to change the html tags and add new ones.

If you have non-xhp code that is using invalid attributes on html tags, xhp does not accept them. If this is blocking you from migrating that codepath to xhp, you could add those attributes (temporarily) to the affected tags by editing the definition json files.

If you wanted to add methods to all sgml-stream elements in your system, you could write them in a trait. You could use that trait in your own UserElements, but you would need access to the codegen to inject them into the html tags. You can introduce xhp-lib methods you use in your code into your own version of sgml-stream this way. (You can't add mutating methods, since sgml-stream elements are immutable. See sgml-stream's docs for more information.)