Firefox still does not seem to support fully web components (html templates, custom elements, shadowdom see http://caniuse.com/#search=shadowdom )
I hope they will get there fast - this will put pressure on dinosaurs like IE or Safari
Mozilla Brick
11–20 of 122 posts
Re: Mozilla Brick
#12The demos seems very unpolished but I hope they keep working on it. Does anyone know what framework is used to 'generate' such doc websites? http://brick.mozilla.io/v2.0/docs
This page is throwing an exception for me... http://brick.readme.io/v1.0/blog/welcome-to-mozilla-brick looks like the link should be v2.0 instead of v1.0
Link fixed!
Re: Mozilla Brick
#13The demos seems very unpolished but I hope they keep working on it. Does anyone know what framework is used to 'generate' such doc websites? http://brick.mozilla.io/v2.0/docs
https://readme.io/ edit: damn, "Normally $99/month | $79/mo" for documentation
It's currently only $39/mo.
There's also a free tier that does the three column layout, which is targeted at projects and single developers (rather than actual startups or companies).
Re: Mozilla Brick
#14Firefox still does not seem to support fully web components (html templates, custom elements, shadowdom see http://caniuse.com/#search=shadowdom ) I hope they will get there fast - this will put pressure on dinosaurs like IE or Safari
I hope the apps market keeps recovering. This will put pressure on dinosaurs like browsers pretending to be an OS.
Re: Mozilla Brick
#15Firefox still does not seem to support fully web components (html templates, custom elements, shadowdom see http://caniuse.com/#search=shadowdom ) I hope they will get there fast - this will put pressure on dinosaurs like IE or Safari
I hope the apps market keeps recovering. This will put pressure on dinosaurs like browsers pretending to be an OS.
yea because it's much better to have closed, restricted app markets (like Apple, Google, Microsoft ones) than web standards.
Re: Mozilla Brick
#16I like how the documentation and example area laid out side by side, anyone cares to describe how they accomplished that? Thanks aot.
Re: Mozilla Brick
#17The things that deters me about Brick are that there aren't very many components yet, they aren't very styled or pretty, and the site doesn't show me what the components look like on one page (I have to click through to a demo for each component). It's only been around for a year, though honestly with the support it has gotten, I'd need to see more before I'm able to imagine developers using it. Obviously, it's a bea…
Ionic's widgets aren't web components and aren't usable outside of Ionic/AngularJS. This means they're not recognized as custom elements by the browser (no future dev tools support). They leak DOM and CSS internals into the page. Worse, they require the host application to be Angular based.
Brick components are encapsulated, both with shadow DOM and scoped CSS, and usable in any web page and with any or no framework. You can freely mix Brick, Polymer, Bosonic, or "raw" custom elements in a single page.
edit: It looks like Mozilla is dropping X-Tag in favor of "vanilla" (what I called "raw") standard web components APIs. This would make Brick a collection of components, rather than a web component helper library like Polymer, and more akin the to Polymer project's Paper Elements.
Re: Mozilla Brick
#18wth is going on at mozilla? There seems to be a lot of excitement to create stuff, without much attention to whether it's needed .. or where the lifecycle goes beyond creation.
http://www.ianbicking.org/blog/2014/09/professional-transiti...
Re: Mozilla Brick
#19The things that deters me about Brick are that there aren't very many components yet, they aren't very styled or pretty, and the site doesn't show me what the components look like on one page (I have to click through to a demo for each component). It's only been around for a year, though honestly with the support it has gotten, I'd need to see more before I'm able to imagine developers using it. Obviously, it's a bea…
Ionic's widgets aren't web components and aren't usable outside of Ionic/AngularJS. This means they're not recognized as custom elements by the browser (no future dev tools support). They leak DOM and CSS internals into the page. Worse, they require the host application to be Angular based. Brick components are encapsulated, both with shadow DOM and scoped CSS, and usable in any web page and with any or no framework.…
Definitely, though when it comes to UI frameworks, many developers want a complete (and styled) solution, and usually stick to a cohesive framework. Brick is obviously more modular, but that's not enough yet. It still needs more components and perhaps themes in order to be looked up, but I recognize it's a new project. Hopefully, the exposure today gets it some contributors.
Re: Mozilla Brick
#20Can I use this client-side? From what I read on the page this seems to be only geared towards a certain server-side-setup with node.js, brewer and stuff.