HTML6 Concept
31–40 of 89 posts
Re: HTML6 Concept
#32This seems like a great idea but if it requires all that redundancy ( ) I have trouble seeing this used in practice.
Re: HTML6 Concept
#33Re: HTML6 Concept
#34You can already create your own custom HTML tags with the `document.registerElement()` API. And then use all the semantic elements you want. You can even add custom rendering and logic to then via the shadow DOM.
There's a lot of existing elements you can already use: http://customelements.io
Browser support is not 100% there yet, but http://polymer-project.org provides a polyfill that works on IE9+.
Re: HTML6 Concept
#35Terrible because not only it disrupts completely on how HTML matured, but also because there won't be any more HTML versions from now on; HTML is now a living versionless standard.
Sorry, my intention is not to just bash your idea. I personally disliked it because it resembles xml, something that I learned to hate. But that's me.
But please, don't call it HTML6.
Re: HTML6 Concept
#36Isn't html5 supposed to be a living standard [1], meaning continuous updates and no html:next spec? [1] https://wiki.whatwg.org/wiki/FAQ#What_does_.22Living_Standar...
Re: HTML6 Concept
#37
I do like the idea of not having generic 's everywhere. You can already do this with, for example, Angular. Basically, aside from the pre-defined elements (div, span, input, etc.) I want to just use whatever element I choose myself. I should then be able to style it how I want, and by default it can be, let's say, a borderless, 0 margin, 0 padding, transparent, block element. That way I can use add and style it how I want. Saves keystrokes. This gets me into trouble if later browsers decide to actually support with different semantics than I intended, but I am sure we could work around this somehow without resorting to namespacing.Lastly, I really would love to be able to define element behavior. I want to say that is a link, until you click on it, then it opens a calendar, and fires such and such events, etc. Basically, instead of adding a script tag to the base template that defines how $('.calendar') should work, I want to define it globally, a la Angular's directives, then have this happen for the entire site. If the browser allowed me to have finer grained control over user input (exact keystrokes, position of cursor, etc.), I could then re-create ! You might say "well, we already have that, the browser does it", but the beauty of doing it yourself is that you can define more complex rules for it than just "type in text". You could, for example, easily define the format of it without having to resort to ugly hacks (think a mm/dd/yyyy type input, or an insurance subscriber ID with a very specific format).
Re: HTML6 Concept
#38Re: HTML6 Concept
#39This makes zero mention of shadow DOM or web components, which strikes me as somewhat ignorant on the author’s part.
So, I wouldn't say ignorant but that the Web is catching up to this "spec's" vision.
[1] https://github.com/OscarGodson/HTML6/commit/7d58a98b30fe473d... [2] https://github.com/w3c/webcomponents/commit/c60060999073e181...
Re: HTML6 Concept
#40Is there anything preventing you from using non-native elements right now? I mean the weirdness aside... can't modern browsers just recognize current and process them as such? Why not just have HTML keywords be hands off for your app and then do your own thing with the element syntax? That's what Angularians are doing.