Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Brick – UI Components for Modern Web Apps

mozilla.github.io

Post reply on HN
Print view View original

41–50 of 78 posts

Re: Brick – UI Components for Modern Web Apps

#41

Post by potch »

nogridbag wrote: post #27
jwilliams wrote: post #2

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...

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.

If you wouldn't mind, could you file this (and other problems you run into) as issues? https://github.com/mozilla/brick/issues

Re: Brick – UI Components for Modern Web Apps

#42

Post by csuwldcat »

moondowner wrote: post #4
jwilliams wrote: post #2

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...

Locks FF Nightly too.

Given that the errors and ability to reproduce are so erratic (to the extent that people with the very same browser versions on the same platform are seeing different behavior), I have a feeling the issue may be something like this: https://github.com/eternicode/bootstrap-datepicker/issues/95...

Re: Brick – UI Components for Modern Web Apps

#43

Post by csuwldcat »

NKCSS wrote: post #21
jwilliams wrote: post #2

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...

Yup, has been a while since I've had to fire up IE to view something that doesn't work in chrome :P While the page does load, it has a long running script that dies :P

Given that the errors and ability to reproduce are so erratic (to the extent that people with the very same browser versions on the same platform are seeing different behavior), I have a feeling the issue may be something like this: https://github.com/eternicode/bootstrap-datepicker/issues/95...

Re: Brick – UI Components for Modern Web Apps

#44

Post by csuwldcat »

cateye wrote: post #12
jwilliams wrote: post #2

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...

I can confirm this on OSX - Chrome 28.

The issue might be locality dependent, we have several people where who are running the exact same version and platform that cannot reproduce - could be an issue like this: https://github.com/eternicode/bootstrap-datepicker/issues/95...

Re: Brick – UI Components for Modern Web Apps

#48

Post by spankalee »

csuwldcat wrote: post #36
bpatrianakos wrote: post #28

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…

You're overlooking that the underlying technology - Web Components - is landing as a standard as we speak in both Firefox and Chrome. The idea that creating custom elements is inherently bad is an urban legend - there is no empirical basis for such a claim. Additionally, you are mixing metaphors, Custom Elements are not meant to describe data, they are meant to create new, active UI components and other useful tags.

Well, you could use such tags to describe data directly in the markup. I'll think we'll see two definite camps on that issue. Of course, what's data?

Re: Brick – UI Components for Modern Web Apps

#49

Post by bsimpson »

jwilliams wrote: post #2

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...

Works fine in ChromeOS 28.0.1500.95
Post reply on HN