Re: [WICG/webcomponents] HTML Modules (#645)

> @ox-harris the thing that you do is really impressive and I admire that, but I have great doubts about the marketing promises that you make. You mention `native` a couple of times per paragraph per page, which may sound that this is definitely going to be implemented the way you suggest. But looking at the state of HTML and CSS modules, there are no proposals that reached somewhat mature stage, so your "guess" of how the things should work might turn into a disaster for people using your package, given that you mess a lot with HTML without using `data-*` attributes or `import` tag, which officially doesn't exist yet.

It's indeed an important feedback @GeorgeTailor . But somehow, we also have factored this into OOHTML; maybe it isn't very obvious. This page in the docs - https://webqit.io/tooling/oohtml/docs/resources/meta-tag - recommends using the OOHTML meta tag to customise attribute and element names to something like what you've wished.  So, the `<import>` element could read `<html-import>`, and the `id` attribute could read `data-id` - as we have shown in these examples: https://webqit.io/tooling/oohtml/docs/learn/examples. We've left this completely open as at now to encourage experimentation in the community. But OOHTML's default attribute and element names are reading without prefixes because it needs to first give a native-like experience.

We're hoping to see the different ways developers imagine a module system for HTML. And with an implementation that is completely bendable, we hope OOTHML can be a great foundation for that.

I am hoping I can put up a more formal proposal at the relevant for OOHTML. The goal is to get OOHTML on a standards track.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/645#issuecomment-898683685