71–78 of 78 posts
Thanks to the people behind HTML5 for kicking off the innovation.
Thanks to the team that put this together at Mozilla. I went to the demo page and things just worked.
Calendar looks broken in FF and Chrome here. All I see is: 21 21 21 21 21 21 21 21 21 21 21 According to Browsershots it looks like this on many browsers: http://browsershots.org/http://mozilla.github.io/brick/compo... Same with the datepicker. Some other stuff also looks broken. I would much prefer one piece of javascript per component. So if I liked one, I could use it and improve it. Im not so much inclined to use…
Each component is isolated in just the way you describe, the only requirement is the base X-Tag Web Component library.
The first example (flip widget) already does exactly nothing on Android.
Counterpoint: it works perfectly on my Android device (using the standard awesomely-named "Internet" browser).
This is cool and certainly useful but I have concerns. Forgetting for a moment that this is a shim and imagining that all browsers support this natively, isn't this sort of thing outside the intended purpose of html. Html should describe content not styling and this sort of thing seems ripe for abuse. I thought XML was the markup language for describing custom data. Adding the ability to create your own DOM elements…
I'd rather say than .
Earlier quoted context omitted.
Hi! I work on Brick. Yes, there are still rough edges on these components, and we're putting them out there in the hopes of getting feedback and bug reports- a traditional beta.
Hi, Is there any documentation to read about the implementation of these components? Does it use x-tags??