The HAX editor learns about how to work with web components and is opt-in. Web components built to work with HAX should work with the web and not care about HAX aside from supplying a static get haxProperties() method which returns valid HAXSchema.
See a web component authored with the HAX editor, run in a stand alone codepen!
In rare situations blocks need to care about HAX such as:
Regardless of these situations, the block still must work without hax on the system. A guiding design principle of HAX and it's ubiquitous nature, is that content produced with the HAX editing system, must work without HAX being present.
The only exception to this would be blocks that are intentionally engineered to be in the context of a HAX site. Examples include:
Any block that relies on a third party service must work with or without HAX being present as a core principle of the development of the system.
The user asks to put a video on this page.
The result is that the Configure Block panel shows the settings from the HaxSchema read in.
This tag only shows up in the Merlin results because of it being listed in our appStore. Even if an element is listed there, HAX doesn't nessecarily know how to edit it, just that it's allowed to place it on the page and respond to it.
When clicking the video / it becoming the activeElement on the page, HAX will look for a haxProperties() method. video-player has one as defined here.
The result of these settings is highly semantic HTML code