51–60 of 78 posts
There is a lot of great JS frameworks out there that projects DOM etc., but I always fall back to markup as the best way to build a browser based app
Earlier quoted context omitted.
I'm not having the freezing issue with Chrome (28). But I think there're some major usability issues. I cannot figure out how to input a date. If I input "8" then "16" it's current value is 08/16/yyyy with the "yyyy" part selected. If I continue to input "2" for the year part it changes to 1902. Inputting "20" will reset the date picker back to mm/dd/yyyy.
I believe you are describing the native datepicker , I am seeing the same weirdness. Be advised, the calendar polyfilled calendar is only active when a native implementation is not detected, or you force it to be used. This may be a bug in Chrome itself .
When it comes to search, their kit might eclipse yours...at least for the time being.
On IE10 this library has no animations. Is it possible to polyfill your way to decent support with animations at least on IE10?
(I hate IE but a lot of our customers use it)
Interesting, although I think the "beta" is quite literal. Seems to lack a bit of polish. The one I was most interested in was the Date Picker, but locks up Chrome (28) and Safari (6) on my machine. http://mozilla.github.io/brick/component/datepicker/demo/ind...
21
21
21
21
21
21
21
21
21
21
21
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 a library of tons of stuff I dont use.
Doesnt render well on Opera mobile.
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…
Web Components is an active W3 spec. http://www.w3.org/TR/2013/WD-components-intro-20130606/ All browsers are going to support Web Components eventually and it is going to greatly expand what we thought HTML should or shouldn't do. I think Chrome Chrome Canary has an implementation behind a flag and FF is actively working on it as well.