Re: [whatwg] [br] element should not be a line break
On Fri, Aug 6, 2010 at 4:29 PM, Aryeh Gregor wrote: > > On Thu, Aug 5, 2010 at 2:53 PM, Bryce Fields wrote: > > Why not just list along with the other obsolete elements instead of > > trying to rebrand it semantically? > > What markup do you propose for addresses and poems, and in what > practical sense would this markup be superior to using ? The HTML5 spec says of : "The pre element represents a block of preformatted text, in which structure is represented by typographic conventions rather than by elements." sounds ideal for both examples to me (in conjunction w/ the element in the second example. It preserves the line breaks w/o adding any overhead markup to the mix. -- - Bryce Fields www.royalrodent.com "Do or do not. There is no try." -- Yoda
Re: [whatwg] [br] element should not be a line break
On Thu, Aug 5, 2010 at 1:24 PM, Christoph Päper wrote: > Jeremy Keith: > > > > The element is currently defined as "a paragraph-level thematic > break." I think could be defined as "a text-level thematic break." > > That makes perfect sense. The only problem I see is existing content which > relies on consecutive ‘br’s producing multiple line breaks, i.e. often a > paragraph-like appearance. (Although ‘br’s were always intended to be > collapsed, browsers never did this.) Why not just list along with the other obsolete elements instead of trying to rebrand it semantically? Let's face it. is a pain to try to rationalize as a purely semantic element and any use you have for the element could probably easily be accomplished w/ other semantic code. Why not just call it obsolete and discourage authors and vendors from using it? (first post...be gentle...) :) - Bryce Fields www.royalrodent.com "Do or do not. There is no try." -- Yoda
