ghepting

+1

Being the author of this framework, I'd love to have feedback and any issues reported on the github page. https://github.com/groundworkcss/groundwork/issues?state=ope...

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? :)

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

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 "<aside class="one mobile third"></aside>" and "<article class="two mobile thirds"></article>" is more natural for me to type

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.

I think -webkit-filter is to blame here. Webkit must not support different pixel densities with these yet :(

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

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! :)

Foundation has really tought me a lot and inspired me over the years. I gladly admit that I've been heavily influenced and learned a lot by the amazing work the Zurbians have been doing. I thought about just contributing to Foundation, but had so many ideas and things I wanted to do, that I knew they would eventually tire of reviewing my frequent pull requests :)

hehe, I <3 Zurb, I've followed them and the cool stuff they post on their Playground and have been inspired with what they've done with Foundation over the years, too. Orbit seemed like a great component to include in Groundwork to achieve a MVP. I plan to write a fresh alternative or enhance and contribute to Orbit moving forward. The current version isn't quite as flexible as I want it to be (it needs to properly support content-only sliders with no images, have less image dependencies -- possible utilize SVG/font icons for controls, etc.)

Last I checked, Skeleton is just a grid system and doesn't attempt to be a complete framework (and is basically the old Foundation Grid isn't it? -- I think the guy that made Skeleton used to be a Zurbian) -- We can easily extract the grid system from Groundwork to be stand-alone and use it in the same way. If you'd like, create an issue on the Github page and I'll make it happen!

I agree with this -- I aimed at making Groundwork as close to this as possible. Even the button styles (colors, radius, borders, etc.) are all easily customized in the _variables.scss file. I think there's more we can do to make it even more generic of coarse, I encourage you to create issues on the Github page if you find components have too much stylistic direction. :)

+1 :)

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

Sorry! Not sure what the deal is with the Safari issue related to the tooltips plugin yet. :/

However, as stated in big superscript on the brand name, Groundwork is in Beta and was just published on February 5th (15 days ago). If you would all submit issues and contribute to the project on Github, I bet these bugs will quickly become a thing of the past! :D

As with industry, competition most often leads to further innovation and drive to improve a product. ;)

CoffeeScript is definitely my language of choice and compiled to highly accurate and optionally minified javascript.

Great point! I will work on drafting something to this effect. Thanks for the feedback! :)

The intention here is to encourage customization of the color/radius variables in the _variables.scss partial :)

I am aware of this issue, but haven't identified the problem yet (not on Mountain Lion with my current device) -- any help from the community would be much appreciated! Post any information that would help to resolve this issue here: https://github.com/groundworkcss/groundwork/issues/12

:)

Thanks! Glad you like it :)

This issue is most likely related to the resizer -- if you close the resizer are you still experiencing this issue on the iPad? Also, if everyone can please post issues on the Github Issues that would be very helpful! Thank you! :)