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

Groundwork - A Responsive HTML5, CSS and JavaScript Framework

groundwork.sidereel.com

Post reply on HN
Print view View original

91–98 of 98 posts

Re: Groundwork - A Responsive HTML5, CSS and JavaScript Framework

#91

Post by ghepting »

a_m0d wrote: post #28

This framework is quite broken on the iPad (in Chrome). - The dropdown menu doesn't work well. It triggers on hover, but trying to do "hoverintent" on the iPad simply fires the click event on the button, causing the menu to appear briefly before the page navigates. - I can't even scroll at all on the demo pages. Dragging the page (to scroll) just drags the whole tab rather than actually scrolling.

Thank you very much for the feedback. If you would post the issues you're experiencing on the Github page, that would be really helpful in getting any bugs resolved! :)

Re: Groundwork - A Responsive HTML5, CSS and JavaScript Framework

#92

Post by ghepting »

sgdesign wrote: post #11
Swizec wrote: post #8

Parts of the site look a bit blurry on a retina :( That's really not the best first impression for this sort of site ...

Same here: http://cl.ly/N1KK

This must be related to using -webkit-filter:drop-shadow()... ?

Re: Groundwork - A Responsive HTML5, CSS and JavaScript Framework

#94

Post by ghepting »

instakill wrote: post #83

Nice looking, but those boxes look exactly like buttons. Very confusing.

Hey, thank you for the feedback. Just to be sure, are you referring to the Messages and Callout UI elements? If so, I totally see your point, that may be something we'll want to change.

Re: Groundwork - A Responsive HTML5, CSS and JavaScript Framework

#95

Post by ghepting »

nkozyra wrote: post #20

Some notes: As mentioned, one of the first things that should be addressed when you're building a competing framework is what yours offers that the "big boys" don't. I don't really see that; indeed, what I'm first hit with is something that doesn't look as polished as Bootstrap. As I poke through it, the whole framework looks like an analog to Bootstrap; I have to ask ... why? Is responsive text the only thing not av…

I appreciate and respect your opinion on this, but can you explain what about these semantic class names you find is causing you nausea? I've considered having them be chained (i.e. .two-thirds) instead of seperated, but find myself thinking that "" and "" is more natural for me to type

Re: Groundwork - A Responsive HTML5, CSS and JavaScript Framework

#96

Post by ghepting »

goldfeld wrote: post #65
subpixel wrote: post #57

Earlier quoted context omitted.

Because I'm also shopping-around: what are your thoughts on Foundation? What's your problem that Bootstrap doesn't solve?

I need to actually reposition my grid elements when breakpoints happen, not just resize or reflow them. The reordering seems promising (so I can alter the flow by appending css classes instead of needing to mess with html structure).

You can easily alter the overrides in the _responsive.scss to accomplish this :)

Re: Groundwork - A Responsive HTML5, CSS and JavaScript Framework

#97

Post by ghepting »

hbogert wrote: post #51
PavlovsCat wrote: post #36

Earlier quoted context omitted.

Going to the URL of the iframe directly is much faster for me: http://groundwork.sidereel.com/home.html

Indeed, went from unusable to smooth on a nexus 7

Thank you all very much for the feedback on this, I wasn't aware of the negative impact the viewport resizer was having on these mobile devices. It is to be expected that iframes would perform poorly on them and I had included a regex to redirect mobile user agents to the home.html page to avoid them having that served up. Perhaps the mobile device detection needs a more reliable method... Any suggestions? :)

Re: Groundwork - A Responsive HTML5, CSS and JavaScript Framework

#98

Post by tomelders »

ghepting wrote: post #85
tomelders wrote: post #7

Using Safari 6.0.2, clicking on the first input on this page crashes Safari with a speed and efficiency that can only be admired. http://groundwork.sidereel.com/?url=tooltips-js I wish Safari could shut down that quickly when I manually quit. No problem with Chrome.

I thought that was pretty bad ass, too. You've gotta give me credit for exposing such a huge bug to Apple. :)

I've not looked into it. Do you know what the cause was?
Post reply on HN