scott100 Posted May 30, 2006 Share Posted May 30, 2006 And scott100, yes. The reason for the style attribute's deprecation is exactly the existance of IDs.<{POST_SNAPBACK}> I personally think this stinks to high heavens So what is w3 aiming for, a pure xhtml document with only links to external .css and .js ? Link to comment Share on other sites More sharing options...
Jonas Posted May 30, 2006 Share Posted May 30, 2006 (edited) I still don't understand why the style attribute would be depreciated, any way. <{POST_SNAPBACK}> Because the style attribute is really no different than any old attribute from older versions of html, in that it's just as highly impractical when making large pages (many documents), going in to edit single style attributes.I personally think this stinks to high heavens So what is w3 aiming for, a pure xhtml document with only links to external .css and .js ?<{POST_SNAPBACK}> I think that's EXACTLY what they are aiming for.HTML: StructureCSS: FormattingJS: Browser scriptingeach in their own documents, with different file extensions. In addition, I like to use a scripting language to include a file called something like head.inc, inside which I have the <script src="" type="text/javascript"></script> and <link ... /> so I can change that in each file by just editing the head.inc file. Edited May 30, 2006 by Jonas Link to comment Share on other sites More sharing options...
Jack McKalling Posted May 30, 2006 Share Posted May 30, 2006 Of course, but occasional structuring style attributes (such as positioning or dimensioning) should not be forced to stay in the stylesheet, you should be able to have some in the document, my opinion Link to comment Share on other sites More sharing options...
boen_robot Posted May 30, 2006 Share Posted May 30, 2006 So what is w3 aiming for, a pure xhtml document with only links to external .css and .js ? Am... yes? I mean, separating content from presentation is their goal after all. XHTML to describe the structure and CSS for the variety of presentations. Link to comment Share on other sites More sharing options...
scott100 Posted May 30, 2006 Share Posted May 30, 2006 I think that's EXACTLY what they are aiming for.HTML: StructureCSS: FormattingJS: Browser scriptingeach in their own documents, with different file extensions.So <style> in the head is next to go? if it hasn't already... Link to comment Share on other sites More sharing options...
Jonas Posted May 30, 2006 Share Posted May 30, 2006 So <style> in the head is next to go? if it hasn't already...<{POST_SNAPBACK}> Possibly... Link to comment Share on other sites More sharing options...
aspnetguy Posted May 30, 2006 Share Posted May 30, 2006 The align attribute for div is depreciated in html 4, as in xhtml strict.And W3Schools had never said Style is depreciated, can't be. You're probably confused with something else, <{POST_SNAPBACK}> He said he found a link on these forums to W3C specs that said it was. I can see the pont. If you are just going to use inline styles why not go back to <font>. I think they are pushing towards having all cSS defined in stylesheets and just referenceing hte ids or classes. Link to comment Share on other sites More sharing options...
boen_robot Posted May 30, 2006 Share Posted May 30, 2006 The <style> element is meant for per-page data, the same way you're allowed to have JS in the head and/or body even. Before such elements are gone, there is a need for a scriptless mechanism to allow different files to be loaded for sections and per-page data. I can do such thing by using XSLT and there are other ways with JS and and server side scriptings, but there's no possible way of doing this with pure XHTML.So sleep tight. The <style> attribute has a long way to live before it's deprecated.[edit] Actually, I'm a big fat liar. There's already a mechanism for that. You can call multiple links, each containing more and more specific things, as long as they are in order of specificness. For example: <link rel="stylesheet" type="text/css" href="site.css" /><link rel="stylesheet" type="text/css" href="section.css" /><link rel="stylesheet" type="text/css" href="subsection.css" />...<link rel="stylesheet" type="text/css" href="page.css" /> So the <style> element is really the next to go. It's only a matter of time until internet and browsers are fast enough for W3C to decide this.[/edit] Link to comment Share on other sites More sharing options...
Jack McKalling Posted May 30, 2006 Share Posted May 30, 2006 But you all forgot the style attribute DOES have an advantage in Xhtml meanings over those presentation elements as font, bold, underline, strike etcetera, namely all those pretentations rubbish in one attribute :)Anyway, I won't use it either for ALL styling statements, but just for the occasional statement that counts for one single element and does not need to be changed ever Only for that I don't want it to be depreciated, should be possible to use it like that. Link to comment Share on other sites More sharing options...
yoshida Posted May 30, 2006 Share Posted May 30, 2006 HTML: structure.CSS: formatting.JS: browser scripting.But where does the content go? Should that be loaded externally through something like AJAX? Ow wait... that's going to be deprecated to since I've only seen it coded in the <head> section.Something tells me everything but databases and serversided scripting will be dead five years from now. Welcome to the AMP era. ^^ Link to comment Share on other sites More sharing options...
Jonas Posted May 30, 2006 Share Posted May 30, 2006 But where does the content go?XML and (X)HTML in unison.(and of course databases, but it's still come out as xml or html on the client-side.) Link to comment Share on other sites More sharing options...
aspnetguy Posted May 30, 2006 Share Posted May 30, 2006 HTML: structure.CSS: formatting.JS: browser scripting.But where does the content go? Should that be loaded externally through something like AJAX? Ow wait... that's going to be deprecated to since I've only seen it coded in the <head> section.Something tells me everything but databases and serversided scripting will be dead five years from now. Welcome to the AMP era. ^^<{POST_SNAPBACK}> AJAX can be stored in external JS files. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now