Re: [whatwg] Joined blocks

2008-08-13 Thread Kristof Zelechovski
The concept of joint blocks (which should rather be named disjoint canvas) is relevant mainly to printouts. As it has already been explained in the booklet case, HTML is not the primary workhorse for preparing professional printouts. Window content is stretchable, unlike a print sheet, therefore

Re: [whatwg] Joined blocks

2008-08-03 Thread Christoph Päper
Shannon: Something I think is really missing from HTML is "linked text" Linked or continued (numbered, ordered) lists have been dicussed here a while ago, and were rejected if I remember correctly. They made a stronger use case than generic continued texts in my opinion, although both co

Re: [whatwg] Joined blocks

2008-08-02 Thread Russell Leggett
Ignore my last statement. It was a draft I wrote before reading Ian's response. If he has something in mind to get the same thing accomplished without adding extra tags, all the better. On Sat, Aug 2, 2008 at 8:06 PM, Russell Leggett <[EMAIL PROTECTED]>wrote: > I would be happy to have this as a

Re: [whatwg] Joined blocks

2008-08-02 Thread Russell Leggett
I would be happy to have this as a purely css solution, but if multiple container elements are required for the content to flow to, would you not want that relationship in the html? We specify anchors, links, and relationships in html, why not this? How the flow between blocks should certainly be c

Re: [whatwg] Joined blocks

2008-08-02 Thread Ian Hickson
On Sat, 2 Aug 2008, Shannon wrote: > > The accuracy of your statement depends largely on whether the > specification allows the content source to be defined across all joined > blocks or only in the first. For example: > > first parasecond para > ... other unrelated markup ... > third para > >

Re: [whatwg] Joined blocks

2008-08-01 Thread Shannon
Tab Atkins Jr. wrote: This is definitely and distinctly a CSS issue, not a HTML one. The fact that the contents of an element flow into another box elsewhere in the page has nothing to do with the underlying structure of the data - it's still a single cohesive element, and thus in html it wo

Re: [whatwg] Joined blocks

2008-08-01 Thread Tab Atkins Jr.
On Fri, Aug 1, 2008 at 7:28 AM, Russell Leggett <[EMAIL PROTECTED]>wrote: > For what it's worth, Shannon, I totally agree with you. Not only is this > something I have been wanted for a long time, but I think it belongs in the > html. It's one thing if you just want columns, which is being covered

Re: [whatwg] Joined blocks

2008-08-01 Thread Russell Leggett
For what it's worth, Shannon, I totally agree with you. Not only is this something I have been wanted for a long time, but I think it belongs in the html. It's one thing if you just want columns, which is being covered here: http://www.w3.org/TR/css3-multicol/. The CSS covers that nicely, but there

Re: [whatwg] Joined blocks

2008-07-31 Thread Shannon
I agree this is _mostly_ a CSS issue except that there is semantic meaning to the join attribute beyond layout. The attribute could serve as a guide to search engines, web-scrapers or WYSIWYG applications that two areas of the page should be considered a single piece of content. I am also unsur

Re: [whatwg] Joined blocks

2008-07-31 Thread Ian Hickson
On Fri, 1 Aug 2008, Shannon wrote: > > Something I think is really missing from HTML is "linked text" (in the > traditional desktop publishing sense), where two or more text boxes are > joined so that content overflows the first into the second and > subsequent boxes. This is a standard process