61–68 of 68 posts
Earlier quoted context omitted.
CSS1 was mostly about typography, but CSS2 supports layout equivalent to (or rather a superset of) what is possible with HTML tables.
Here's a simple task you can't do in CSS2: Create a multi-line form where the labels are right-aligned to the fields, the fields all line up, and everything expands to fill the contents.
label { display: table-row; }
span { display: table-cell; }
Label:
Longer label:
Earlier quoted context omitted.
CSS does support flexible grids (with power equivalent to HTML tables), it is just that IE has not supported it until IE8, which means it hasn't been used widely. I fint it strange that people keep blaming the shortcomings of IE6+7 on the CSS standard.
Reference? Are you referring to http://www.w3.org/TR/css3-grid/ ? Which is at the working draft status?
The working draft you refer to is a new model which is more powerful than either HTML tables or CSS2.
Earlier quoted context omitted.
HTML should not be used for UI, it's for inserting content and from elements into a presentation. CSS, with the help of graphics and javascript for interactivity should do the UI. Doing something like: with-html :ul :id "site-menu" dolist (menu-item (list "home" "news" "blog" "aboutus")) :li (:a :href concat(*server-root* menu-item) menu-item) Should generate this: home news blog aboutus Then in a CSS page referenced…
In what universe are content, forms and menus not part of the UI?
This is very similar to addition being a far higher level process than the ADD opcode present in every instruction set. Sure, sometimes addition translates to a single ADD, but not always.
Earlier quoted context omitted.
Here's a simple task you can't do in CSS2: Create a multi-line form where the labels are right-aligned to the fields, the fields all line up, and everything expands to fill the contents.
label { display: table-row; } span { display: table-cell; } Label: Longer label:
Earlier quoted context omitted.
Reference? Are you referring to http://www.w3.org/TR/css3-grid/ ? Which is at the working draft status?
CSS2 (which has been a recommendation for a decade) supports display:table, which is equivalent to the layout model of HTML-tables: http://www.w3.org/TR/CSS21/tables.html#value-def-table The working draft you refer to is a new model which is more powerful than either HTML tables or CSS2.
Earlier quoted context omitted.
Reference? Are you referring to http://www.w3.org/TR/css3-grid/ ? Which is at the working draft status?
CSS2 (which has been a recommendation for a decade) supports display:table, which is equivalent to the layout model of HTML-tables: http://www.w3.org/TR/CSS21/tables.html#value-def-table The working draft you refer to is a new model which is more powerful than either HTML tables or CSS2.
The question was whether CSS supports the primitives required to do grid layouts without coupling the CSS to HTML, effectively requiring the two of them to be treated as object code.
If you're going to require that the markup contain divs that are ordered and nested just so, so that they can be styled to layout like a table, then you might as well just use a table. Either way you are coupling presentation to semantics.
Earlier quoted context omitted.
In what universe are content, forms and menus not part of the UI?
In a world where you can layer truly higher-level UI elements on top of them? Just because some elements map 1:1 doesn't mean all do. You can generate a button from or but that goesn't mean you can't generate image "buttons". The final generation of a "button" should be left to your rendering module. This is very similar to addition being a far higher level process than the ADD opcode present in every instruction set…
Skinning, as you point out, often demands modification to the DOM, a task to which HTML and CSS alone are unsuited. It can be done with JavaScript, but it's much more practical and reliable to use a server-side abstraction a la ASP.NET or Seaside. This is more or less the point made by the original article.
Earlier quoted context omitted.
CSS2 (which has been a recommendation for a decade) supports display:table, which is equivalent to the layout model of HTML-tables: http://www.w3.org/TR/CSS21/tables.html#value-def-table The working draft you refer to is a new model which is more powerful than either HTML tables or CSS2.
CSS emulation of tables doesn't meet the requirement though. The question was whether CSS supports the primitives required to do grid layouts without coupling the CSS to HTML, effectively requiring the two of them to be treated as object code. If you're going to require that the markup contain divs that are ordered and nested just so, so that they can be styled to layout like a table, then you might as well just use…
You don't have to use divs, you can use semantic elements (P, whatever) if that is appropriate for the content.
You definitely might not just as well use a table. The trouble with tables for layout is that they have the wrong semantics, which means they makes the page less accessible.