If everyone's wondering how Ink is different from Bootstrap, the answer is: mainly in how Ink builds layouts. Instead of the column span philosophy, Ink uses percentage based blocks. That alone is a big difference.
Ink – Interface Kit
71–73 of 73 posts
Re: Ink – Interface Kit
#72Can we please come up with a better markup for form element grouping than "div.control-group"? Specifically, HTML has always allowed nesting an inside - and that's more than enough to create either a horizontal or stacked layout. No s needed. And no "for" attribute needed with an unnecessary input ID.
To my knowledge this is incorrect. Assistive technologies don't recognize input names when nested inside of label elements, and as a result is frowned upon by the W3C. Unless you meant something else by, "...HTML has always allowed nesting an inside ..." Source: http://www.w3.org/TR/WCAG20-TECHS/F68.html
Maybe an aria-labelledby attribute would fix this? Heck, could still use a label "for" attribute and keep the input nested.
Either way, I meant that it is legal HTML to do that kind of nesting. Did not know that it was frowned upon, as far as standards are concerned, even assistive.
Re: Ink – Interface Kit
#73Earlier quoted context omitted.
When you put a label with text and the input inside, how would you get the text to take up 150px and the input to be to the right of that consistently across a large form? Such as here: https://www.roadreadycertified.com/order/begin/ Note: It's just an example, not promoting the site.
It's possible to do by adding a padding-right as well as position:relative on the label, and then position:absolute on the input to place it over the padded area. Not the easiest CSS to write, but I strongly prefer clean markup (at a cost of hackish CSS) to hackish markup.