Slashdot Mirror


Help Beta Test Slashdot CSS

After almost 8 years, Slashdot's HTML is finally getting an overhaul. For now the changes are almost entirely under the hood, as we migrate the current skin to CSS. Slashdot itself will migrate in the next few weeks, but for now, we'd appreciate it if people who understand CSS could take a look at Slashcode. If you use a browser that lets you select a stylesheet, you can take a look at that site with the Slashdot CSS Skin. Keep in mind that Slashcode doesn't look exactly like Slashdot, so there will be some differences between that site, and the final version that will appear on Slashdot. We're mainly looking for feedback on compatibility issues and blatant bugs. You can use our our SF bug tracker to submit bug reports. Thanks for your help. Once we move Slashdot, work will begin on a new look & feel. If you have ideas, you could start playing with the CSS stylesheets now!

581 comments

  1. Just one question... by suso · · Score: 5, Funny

    After almost 8 years, Slashdot's HTML is finally getting an overhaul.

    What is a HTML?

    1. Re:Just one question... by JoeBar · · Score: 3, Funny

      What is a joke?

    2. Re:Just one question... by falcon5768 · · Score: 1, Insightful
      Here is a good one, why dont slashdot redo the moderation system to prevent idiot trolls for modding something funny offtopic, redundant, flamebait, or troll.

      this is getting insain. Just cause your too young to get the joke doesnt mean 90% of us dont get it.

      --

      "Slashdot, where telling the truth is overrated but lying is insightful."

    3. Re:Just one question... by D'Sphitz · · Score: 0, Flamebait

      Well, if 90% of us get it, then 90% of the moderators get it also, and they'll mod it appropriately. It's all just a big retarded popularity contest anyway, and it should be done away with altogether IMO.

    4. Re:Just one question... by D'Sphitz · · Score: 0, Flamebait

      and no, "What is a HTML?" isn't funny at all, it's first post karma whoring.

    5. Re:Just one question... by Saeed+al-Sahaf · · Score: 1, Funny

      Woah. Dude. Less coffee.

      --
      "Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
    6. Re:Just one question... by Anonymous Coward · · Score: 0

      I agree. This is getting totally insain.

      What is an 'insain'?

    7. Re:Just one question... by aklix · · Score: 2, Insightful

      At the time of this posting, the parent of this post is modded 2, Insightful...

    8. Re:Just one question... by Mercano · · Score: 1

      I belive its called meta moderation. Mods who get "unfair"s on thier recent mod point expenditures are less likely to get mod points next time.

      --
      #include <signature.h>
    9. Re:Just one question... by Anonymous Coward · · Score: 0

      Here is a good one, why dont slashdot redo the moderation system to prevent idiot trolls for modding something funny offtopic, redundant, flamebait, or troll.

      I know, I know! They should add a -1, Not Funny.

    10. Re:Just one question... by jkmiecik · · Score: 1

      At the time of this posting, the parent of this post is modded 2, Insightful...

      (No, really.)

    11. Re:Just one question... by Anonymous Coward · · Score: 0


      At the time of this post, the parent is modded 1...

    12. Re:Just one question... by allism · · Score: 1

      Your moderation must have come from one of the staff. I agree, it is an incredibly ugly color scheme.

      Every time I see the "It is what IT is" slogan, I think, "What, feces?" But not so politely worded.

    13. Re:Just one question... by Kent+Recal · · Score: 2, Funny

      Cool, is this the +2-Insightful thread?

    14. Re:Just one question... by Trejkaz · · Score: 1

      I think it was some ancient format which was superceded by XHTML in 1999, over five years ago. I didn't realise anyone used it still, but looking at Slashcode, it seems they still do.

      --
      Karma: It's all a bunch of tree-huggin' hippy crap!
    15. Re:Just one question... by Xyrus · · Score: 1

      Slashdot's updating?

      *looks around*

      Well, that explains all these monkeys flying outta my butt.

      How about a little warning next time, eh CmdrTaco? That's a hard one to explain during a team meeting.

      ~X~

      --
      ~X~
    16. Re:Just one question... by Shaklee39 · · Score: 1

      If you are so old shouldn't you have spelled "you're" correctly?

    17. Re:Just one question... by D'Sphitz · · Score: 1

      if i'm a karma whore apparently i'm not very good at it

  2. css!! by jlebrech · · Score: 5, Informative

    If you do change to CSS beware as some CSS is IE specific, like list trees.

    1. Re:css!! by MyLongNickName · · Score: 5, Funny

      Doesn't everyone on Slashdot use IE?

      (sorry)

      --
      See my journal for slashdot ID's by year. Mine created in 2005. http://slashdot.org/journal/289875/slashdot-ids-by-year
    2. Re:css!! by qw(name) · · Score: 5, Insightful

      The "design for all browsers" paradigm isn't a good one. It promotes the use of non-compliant browsers. It's much better to design to the standards no matter what.

    3. Re:css!! by VJ42 · · Score: 3, Informative

      That shouldn't be a problem if the developers remember to use the w3c CSS validatior:
      http://jigsaw.w3.org/css-validator/

      But seeing as they don't bother using even the html validator I'm not counting on it.

      --
      If I have nothing to hide, you have no reason to search me
    4. Re:css!! by qw(name) · · Score: 1

      There already appears to be a problem with validating Slashcode.com's HTML 4.01 Strict main page.

      http://validator.w3.org/check?uri=http%3A%2F%2Fwww .slashcode.com%2F
    5. Re:css!! by cybersaga · · Score: 4, Funny

      Thank goodness everyone's customers use standards compliant browsers. Whew! Your theory would be totally ridiculous if they didn't.

      [/sarcasm]

    6. Re:css!! by bmongar · · Score: 3, Insightful

      "Design for standards" paradigm isn't a good one. It promotes looking for consultants that won't drive away business.

      --
      As x approaches total apathy I couldn't care less.
    7. Re:css!! by T-Ranger · · Score: 1

      But here in reality, that hast to be "design for a subset of standards that major browsers actually use"

    8. Re:css!! by daniil · · Score: 1

      Now try the same trick with the Slashdot main page :p

      --
      Man is a slave because freedom is difficult, whereas slavery is easy.
    9. Re:css!! by qw(name) · · Score: 1

      It promotes good coding practices both at the browser level and at the (X)HTML/CSS level. Why some browsers still (after all these years) do render various elements according to established standards is beyond me.

    10. Re:css!! by mrchaotica · · Score: 3, Interesting

      If you think about it, his theory would be totally unnecessary if they did.

      Incidentally, I agree with him -- designing web sites for broken browsers is like giving illegal immigrants drivers' licenses: it's stupid and it doesn't fix the underlying problem.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    11. Re:css!! by VJ42 · · Score: 1

      IIRC Slashcode uses HTML 3.2, but you're right anyway, it dosn't validate like that either.

      --
      If I have nothing to hide, you have no reason to search me
    12. Re:css!! by Adlopa · · Score: 1

      Anyone got a Coral cache for this..?

    13. Re:css!! by Anonymous Coward · · Score: 0
      that hast to be

      Verily and forsooth, my good man!

    14. Re:css!! by Anonymous Coward · · Score: 0

      To the vast majority of the world, a "good coding practice" is one that makes the code useful to the most amounts of people (i.e. viewable by the most people's browser). Nobody cares if some code is "conceptually beautiful", or "internally consistent", or "a 31337 hack" or whatever to a bunch of code monkeys.

    15. Re:css!! by Metteyya · · Score: 1

      The "design for all browsers" paradigm isn't a good one. It promotes the use of non-compliant browsers. It's much better to design to the standards no matter what.
      Yeah, sounds great. You newer wrote (X)HTML & CSS for someone who paid you for it, did you? Flushing the toilet after dropping 85% of internet users may be OK if you write your own blog, but is inacceptable if site is meant to be a ?ortal.
      If you want standards, read Zeldman. He never advises throwing away support for IE.

    16. Re:css!! by Corbie · · Score: 2, Informative

      Which is why you should design for standards first, and then fix what you can for non-compliant browsers. Make it accessable, but make it standards-based first and foremost.

    17. Re:css!! by seriesrover · · Score: 2, Informative
      Show me a business that has decided to cut out 85% of its customer base and I'll show you a thousand that have decided not to. The need for standards vary from "not important" to a "must have" depending on their application. To pretend IE doesn't exist, or code as if they don't matter, is business suicide.

      Besides, does any browser meet all of the W3C standards flawlessly?

    18. Re:css!! by chromaphobic · · Score: 5, Insightful

      Right, so the intelligent thing would be to explain to my clients that it's Microsoft's fault and not mine that the site I just designed for them doesn't display properly for 9 out of 10 of their customers? After all, I followed the standards and it would be stupid not to!

      "Sorry Mr. Client, standards evangelism is far more important to me than your customers. Now, when should I be expecting payment?" Yeah, that'll fly.

      I think I'll keep using my current methodology: Design to the standards first, then add whatever hacks are needed to handle the various browser bugs in secondary stylesheets to ensure the widest possible compatability across as many browsers and platforms as I can.

      Call me crazy, but keeping the client and their customers satisfied (and, as a result, making the site display properly for as many visitors as I possibly can, rather than just those that use a "standards compliant" browser) and subsequently getting paid for my work is more important to me than beating the standards drum.

    19. Re:css!! by dr.badass · · Score: 1

      The "ignore browser differences" paradigm isn't a good one. It promotes the use of websites other than the one you're designing. It's much better to remain in touch with reality.

      --
      Don't become a regular here -- you will become retarded.
    20. Re:css!! by jizmonkey · · Score: 0, Flamebait
      designing web sites for broken browsers is like giving illegal immigrants drivers' licenses: it's stupid and it doesn't fix the underlying problem

      It's stupid to give immigrants drivers' licenses, huh? Boy, you so succicently marshalled and analyzed the benefits and problems of the alternatives to having the law be blind to the existence of millions of people. With an intellect like yours, I'm sure we can expect the President to appoint you to a high-level position in Washington within the week. In fact, I'm forwarding your message to president@whitehouse.gov, because your message was so incisive and thought-provoking, that he needs to have it on his desk today, because it demonstrates that your intellect far surpasses any other candidate he might even be thinking of appointing for any of hundreds of positions.

      And the "underlying problem" you're referring to, I totally agree, you are so right. The seven million undocumented immigrants in the United States need to be gotten rid of. Immediately. Clearly, we can't deport so many people, given how slow it took to evacuate New Orleans, so the best answer (the "final solution" you might say) to this "seven million" is to execute them and use them as landfill in low-lying flood-prone areas. It will be difficult to distinguish American citizens, given that the children of undocumented immigrants are full citizens just like you and me and undocumented immigrants often marry citizens but cannot get their green card for legal reasons, but by gum, we can do it. With some American know-how, we could convert the Astrodome (once the refugees leave) into a high-performance landfill factory like the Germans used to have, only more advanced. Undocumented immigrants go in, landfill comes out. We would have the problem of what to do with all those American citizens who suddenly no longer have parents or spouses, and crime would dramatically increase by breaking up families, but that is a secondary concern to "fixing the underlying problem."

      I feel that my mind has grown just being exposed to your brilliant ideas.

      --
      With great power comes great fan noise.
    21. Re:css!! by panic911 · · Score: 1

      All common browsers have their CSS issues. Even firefox and opera have certain non-standard css tags. Besides just that, the ones that do implement all (or most) standard css tags, probably won't implement them the same way - so you need to watch out for rendering problems across browsers.

    22. Re:css!! by godders · · Score: 1

      Fine, but there's a BIG difference between making sure stuff works in most browsers, and producing your HTML The Microsoft Way (tm) The fact is that all the modern browsers' render 95% of the standards they support identically. It's just you only hear about the other 5% because it causes so many problems. So design with standards as far as you can, using basic functionality that's well supported, and THEN test in other browsers and fix it up where appropriate. Just because browsers are different that does not mean you have to either pick 'standards' and not support IE, or pick 'The Microsoft Way' and not support anything else, and those that suggest so are generally trying to make excuses for the fact they can't be bothered to learn properly.

    23. Re:css!! by Ucklak · · Score: 1

      But there's no problem to coding to the standard or what is widely accepted from the published then tweaking for IE like most of us XHTML coders do.

      At least Opera workarounds are just different interpretations and not bugs.

      IE adds a pixel here and a pixel there.

      The Tasman engine (IE/Mac) sucks the most and causes the stylesheet to become bloated but isn't really _that_ big of a problem.

      My favorite IE workaround that isn't a hack is the !important rule.

      --
      if you steal from one source, that is plagiarism, if you steal from many, well, that's just research.
    24. Re:css!! by radish · · Score: 1

      Incidentally, I agree with him -- designing web sites for broken browsers is like giving illegal immigrants drivers' licenses: it's stupid and it doesn't fix the underlying problem.
      Terrible analogy. A more accurate one would be your store refusing to serve illegal immigrants while every other store in town still does. You may be standing up for what you see as right, but you'll go bankrupt in the process. A little pragmatism goes a long way.

      --

      ---- Den ene knappen er powerknapp, den andre er Bender voice knapp "Bite My Shiny Metal Ass"

    25. Re:css!! by shakah · · Score: 1

      I thought the goal of drivers' licenses for illegal immigrants was to lower the number of uninsured vehicles on the road. What's stupid about that, and how does it not address that problem?

    26. Re:css!! by CowboyBob500 · · Score: 4, Interesting

      Personally I design to standards and then detail the charges for the time it takes me to fix it on IE in the final invoice. Then the client knows exactly how much the use of IE is costing them as a percentage of the total cost of the project.

      It doesn't cost them anymore than before, but it really opens their eyes.

      Bob

    27. Re:css!! by Reapman · · Score: 1

      That's great, of course if 80% of your users can't get to your site, they're more then likely going to go to your competitor instead of a new browser. Sad but true. Proclaming yourself 100% standard doesn't do you any good if nobody on this planet can view the page. Of course Slashdot might be able to get away with it since we're generally more tech savy then the average bear and it's not really a commerce site. When I design a site I make it as standard as possible without breaking it in any of the "big 3" (Opera, FF, IE, and Text Browsers for accessablity where possible). Heck as far as I know there isn't a 100% standards based browser, is there?

    28. Re:css!! by spongman · · Score: 1

      actually, the correct solution is to design to the standards, and as for complaining customers: shoot them in the name of open standards.

      viva la revolution!!

      <joke/>

    29. Re:css!! by Haeleth · · Score: 1

      Besides, does any browser meet all of the W3C standards flawlessly?

      Of course there isn't, and nobody's pretending there is. But standards-compliance is analogue, not digital. No browser is fully standards-compliant - but most of them are a hell of a lot closer than IE.

      Using the fact that no browser is perfect as an excuse for not even trying to make your site standards-compliant (or worse, for designing for IE only) is a bit like saying "why lock up thieves and murderers, everyone's broken some law or other!"

      But the fact is that thieves and murderers are not on the same level as people who occasionally exceed a speed limit by 5 mph. And IE's brazen disregard for basic elements even of CSS1, a ten-year old standard, is not on the same level as Opera's failure to implement a few minor features.

    30. Re:css!! by Jugalator · · Score: 1

      The "design for all browsers" paradigm isn't a good one. It promotes the use of non-compliant browsers. It's much better to design to the standards no matter what.

      I doubt it, just look at the Acid Test what you may end up with then if you're careless. My suggestion: Design to standards, but try to find a reasonable lowest common denominator.

      --
      Beware: In C++, your friends can see your privates!
    31. Re:css!! by mrchaotica · · Score: 3, Insightful

      No, you should design for standards, and then sit back and relax. Let it look suboptimal in non-compliant browsers; it'll give them incentive to upgrade.

      This, of course, assumes that the bugs in the non-compliant browsers result in only cosmetic defects; however, I would say that if something is so broken in IE that it's genuinely unusable, then you should try approaching the problem in a completely different way.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    32. Re:css!! by hdante · · Score: 1

      Slashdot readers are not supposed to be clients. They're supposed to choose the browser they like and understand why slashdot looks awful on it. :-)

      BTW, the picture of the dog is being covered by the first news in the slashcode site. It's awful that they don't suppot firefox... ;-)

    33. Re:css!! by mrchaotica · · Score: 1

      It does address the problem of uninsured vehicles, but that's beside the point. The real problem is that the illegal immigrants are here in the first place. It's stupid to give them drivers' licenses because we should be deporting them instead.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    34. Re:css!! by Anonymous Coward · · Score: 0

      Loading slashcode I got a 500 error -- got real happy thinking /. /.ed itself. Hit refresh, /code loaded - hot damn!

    35. Re:css!! by Anonymous Coward · · Score: 0

      want to check out difference between firefox and ie in css? check out dalata.net in both.

    36. Re:css!! by Watts+Martin · · Score: 4, Insightful

      The way I design web pages -- and I'm pretty sure I'm not alone, doing something very radical here! -- is to design for Gecko-based browsers and Safari first, because they very rarely show major deviances from one another or standards. Then I take the design to Windows IE and tweak the style sheets to account for anything that broke there, which is usually pretty minimal--frustrating, but its quirks are known and well documented. And I make sure the page is readable and usable in Lynx. At the end of the day, I have fine standards-compliant XHTML and CSS that works everywhere from Firefox to the Sidekick.

      In almost all cases you can make IE happy without having to seriously compromise. There are broken browsers I'm perfectly happy to ignore: pre-Mozilla Netscape, pre-5.0 IE, NetPositive for BeOS, HotJava. These are ones that you simply can't tweak for; generating web pages that renders perfectly on all of those platforms can be done, as OS News proves -- and can only be done by creating hideously bloated web pages where 70-80% of what's being sent to the browsers is markup, as, uh, OS News proves. (The term "pathologically compliant" comes to mind.)

    37. Re:css!! by Dan+Ost · · Score: 1

      That's brilliant. How do your customers typically respond?

      --

      *sigh* back to work...
    38. Re:css!! by Overly+Critical+Guy · · Score: 1

      Actually, most do. This is based on what Taco has said in the past as well as the logs of sites that get linked in story articles or comments. Not really that surprising.

      --
      "Sufferin' succotash."
    39. Re:css!! by shakah · · Score: 1
      You've been watching too much Fox News Channel.

      Regardless of what you think about the complex issue of illegal immigration, the reality is that illegal immigrants are here, and uninsured driving is a real problem (on several levels).

      But by all means keep up your ranting, I'm sure it will do a lot of good.

    40. Re:css!! by I+Like+Pudding · · Score: 0

      The problem here is that IE *is* the standard.

    41. Re:css!! by dave420 · · Score: 1
      "better" != "sensible"

      People use IE. Most people use IE, in fact. Coding something that doesn't work in it is great for making a point about standards, but really really shit for making something useful.

    42. Re:css!! by Anonymous Coward · · Score: 0
      Regardless of what you think about the complex issue of illegal immigration, the reality is that illegal immigrants are here, and uninsured driving is a real problem (on several levels).

      But by all means keep up your ranting, I'm sure it will do a lot of good.


      Some family members of the deceased in the world trade center would disagree with you adamantly. Some "illegal immigrants" with expired visas spent 8 years here training to kill them. Letting them stay obviously wasn't a good answer either.

      And lay off with the flaming via putting words in mouths. Nobody said they watched Fox except you with a follow up of a hate message based on it.

      Keep up your ranting against imaginary Fox News Channel viewers and blame all your problems on it. I'm sure it will do a lot of good.

    43. Re:css!! by Pfhreakaz0id · · Score: 1

      i'm guessing his client resell rate isn't real high :)

    44. Re:css!! by Corbie · · Score: 3, Insightful

      To a certain extent I aggree with you - especially in regards to certain cosmetic things looking suboptimal in non-compliant browsers. However, this design perrogative is only available when you, the designer, are directly making the calls for what goes and what doesnt. In the case of working for paying clients, or poorly-informed employers with phobias for non-microsoft platforms, this is in many cases not an option. I heartlily beleive that it is our duty as designers and programmers to educate those we work with and for about the reasons for writing standards compliant code, but there will always be times when the end product is simply out of our control (client need intranet site, only uses old Windows boxes for for office machines, won't switch browsers -or- client is extremely picky and the bosses demand his every demand be made, naturally when he pulls his lovely full XHTML/CSS site up in IE on his home machine he is pissed and cannot be reasoned with). This is why I suggest a happy median - structure content with standards-compliant XHTML, and use as much CSS as humanly possible that will work in both browsers. Then, you can always add on some of the lovely options that is available with a browser that supports the full extent of CSS2, and begin making suggestions. That way, even if they don't buy it, you still have a site that conforms to the standard, even if you had to make a few sacrifices to do it (not that there's anything against coming up with a new solution that no one has ever thought of that makes your particular design display perfectly cross-browser). The web is about accessability, and if you loose that, then what's the point?

    45. Re:css!! by Hes+Nikke · · Score: 1

      just use a browser detect and spam IE users telling them that it looks ugly because IE sux... thats what i do when i design for standards, and don't want to bother to "fix" it for IE.

      --
      Don't call me back. Give me a call back. Bye. So yeah. But bye our, well, but alright we are on a shirt this chill.
    46. Re:css!! by fbjon · · Score: 1

      Dependes on how bad suboptimal means in non-compliant browsers. The site should be usable at all times, and stuff like overlapping blocks and covered text should be fixed (it creates mounds of frustration), but it doesn't have to look picture perfect.

      --
      True confidence comes not from realising you are as good as your peers, but that your peers are as bad as you are.
    47. Re:css!! by Anonymous Coward · · Score: 0

      Designing Slashdot is a liiittle bit different than for a paying customer. In fact, a Slashdot that has cosmetic errors on broken browsers may be a good thing. It is the users that want to read News For Nerds, not the other way around. Which is probably only true for a handful of web sites in the world

    48. Re:css!! by shakah · · Score: 1

      Wow. Hit a nerve there, eh?

    49. Re:css!! by CowboyBob500 · · Score: 2, Interesting

      I don't just target IE. I give a complete breakdown of costs for all things on the invoice. But unlike most people instead of just detailing "web pages" or something, I break down what the cost of development was for each browser.

      Again, it doesn't cost the client anything more than normal, and I have plenty of clients who come back for more business.

      Bob

    50. Re:css!! by brunogirin · · Score: 1
      Yes and no. The best way to do it I reckon is to start by building a standard compliant CSS and test it with standard compliant browsers (Firefox, Safari, etc).

      Then when it completely works on those, test on IE and for the parts that don't work on IE, use one of the many well known hacks that will provide IE with different values. The best hacks make use of tag selectors that either only IE understands (because IE has embraced and extended the specs) or only IE doesn't understand (because IE doesn't implement the specs fully). Then you can isolate IE specific code.

      Doing it this way, you promote the use of standard compliant browsers because you design primarily for them and it will work in all of them. but at the same time, you cater for the vast majority of IE users.

      For more information on suck hacks, go and see sites like A List Apart.

      You might argue that it is a pain to have to add IE specific hacks but don't forget that HTML/CSS is not meant to provide exact layout. So if something looks slightly different in different browsers but is usable, don't bother with a hack, just leave it as is. If your layout is flexible enough, this should be what happens most of the time.

    51. Re:css!! by mrchaotica · · Score: 1, Offtopic
      1. I don't watch the Fox News Channel, ever. In fact, I do my best to avoid the useless American media altogether.
      2. Illegal immigrants are, by definition, illegal! If anyone else breaks the law, what do we do? Obviously, we punish them. We should do the same for illegal immigrants, because they are all criminals. Besides, if they have no respect for our immigration laws, what makes you think they respect any of our other laws? Come to think of it, they don't care about our traffic laws either -- that's why they never got insurance! Here's the bottom line: if the immigrants love our country so much they want to move here, then they should also respect it enough to obey the law!
      3. If, on the other hand we want to let them stay here anyway, then we ought to change the immigration laws so that they won't be illegal anymore. It's asinine that we would give them some kinds of documentation and not others, and it's even more asinine that they get the privilages of driving, school for their kids, etc. without having to pay taxes like any other (documented, legal) resident would!
      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    52. Re:css!! by CowboyBob500 · · Score: 1

      Surprise normally - most assume IE would be the easier to develop for since its the most common.

      Bob

    53. Re:css!! by Ubergrendle · · Score: 2, Funny

      Nah, we're all still on Mosaic. Slashdot is the only site we can still visit coincidentally, and the lack of flash support means we don't have to read MS adverts ontop of Linux articles.

      --
      John Maynard Keynes: "When the facts change, I change my mind. What do you do?"
    54. Re:css!! by a11 · · Score: 0

      well, you're a fucking loser. you're not funny, yet choose to ramble on and on without being funny or making a point of any sorts. you're probably quite overweight. quite likely a real ugly mofo whose girlfriend doesn't suck a good dick or shave in the proper places. you have a certain lack of social skills but pride yourself in your latest cool gadgets from cdw. Sometimes I think I am the only compsci geek on the planet who has a date w/ a hot girl on saturday night and can get into the top nightclubs w/o standing in line. and I still write better code than you dumbasses. I am freaking amazing - what a catch. and quite a fucking loser you are indeed. go code yourself a personality. it would have to be in vb in your case.

    55. Re:css!! by labyrinth · · Score: 1

      Agreed, except that instead of using IE-specific tag selectors I prefer conditional comments. That way, if the next version if IE breaks your hacks, it is easier to see where they are, and to change them so they work only in the IE versions for which they apply.
      My experience is that only a small number of these are necessary in what you typically want to use in a website, and you only have to figure them out once.

    56. Re:css!! by Taladar · · Score: 1

      No, it should not be fixed. Those things are good reasons for switching to a compliant browser.

    57. Re:css!! by Fatalis · · Score: 1

      His "theory" makes more sense than your sarcasm, because developing with standards in mind does not rule out making it work in outdated browsers like IE. It means developing "for all browsers" and avoiding to use proprietary features where possible. It means providing fallbacks and enabling graceful degradation, and making the code future-proof. It does not mean not developing for any browser, as you're so subtly implying.

      --
      Deus est fatalis
    58. Re:css!! by Pfhreakaz0id · · Score: 1

      sorry. Misunderstood your point. I thought you charged EXTRA for the ie compatibility over the standards version.

      I agree, from my old days of dooing such freelance work that clients are happier with an itemized bill versus "45 hours programming/design @ $xx per hour"

    59. Re:css!! by Evil+Grinn · · Score: 1

      The "design for all browsers" paradigm isn't a good one.

      Not to mention that no one really does it anyway. What most people/companies have time to do is to design for "both" browsers, with the definition of "both" changing over the years: Mosaic and Netscape, IE and Netscape, IE and Mozilla, etc.

    60. Re:css!! by dtfinch · · Score: 1

      I subscribe to the "two party system" duality paradigm whereby most competitive markets evolve into primarily a two horse race and just make sure my pages work in the top two browser engines, IE and Gecko. I'll usually try some pages in Konqueror and Opera, but sometimes it's only after the site has gone live, and I usually don't encounter serious problems. Most of my active development goes on in FireFox, except for HTA applications which are IE only, though I've been experimenting with XUL-Runner for making cross platform HTML apps.

    61. Re:css!! by calyphus · · Score: 1
      ...it's even more asinine that they get the privilages of driving, school for their kids, etc. without having to pay taxes like any other (documented, legal) resident would!
      Hmm, how do these illegals avoid paying taxes? Sales taxes are unavoidable. Property taxes are collected either indirectly by a landlord or directly under threat of foreclosure. Income withholdings are made by employers (even if the alien provides bogus SSN info, the g'ment still gets its cut). Most illegals work with the appearance of legitimacy. There certainly are those working for wages 'under the table,' but they are the minority and still have to pay the use and possession taxes.
      --


      The potato it is uninformed.
    62. Re:css!! by elemental23 · · Score: 1
      Nope, check their doctype declaration:
      <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
                  "http://www.w3.org/TR/html4/strict.dtd">
      --
      I like my women like my coffee... pale and bitter.
    63. Re:css!! by elemental23 · · Score: 1

      If, on the other hand we want to let them stay here anyway, then we ought to change the immigration laws so that they won't be illegal anymore.

      Fixing our immigration laws is much easier said than done. Large, sweeping changes seem to scare an awful lot of people, which translates into lost votes and changes that aren't ever implemented.

      Because the underlying problem (illegal immigration) can't be fixed this easily, smaller changes that can reduce related problems (unlicensed, uninsured driving) can be helpful in the interim. Illegal immigrants are going to drive, period. We should do what we can to help as many as possible do it legally.

      --
      I like my women like my coffee... pale and bitter.
    64. Re:css!! by Anonymous Coward · · Score: 0

      Validation Error:
      1042. No opening tag specified.

      Line 6: [/sarcasm]
      -------^

    65. Re:css!! by Anonymous Coward · · Score: 0

      The XHTML and CSS aren't even standards compliant. Pffft.

    66. Re:css!! by jonadab · · Score: 2, Insightful

      > No, you should design for standards, and then sit back and relax. Let it
      > look suboptimal in non-compliant browsers; it'll give them incentive to
      > upgrade.

      I take an approach that's sort of a compromise between these positions. First, I design the site using documentation that's based on standards (e.g., the XHTML and CSS documentation at w3schools.com is mostly pretty decent). Then I validate it at validator.w3.org. Then I test it in several web browsers and make sure it adheres to the following:

      First, the site should look basically the way I intended it to look in recent versions of Gecko at resolutions from 640x480 through 1600x1200, at 24 bits per pixel. This generally is not a problem.

      Second, the site should look reasonable (not necessarily exactly as intended) in the latest version of every major browser that I have at my disposal, at resolutions from 320x200 through 2560x2048, at 16 bits per pixel and higher. (I try to keep a copy of the latest at my disposal for this testing, even though it's usually the hardest one to please, because it's so widely deployed.) The definition of "reasonable" fluxes a little depending on how important aesthetics are to the site and how important the site is to me. Images are allowed to be ugly at 16bpp.

      The site must be legible and navigable (i.e., the text can be read and the links can be followed) in all browsers, including really old and crufty and horrible ones, even at very low resolutions, and in 16-color mode (4bpp), and in 256-shade greyscale. It's allowed to look suboptimal, even very suboptimal, but it should be usable. This usually is not a problem with well-designed sites.

      I do not attempt to support 1-bit color. Sorry, not going there.

      --
      Cut that out, or I will ship you to Norilsk in a box.
    67. Re:css!! by nmg196 · · Score: 1

      > No, you should design for standards, and then sit back and relax.
      > Let it look suboptimal in non-compliant browsers; it'll give them
      > incentive to upgrade.

      Yeah, because users will then think: "ooh - this site looks shit compared to all the others. It must be my browser's poor support of standards. I'll go upgrade right now."

      Or are they more likely to think "this site looks shit compared to all the others. They obviously have crap web developers." [user navigates elsewhere]

      I wonder which is more likely? (Clue: the latter)

      Don't take a job as a web developer (please).

    68. Re:css!! by eihab · · Score: 1

      Sure, sit back and relax and don't get paid!

      I'm a freelancer, and none of my clients even consider paying me if their website doesn't display correctly on IE. Why? They believe IE is the ONLY browser, they believe Windows is the ONLY OS.

      I have a hard time explaining to clients why we can't just create the whole thing with flash, or why flash intros is a bad idea (they still request it anyway), or why oh why they can't put that amazing 3D presentation that they have on a CD on their website.

      Not everyone who wants a website knows how it should be designed, they usually see something that they like (and you won't believe the crap they like) and say they want something like it.

      Apart from website owners you have users, do you think that when a user sees your website broken he'd think (no matter what you tell him) that IE is bad? GOD FORBIDS!

      He'll just move away and take his business, ads clicks/views somewhere else and curse the dumb-ass who created that site.

      My solution? nothing. I try my best to educate business owners, try my best to design for standards and fix IE bugs, and most of all try to avoid client side projects and look for more server side stuff.

      The web as it is disgusts me...

      --
      If you can't mod them join them.
    69. Re:css!! by Sancho · · Score: 1

      I think it's less likely that they'll upgrade and more likely that they'll stop visiting your site, thinking it broken.

      Remember, most IE users don't realize that there are other options and probably don't care.

    70. Re:css!! by Anonymous Coward · · Score: 1, Insightful

      Of course if you designed for IE first then detailed what it would cost to make it work on the less popular browsers - very few customers would actually pay for non-IE support.

      If your customers only care about IE you are doing the wrong thing and costing them more by designing for 'standards' (which are only one group's perception of the standard) instead of IE which, frankly, is the most popular standard.

    71. Re:css!! by horza · · Score: 1

      Right, so the intelligent thing would be to explain to my clients that it's Microsoft's fault and not mine that the site I just designed for them doesn't display properly for 9 out of 10 of their customers? After all, I followed the standards and it would be stupid not to!

      Correct. And then you do as you mention below in your post and bill the client accordingly.

      "Sorry Mr. Client, standards evangelism is far more important to me than your customers. Now, when should I be expecting payment?" Yeah, that'll fly.

      Or you could talk to them like intelligent people. The appalling standard of Microsoft software is well known in the business world.

      I think I'll keep using my current methodology: Design to the standards first, then add whatever hacks are needed to handle the various browser bugs in secondary stylesheets to ensure the widest possible compatability across as many browsers and platforms as I can.

      There are numerous hacks, such as the great IE 7 hack, but these only plaster over the problem.

      Call me crazy, but keeping the client and their customers satisfied (and, as a result, making the site display properly for as many visitors as I possibly can, rather than just those that use a "standards compliant" browser) and subsequently getting paid for my work is more important to me than beating the standards drum.

      I mentioned in a previous post how I spent weeks converting this website with property in nice, france to pure CSS. Take a look in IE and Firefox and you will see there are still a few glitches in IE. It's just not worth my clients time paying to fix them and so they will stay. Works fine in Opera. Fixing cross-browser problems hits the laws of diminishing returns, where you spend a disproportionate time fixing more and more minor IE glitches that are totally unpredictable.

      Phillip.

    72. Re:css!! by damiam · · Score: 1
      designing web sites for broken browsers is like giving illegal immigrants drivers' licenses

      The difference being that illegal immigrants don't make up 95% of the population.

      (Unless you consider all non-Native American people in the US to be illegal immigrants, which could be argued for but probably isn't what you're talking about.)

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    73. Re:css!! by Anonymous Coward · · Score: 0

      Yea, and I'm guessing you just make sites for friends and family. Try pulling that in a coporate enviroment and you'll have a hard time trying to make money.

    74. Re:css!! by seriesrover · · Score: 1
      However the majority of your clients customers do not know about standards compliant - they barely have even heard of HTML. What they will see is a broken Real Estate website in a sea of Real Estate websites that aren't.

      You can go on all day talking about how crap IE is, but here's the bottom line - it matters to you, but it doesn't matter to the people that it matters to.

    75. Re:css!! by Anonymous Coward · · Score: 0

      Or the (totally non-technical) client says: Look how crap this looks! Why should we do any further business with you? You try to explain to them that it is their browser, but as far as they are concerned IE is _the_ standard so your words fall on deaf ears...

      The same thing happens when you develop for mobile devices. You say: It is a bug in the firmware (and it really is). All the client sees is your "crappy" app not working correctly...

    76. Re:css!! by Generic+Guy · · Score: 1
      If your customers only care about IE you are doing the wrong thing and costing them more by designing for 'standards' (which are only one group's perception of the standard) instead of IE which, frankly, is the most popular standard.

      IE has been slipping in popularity, especially now that Opera and others have stopped reporting themselves as IE.

      As Microsoft is more likely than anyone to change how their next revision handles displaying web content, his billing method strikes me as quite brilliant. Under this method, his method is more likely to work in the future especially as popularity of other browsers (even among Microsoft's own revisions) shifts. And its easy to come in and re-bill for new features bif it becomes necessary.

      On the other hand, your method of programming to one application is highly likely to break in the future. Its almost like you expect recurring business on the basis of continually "fixing" your clients' code. Either that, or you are simply a hack who slaps enough barely enough code together to work only under a narrowly defined environment. Not a good way to bolster a reputation. I noticed you posted this AC. Worried about your karma, are you?

      --
      { - Generic Guy - }
    77. Re:css!! by Hes+Nikke · · Score: 1

      quoting from my post above:
      and don't want to bother to "fix" it for IE.

      so... no comment. :P

      --
      Don't call me back. Give me a call back. Bye. So yeah. But bye our, well, but alright we are on a shirt this chill.
    78. Re:css!! by dhasenan · · Score: 1

      Look, we actually want people to look at our sites. Otherwise we'd use Intercal rather than HTML. We don't want to exclude a portion of our potential viewers that could range from perhaps 10% to 95% (usually no less than 80% for non-technical sites, I'd guess). Therefore, we accept IE quirks as well as W3C standards.

      I just launched a tiny site, tested mainly with Firefox during development. It validates with the W3C validator and renders just fine with every browser I've checked with--except IE (which spreads the navigation bar out).

      The more I work with it, the more I realize that IE's just a bitch when it comes to CSS. I'm just going to get something that renders decently in IE and then quit. It's not worth it, wondering why my width: auto tag expands something to the widest possible width, or why I can't position something accurately in IE without displacing it in Firefox.

  3. Will the beta bring the site down? by geomon · · Score: 4, Interesting

    Just about every site remodel has problems. I have just gone over the list of things I have issues with on our local public school's new website. Most of my comments have to do with broken capabilites. I'm sure that the folks at /. have tested this system in a non-production environment, but things are bound to go wrong at first. The unfortunate thing about my local school district's website has been access. How much of the /. staff resources are going to be committed to the rollout and how soon are problems going to be addressed?

    Considering the fact that it took nearly two minutes for the form to arrive makes me think we are in for a bumpy ride!

    --
    "Rocky Rococo, at your cervix!"
    1. Re:Will the beta bring the site down? by mspohr · · Score: 2, Funny

      It looks like /. has been slashdotted (slashdotti?).

      --
      I don't read your sig. Why are you reading mine?
    2. Re:Will the beta bring the site down? by liam193 · · Score: 4, Funny

      Slashcode has been slashdotted!

      For all those wishing to read the original article, the contents have been replicated in a modified format here.

    3. Re:Will the beta bring the site down? by Anonymous Coward · · Score: 0
    4. Re:Will the beta bring the site down? by malachid69 · · Score: 1

      Yeah, it appears so.

      About 1/5th of my requests actually make it to load a page.

      Then I notice things like text overlapping the icons at http://www.slashcode.com/comments.pl

      I couldn't really do a valid comparison since I couldn't get it to list any stories or anything.

      --
      http://www.google.com/profiles/malachid
    5. Re:Will the beta bring the site down? by stevey · · Score: 1

      It is a shame that slashcode doesn't seem to update its website very often.

      e.g. Googles cache of the front page shows the most recent front-page story dated December 20th 2004!

      A while back I was looking for a CMS to run a slashdot-like site, and whilst I was pretty sure I'd not need the complexity of the full slash codebase I decided not to use it partially on the grounds that the slashcode website looked so "dead".

      (I'm sure that the CVS repository, and mailing lists are alive; but it's not a thing to instill confidence in potential adoptors).

    6. Re:Will the beta bring the site down? by Martin+Blank · · Score: 1

      Will the beta bring the site down?

      Considering how often I get 503 errors, it may not make much difference. At least with a redesign, outages will be attributable to them visibly working on one of Slashdot's biggest flaws.

      --
      You can never go home again... but I guess you can shop there.
  4. Oh My God, It's Actually Happening! by AKAImBatman · · Score: 5, Interesting

    CmdrTaco? I have exactly two words for you.

    This. Rocks.

    Kudos on finally bringing Slashcode into the 21st century! The Slashdot style over on Slashcode looks absolutely wonderful, with none of the chunky layout problems that plague Slashdot itself! What I'd love to know is, how much bandwidth are you saving by using CSS? Many of the experiments done to date suggest that you could cut your bandwith usage by 30-50%! Will this update usher in a new era of faster page loading? Inquiring minds want to know! :-)

    1. Re:Oh My God, It's Actually Happening! by fshalor · · Score: 2, Funny

      It's also slashdoted...

      LOL!!!

      I love this site. hehe...

      --
      -=fshalor ::this post not spellchecked. move along::
    2. Re:Oh My God, It's Actually Happening! by Crazy+Man+on+Fire · · Score: 3, Funny

      Considering the fact that the Slashcode servers are now a pile of smoldering ash, I'm guessing they haven't saved much bandwidth

    3. Re:Oh My God, It's Actually Happening! by jpostel · · Score: 4, Funny

      CmdrTaco - "Do you smell something?"

      CowboyNeal - "Oh Sh*t! The slashcode server's on fire!"

      ROFL

      --
      Ummm, Jon, aren't you supposed to be dead...? - Otter(3800)
    4. Re:Oh My God, It's Actually Happening! by Malc · · Score: 2, Funny

      You would think Cmdr Taco would know enough about the /. effect that he wouldn't inflict it upon his own servers. He must be some kind of masochist!

    5. Re:Oh My God, It's Actually Happening! by Anonymous Coward · · Score: 0

      He designed Slashcode. You had a doubt?

    6. Re:Oh My God, It's Actually Happening! by JasonUCF · · Score: 5, Insightful

      So I'm going to be modded as flamebait here but um, honestly, "This Rocks"? My first reaction is, ABOUT GODAMNED TIME?

      I mean, couldn't they have found any time in the past 8 years of triple posting the same article, not performing any due diligence regarding fact checking, etc... to fucking fix their html???

      Thanks Rob Malda et all, welcome to the 21st century!

      Mod me down, but you know it's true.

    7. Re:Oh My God, It's Actually Happening! by sootman · · Score: 5, Funny

      No WML. Less styles than CSS Zen Garden. Lame.

      --
      Dear Slashdot: next time you want to mess with the site, add a rich-text editor for comments.
    8. Re:Oh My God, It's Actually Happening! by XO · · Score: 2, Informative

      apparently slashcode is so incredibly bad spaghetti that it has taken this long to actually work with it. blargh.

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
    9. Re:Oh My God, It's Actually Happening! by Seanasy · · Score: 2

      Don't get too excited.

      HTML just wants to be valid. Is that so wrong?

      And why not go for XHTML Strict, or even Transitional?

    10. Re:Oh My God, It's Actually Happening! by adpowers · · Score: 1

      Yeah, really. Now, do you think this means we'll see PNG images five years from now?

    11. Re:Oh My God, It's Actually Happening! by tgd · · Score: 5, Funny

      *one day passes*

      Zonk - "Oh Sh*t! The slashcode server's on fire!"

    12. Re:Oh My God, It's Actually Happening! by Linurati · · Score: 1

      Use http://validator.w3.org/.

      I just ran it against the page and it returned some errors, such as the invalid attribute "language" in a JavaScript block (only type="text/javascript" is required. There are a few others. Not many, but a few. Most of them were due to the login links, so maybe some symbols have to be replaced with their equivalents, such as changing & to &.

      It does look good, though. :o)

      --
      Milo
    13. Re:Oh My God, It's Actually Happening! by JasonUCF · · Score: 1

      HA HA! OH my god this couldn't be funnier...

      So, I totally expected this comment to be -1'd into the floor. But to my surprise, the comment actually rocketed to +5 with a Karma+1, and 4 points of Informative/Insightful allong with a -1 Flamebait.

      The :5 stayed for awhile until.. DUN DUN DUN!!! A /. editor got a little upset with my post.

      Check it out now. Karma bonus is gone. Flamebait , strangely enough, is also gone. Now try to make sense of a +2 post that has a 30% Int / 20% Insightful / 20% informative. Explain THAT math to me.

      Nice to see how thick the skin is guys. Way to metamod.

    14. Re:Oh My God, It's Actually Happening! by catalax · · Score: 1

      As far as i can see, the error result from an article text, not directly from the newtemplates. While slashdot limits the allowed tags, there shouldn't be a problem over here.

      XHTML Transitional, btw., is like buying a car that probably has 4 tires, but rather 3 or only 2. You should always stay standards compliant: use Strict.

    15. Re:Oh My God, It's Actually Happening! by ModernGeek · · Score: 1

      Someone got modded up that said ROFL.

      Lets try it

      LOL ROFL :) :X :* *MSN MESSENGER WINK HERE*

      So, cmdrTaco, when are you going to let us have emotions and these winks all the kids on MSN are talking about?

      --
      Sig: I stole this sig.
    16. Re:Oh My God, It's Actually Happening! by tf23 · · Score: 1

      Here's some details about the slashcss conversion.

      I think some of what you're asking about is answered in that.

    17. Re:Oh My God, It's Actually Happening! by rinkjustice · · Score: 1

      "Mod me down" posts always seem to get modded up. Is this some kinda reverse psychology or something?

    18. Re:Oh My God, It's Actually Happening! by Accipiter · · Score: 1

      Kudos on finally bringing Slashcode into the 21st century!

      Hardly. Moving to HTML 4.01 is like just now getting around to upgrading from Windows 95 to Windows 98.

      --

      -- Give him Head? Be a Beacon?
      (If you can't figure out how to E-Mail me, Don't. :P)

    19. Re:Oh My God, It's Actually Happening! by TheGorilla · · Score: 0

      Slashdot was originally designed as a secret government tool to destroy undesired websites.

      Shortly after it's inception Commander Taco sieged the government offices, after many months the government raised the white flag (he isn't called Commander taco for nothing).

      It's nice to see that we have finally reverse engineered the government html and are ready to add CSS.

      Long live the rebellion!

    20. Re:Oh My God, It's Actually Happening! by commonchaos · · Score: 1

      Thanks for making my day!

    21. Re:Oh My God, It's Actually Happening! by sik0fewl · · Score: 1

      *one day passes*

      Zonk - "Oh Sh*t! The slashcode server's on fire!"

      --
      I remember when legal used to mean lawful, now it means some kind of loophole. - Leo Kessler
    22. Re:Oh My God, It's Actually Happening! by Anonymous Coward · · Score: 0

      It's posts like this which demonstrate a score of +5 is still not high enough.

    23. Re:Oh My God, It's Actually Happening! by Morden · · Score: 1

      Then two days pass and Timothy reposts a story about it.

    24. Re:Oh My God, It's Actually Happening! by __aailob1448 · · Score: 1

      Funniest Slashdot joke ever!

    25. Re:Oh My God, It's Actually Happening! by gottabeme · · Score: 1

      Well, mod me down, but exactly how large a rock have you been living under? :)

      --
      "Those who consume the bulk of goods are those who make them. We must never forget this secret of our prosperity."
    26. Re:Oh My God, It's Actually Happening! by JasonUCF · · Score: 1

      Replying to myself replying to myself, just to say I'm not crazy, and that it looks like people bumped it back up, and, well, woa! Still no karma tho. Slashdot users speaking the truth FTW!~! p.s. the css looks kinda good! woo hoo

  5. Maybe adding a little JS ... by TeXMaster · · Score: 5, Interesting

    for things like collapsing articles to header only and expanding them to full article? (And user options for the initial view)

    --
    "I'm never quite so stupid as when I'm being smart" (Linus van Pelt)
    1. Re:Maybe adding a little JS ... by value_added · · Score: 1

      for things like collapsing articles to header only and expanding them to full article? (And user options for the initial view)

      So ... you're looking for a usenet experience with proper threading, but with clicky links and pictures, and inside a browser, right?

      I've got a better idea. Since the text thing is so 1980s, maybe we can do a Google Groups version, too. That way, those readers who want to use their browser can still do so and get better threading, and the rest of us can access it as a news feed through Gmane. Being able to read /. in mutt *and* get syntax hilighting for any HTML formatted posts -- now, that's something for the suggestion box!

      Ok, maybe not.

    2. Re:Maybe adding a little JS ... by se7en11 · · Score: 1

      in the mean time you may want to try the FireFox extension Greasemonkey.

    3. Re:Maybe adding a little JS ... by Anonymous Coward · · Score: 0

      Yah and add lots of flash and BLINK TAGS! everyone loves BLINK TAGS!!!

      why is it that people get their jollies on eye-candy when having content over style is way more important.

      I prefer a plain html with nothing added (not even a changed background color and gobs of content I can use over some asshat's desire to be a graphic artist any day.

    4. Re:Maybe adding a little JS ... by jzono1 · · Score: 1

      no need for js. firefox can do that with pure css

    5. Re:Maybe adding a little JS ... by b100dian · · Score: 1

      More exactly: http://www.allpeers.com/blog/?p=137 (Slashdot Livecomment Tree).
      Hopefully will be updated when the new SlashCode arrives:)

      --
      gtkaml.org
    6. Re:Maybe adding a little JS ... by aug24 · · Score: 1

      Colour me stupid, but how does firefox enable collapsing divs without JS? I'd really like to know - I could use that capability in my current project!

      Cheers,
      J.

      --
      You're only jealous cos the little penguins are talking to me.
    7. Re:Maybe adding a little JS ... by IpalindromeI · · Score: 1

      I don't know of a way to make permanently expanded (or collapsed) divs, but you can do it on mouseover with :hover.

      <html>
        <head>
          <style type="text/css">
            .b {
              display: none;
              border: 1px red solid;
            }
            /* the key   |
                         V       */
            [class="a"]:hover .b {
              display: block;
            }
          </style>
        </head>
        <body>
          <div class="a">
            Move mouse here for a surprise!
            <div class="b">
              Ta da!
            </div>
          </div>
        </body>
      </html>

      --

      --
      Promoting critical thinking since 1994.
    8. Re:Maybe adding a little JS ... by aug24 · · Score: 1

      Thanks for that, much appreciated. That (with some clever xslt) should make my current task much easier. I guess that's one reason they're called *cascading* style sheets ;-)

      J.

      --
      You're only jealous cos the little penguins are talking to me.
    9. Re:Maybe adding a little JS ... by aug24 · · Score: 1

      Damn, so close! It appears hover will only effect child divs, not siblings. Back to the DOM walk I think. J.

      --
      You're only jealous cos the little penguins are talking to me.
    10. Re:Maybe adding a little JS ... by IpalindromeI · · Score: 1

      You can do siblings, but only immediately adjacent siblings, and the style can only affect the second. It would be tough to make this work with multiple levels, but may be possible depending on your layout.

      <html>
        <head>
          <style type="text/css">
            .a {
              border: 1px solid red;
            }
            .b {
              display: none;
              border: 1px solid green;
            }
            [class="a"]:hover + .b,
            [class="b"]:hover {
              display: block;
            }
          </style>
        </head>
        <body>
          <div class="a">
            One
          </div>
          <div class="b">
            Two
          </div>
        </body>
      </html>

      --

      --
      Promoting critical thinking since 1994.
    11. Re:Maybe adding a little JS ... by aug24 · · Score: 1

      Thanks, I'll give this a try tomorrow (at work). Time to watch Lost now ;-)

      J.

      --
      You're only jealous cos the little penguins are talking to me.
    12. Re:Maybe adding a little JS ... by aug24 · · Score: 1

      Amazing the things I never knew. "The Adjacent-Sibling Selector" eh?

      Thanks, that should just about do it ;-)
      J.

      --
      You're only jealous cos the little penguins are talking to me.
  6. No logon by liam193 · · Score: 2, Informative

    Is there a separate user database for slashcode? Logon doesn't seem to work and even a "send my password" doesn't recognize the login id. Perhaps this is just a Beta/Test issue, but it would be nice to test with real-world configurations and customizations.

    1. Re:No logon by WalksOnDirt · · Score: 2, Funny

      Sounds like the Slashdot main page got hacked, adding this artcle with a link to harvest Slashdot logins. B-)

      --
      a,e,i,o,u and sometimes w and y (at be if of up cwm by)
    2. Re:No logon by Dave2+Wickham · · Score: 1

      As Slashcode is just the CMS which Slashdot uses (well, created), yes, the databases are different. The Slashcode site is designed for articles about slashcode itself (and appears to be on a separate server), whilst slashdot is - well - slashdot.

  7. 500 Internal Server Error by Anonymous Coward · · Score: 0

    Noooo. You killed slashcode.

    Anyone have a cache?

  8. The apocalypse draws nigh. by funny-jack · · Score: 2, Funny

    from the oh-my-god-it's-actually-happening dept.

    You can say that again.

    --
    You probably shouldn't click this.
    1. Re:The apocalypse draws nigh. by aug24 · · Score: 2, Funny

      Oh my god it's actually happening!

      --
      You're only jealous cos the little penguins are talking to me.
    2. Re:The apocalypse draws nigh. by fbjon · · Score: 1

      Watch out, the CSS will contain: span.dnf {display: none; content: "base64;RHVrZSBOdWtlbSBGb3JldmVyOiBXaGVuIHRoZSBmcm 9udCBwYWdlIGlzIHN0YW5kYXJkcy1jb21wbGlhbnQu";}

      --
      True confidence comes not from realising you are as good as your peers, but that your peers are as bad as you are.
    3. Re:The apocalypse draws nigh. by b100dian · · Score: 1

      Duke.N.F!?? I think Longhorn is approaching!!

      --
      gtkaml.org
  9. OMFG by Anonymous Coward · · Score: 2, Funny

    Slashdot going to CSS? Has hell frozen over!? Windows gone GPL!? What's next?

    1. Re:OMFG by schon · · Score: 5, Funny

      Slashdot going to CSS? Has hell frozen over!? Windows gone GPL!? What's next?

      I'd answer, but I'm too busy trying to catch these damn flying pigs!

    2. Re:OMFG by FireFury03 · · Score: 1

      I'm hoping that we're going to see XHTML1.1 strict compliance on slashdot one day...

    3. Re:OMFG by Anonymous+Writer · · Score: 1

      Apple migrating to Intel and a multi-button mouse.

    4. Re:OMFG by ericdano · · Score: 1
      Baby steps......baby steps.....

      I mean, they've resisted for 8 years changing the format.....

      --
      It's either on the beat or off the beat, it's that easy.
      I moderate therefore I rule!
      --
    5. Re:OMFG by Chatterton · · Score: 1

      Yes, no problem... In a Duke Nukem Forever timeframe :D

      There is no great needs to go to XHTML 1.1. A good HTML 4.01 + CSS is all you need and is the latest standard like XHTML 1.1. There is no competition between the two, they have each their plus and minus.

    6. Re:OMFG by kernelfoobar · · Score: 1

      Ok, you take care of the pigs and I'll take care of some cows that decided to drop by...

      --
      Here we go again!
    7. Re:OMFG by isorox · · Score: 1

      I'd answer, but I'm too busy trying to catch these damn flying pigs!

      I assume that the pig's haven't porouted wings, but that they're in flying cars.

    8. Re:OMFG by EnsilZah · · Score: 1

      So they have flying bigs in Duke Nukem Forever?
      Good to know.
      How's the Phantom otherwise?

  10. XHTML by Anonymous Coward · · Score: 5, Interesting

    Just curious -- not attacking or anything -- but why HTML 4 as opposed to XHTML 1 Strict? Is it because of the content type issues with a certain browser, strict XML compliance was too difficult, or simply that only purists ever seem to care? ;-)

    1. Re:XHTML by schon · · Score: 3, Informative

      but why HTML 4 as opposed to XHTML 1 Strict?

      Here is a good list of reasons why HTML4 is preferable to XHTML.

    2. Re:XHTML by spongman · · Score: 4, Insightful

      that has to be the lamest excuse for a list of reasons why not to use something.

    3. Re:XHTML by Anonymous Coward · · Score: 0

      There is really only one good reason there: IE doesn't recognize application/xhtml+xml. The rest of the reasons aren't all that well thought out, especially the incremental page-rendering bullshit.

      Most notably, there is a good reason to use application/xhtml+xml if possible: you can actually validate the structure of a document against a DTD. This is a *good* thing in a web production environment.

    4. Re:XHTML by Anonymous Coward · · Score: 0
      Javascript document.write can't be used, it would need to be replaced by convoluted DOM methods.

      That's a bonus in my book, it's a pity xhtml allows embeded script at all.

      I serve as application/xml+xhtml to anything that advertises it in accept and text/html for broken UA's. Note that this isn't content negotiation, the document is XHTML, we're just hacking around bugs in substandard UA's.

    5. Re:XHTML by nateziarek · · Score: 2, Interesting

      I am sure Spartanicus is a web god that I don't know about and as such I will soon be eating my words (and in only like my 4th post here, no less!), but that wasn't really a list of reasons not to use xHTML. It was a rant against using xHTML just to use xHTML. I personally use xHTML because I never coded HTML4 "properly" and having my xHTML fail has taught me how to do things right. Yes, I could have created a custom DTD to validate my poor HTML4. That or use xHTML. Which is easier again?

    6. Re:XHTML by Spy+der+Mann · · Score: 1

      Well, the transition from html4 to xhtml isn't a difficult one. Let's wait until the CSS model is finished, and maybe then we'll start posting the xhtml feature request. I'm confident that it will take at most 1 year as opposed to 8...

    7. Re:XHTML by mstyne · · Score: 4, Funny

      Hey that guy has a website on the Internet he must be right

      --
      mstyne: real name, no gimmicks
    8. Re:XHTML by slcdb · · Score: 4, Interesting

      That is one of the most ridiculous articles on web authoring that I've ever read. The author's logic seems to mainly stem from the fact that IE has extremely poor standards compliance. Of course it has poor support for XHTML: when IE was last released (6.0) XHTML was still brand-new.

      This guy is seriously arguing that people should not adopt a now mature standard, because one aging piece of software hasn't been updated in four years? He just needs to get over his love affair with IE and realize that the rest of the world is still progressing.

      Addmitedly, I don't know when the article was written, but that's only because the author didn't date it. To argue that XHTML is bad because old UAs poorly support it is truly a case of the tail wagging the dog. I can hardly believe that the author doesn't understand that.

      --
      Despite what EULAs say, most software is sold, not licensed.
    9. Re:XHTML by Anonymous Coward · · Score: 0

      ...but you should acknowlege that the author has got a point. What we all get in more than 95% of the times is just HTML. It does not matter that the CONTENT of your page is valid XHTML; while the page is served as text/html, all browsers including firefox handle it as HTML and guess what, XHTML in this case is handled as a buggy HTML! Now, serve your page as application/xhtml+xml and you'll have problem with more than 85% of world that yet use IE!

    10. Re:XHTML by tolan-b · · Score: 1

      Oh yes, the very idea of supporting a little used browser like IE! I mean what was he thinking? Is he trying to tell us he has clients that need business or something? *guffaw*

      Latest IE still doesn't support XHTML properly.

      Ian Hickson agrees with him:

      http://www.hixie.ch/advocacy/xhtml

    11. Re:XHTML by Exaton · · Score: 1

      Typically conservative stance. It sickens me so much that I can't formulate a properly argumentative answer ; see sibling posts for that.

      You will die a slow and painful death. Meanwhile, those of us looking to the future are well aware of the current limitations in XHTML support, but we will pursue our efforts, knowing full well that its day will come. And much sooner than morons such as you seem to think.

      People, go read this extremely sensible presentation instead of the bullcrap above, and show it to your bosses.

      Thank you.

      P.S. to shon : it occurs to me as I see you five-digit Slashdot ID that you possibly posted that link quite objectively, without actually endorsing its preposterous libel. I sincerely hope that is the case.

    12. Re:XHTML by _bug_ · · Score: 1

      This guy is seriously arguing that people should not adopt a now mature standard, because one aging piece of software hasn't been updated in four years? He just needs to get over his love affair with IE and realize that the rest of the world is still progressing.

      IE 6 and earlier take up at least 80% of the user base on the 'net. So are you saying we should ignore them and focus on developing standards-compliant sites that aren't accessible to 80% of your user base?

      Or would you create a site that's standards-compliant and is still accessible to nearly 100% of your user base? How's that? HTML.

      XHTML is convoluted in its attempt to be backwards compatible with legacy clients. The extra XML tags needed to embed stylesheets or javascript in an XHTML 1.0 doc are ludicrous.

      XHTML 1.1 isn't as bad, but serving the document as text/html breaks the standard and breaks compliant XML applications from processing the content.

      XHTML 1.1 documents served under the correct mime-type are not readily accessible in IE 6 and earlier versions. You're asked where you want to save the file to rather than rendering the page.

      In the rush to use the latest "technology" you're leaving behind a lot of legacy systems.

      CSS is over.. what... 8 years old and only within the last couple years is it finally catching on. We've been waiting for old technology to die off (Netscape 4, IE 3) and now that you can consider those old browsers all but dead, we can start to take CSS seriously.

      XHTML won't be adopted en masse for probably another 8-10 years.

    13. Re:XHTML by Anonymous Coward · · Score: 0

      "Addmitedly, I don't know when the article was written, but that's only because the author didn't date it. "


      Last Modified: Tuesday, August 09, 2005 1:09:57 PM

    14. Re:XHTML by Bogtha · · Score: 1

      Actually, that's probably the best article I've read on the subject. You'd be a lot more convincing if you actually addressed the arguments it gives instead of simply calling it lame.

      --
      Bogtha Bogtha Bogtha
    15. Re:XHTML by Bogtha · · Score: 1

      This guy is seriously arguing that people should not adopt a now mature standard, because one aging piece of software hasn't been updated in four years?

      He's saying that you don't get any of the benefits of XHTML without serving it in such a way as to render it unusable to the user-agent that about 90% of people use. And without the benefits, there isn't any point in choosing it over HTML 4.01, which is also a mature specification.

      --
      Bogtha Bogtha Bogtha
    16. Re:XHTML by Carewolf · · Score: 1

      Is it a lame excuse that it is just inconvenient HTML, that happens to also be unsupported by 80% of the browser market (IE)?

    17. Re:XHTML by Fweeky · · Score: 0, Redundant

      Hixie said it best. Using HTML 4.01 Strict probably makes most purists *happier*.

    18. Re:XHTML by ZeroExistenZ · · Score: 2, Informative

      # Lot's of other sites use it, so it must be good.

      Lot's of Lemmings are jumping off cliffs, do you want to be a Lemming?


      Lemming suicide is fiction

      --
      I think we can keep recursing like this until someone returns 1
    19. Re:XHTML by maxume · · Score: 1

      He isn't arguing xhtml is bad. He is arguing that outputting xhtml is bad. Sure, IE6 is getting pretty old. In the real world though, its usage is still somewhere quite a bit north of 50% of all users. Ignoring 50% of the market for issues that are largely based upon technical purity is pretty silly. html4 and xhtml aren't really that different once they are in the browser. Sure, it is easier(possible?) to use all sorts of xml tools with xhtml, but if that is what you want, just render html4 at the end and ship that to your users.

      --
      Nerd rage is the funniest rage.
    20. Re:XHTML by Fweeky · · Score: 1

      Article looks perfectly reasonable to me.

      XHTML introduces all sorts of compatibility problems, many of which probably make most purists somewhat nervous. What it adds isn't very (at all?) useful in the vast majority of cases, even ignoring the levels of browser support. Just because it's newer doesn't mean it's better, or that you should use it over an older standard, especially when the newer one is little more than a reformulation of the old one in a new, mostly identical but subtly incompatible language.

      This isn't to say XHTML is bad, and that you shouldn't use it, but doing so just because it's newer and gives you fuzzy feelings inside isn't a great reason for favouring it.

    21. Re:XHTML by Bogtha · · Score: 1

      that wasn't really a list of reasons not to use xHTML. It was a rant against using xHTML just to use xHTML.

      Yes, but what you are missing is that the vast majority of people using XHTML are doing just that.

      I personally use xHTML because I never coded HTML4 "properly" and having my xHTML fail has taught me how to do things right. Yes, I could have created a custom DTD to validate my poor HTML4.

      You don't have to create a custom DTD just to validate HTML 4. You only have to create a custom DTD if you want to do things like require end tags for all element types. That's a requirement above and beyond that which HTML 4 requires.

      --
      Bogtha Bogtha Bogtha
    22. Re:XHTML by Tarqwak · · Score: 1

      If Mozilla coughs up the XML error page then I know I've screwed up some tags, quite handy and I don't have to use the validator.w3.org so often.

      The article in question brought one little detail to my attention though: proxies (the caching type). If Mozilla user comes through a proxy and fetches my application/xhtml+xml served XHTML 1.0 page then the page will be cached on the proxy. Now if a clueless MSIE 6.0 user requests the same page via that proxy then he/she gets the File Download dialog with Open Save Cancel buttons.

      So I use following if statement to decide what to serve:
      array_key_exists('HTTP_ACCEPT', $_SERVER) && stristr($_SERVER['HTTP_ACCEPT'], 'application/xhtml+xml') && !array_key_exists('HTTP_X_FORWARDED_FOR', $_SERVER) && !array_key_exists('HTTP_VIA', $_SERVER)

      I know about the request header Accept priority thing but practically it does not get used to demote XHTML AFAIK.

    23. Re:XHTML by Stalin · · Score: 1

      I would assume it is because this site has no need of XML buried in the HTML. The only reason to use XHTML over HTML 4 is the ability to embed XML technologies like MathML into the document. A really good explanation can be found at http://xrl.us/ba4c as to why not to use XHTML. It really doesn't make any sense to use XHTML, if you want to be completely strict, because it won't work right with a majority of browsers; not just the nameless one.



      It all boils down to the fact that /. publishes content where HTML is the maximum requirement. There is no need to get complicated by throwing XML into the mix.



      At least, that is how I see it.

    24. Re:XHTML by wootest · · Score: 1

      The reasons may be lame, but the problems with correct MIME types and how they *break people's web browsers* (I am not *only* talking about IE) are real and not to be underestimated. Required reading: http://diveintomark.org/archives/2003/01/14/eddies _in_the_spacetime_continuum

      The real problem is how people are trying to morph XHTML 2.0 into The Perfect Markup Language. They also did that with HTML 3.0. Does anyone here use HTML 3.0? No, you use at least HTML 3.2, the *backwards compatible* one, that was put in place when people actually wanted to go forward and not listen to perfectionists bickering all day long. (However, you probably use HTML 4.01 or any of the XHTML versions. But that's not the point.)

      I'm not saying people shouldn't try to create a better markup language, but I am saying that the XHTML branch is the only branch of HTML that's still being developed, and it's not a wise decision to basically EOL a lot of the language. Some of the presentational HTML tags (the font tag, anyone?) deserved cutting. They're already deprecated, and CSS is way better for controlling stuff like that. These people are trying to throw out the br tag. Not deprecate it. Yank it. One of these days, wham, straight to the moon. If you ask me, that dog won't hunt, monsignore.

      And finally, I join the rest of you in welcoming the Slashdot adaptation of four year old practises. It's good to have you onboard.

    25. Re:XHTML by nateziarek · · Score: 1
      Yes, but what you are missing is that the vast majority of people using XHTML are doing just that.


      I'd like to see that study that verifies your assumption :-)

      Once again, for me, making sure to write with proper opening and closing tags just makes sense. It is the natural evolution of the code. The strictness helps to maintain consistancy across different browsers.

      In order to properly validate my properly nested and closed tags using HTML4, I would have had to create a custom DTD. Why would I do that when I could just use xHTML?

      I have to ask: are the people that are against xHTML also against using <em> instead of <i> and <strong> instead of <b>? HTML is all about defining the data; not formatting it. xHTML makes that more evident, and I think many hand coders appreciate that.

      that's my $2.50 (which used to be enough for a gallon of gas....)
    26. Re:XHTML by Bogtha · · Score: 1

      I'd like to see that study that verifies your assumption :-)

      Good point, but in my experience, whenever anybody is asked why they chose XHTML, it's almost always one of the reasons Spartanicus debunks in that article.

      Once again, for me, making sure to write with proper opening and closing tags just makes sense.

      What do you mean by "proper"? HTML 4 doesn't require closing tags for a lot of element types. Omitting them is just as "proper" as putting them in.

      It is the natural evolution of the code.

      I have no idea what you mean by that.

      In order to properly validate my properly nested and closed tags using HTML4, I would have had to create a custom DTD.

      No, you don't. HTML 4 already forbids nested elements (I assume you didn't really mean "tags"). All elements in HTML are closed, although some of them don't have to be closed by a tag. There's nothing improper about that.

      Why would I do that when I could just use xHTML?

      XHTML is still less compatible than HTML, even if you take into account Appendix C. Character encodings, for example.

      I have to ask: are the people that are against xHTML also against using <em> instead of <i> and <strong> instead of <b>?

      Why on earth would they be?

      HTML is all about defining the data; not formatting it. xHTML makes that more evident

      That's nonsense. XHTML 1.0 is functionally identical to HTML 4.01. I think you might have fallen for the popular misconception that XHTML is "more semantic", or uses CSS instead of <font>, etc. It's not true. XHTML 1.0 contains <font>, for example, and table layouts are just as valid with XHTML as they are with HTML.

      --
      Bogtha Bogtha Bogtha
    27. Re:XHTML by slcdb · · Score: 1
      And without the benefits, there isn't any point in choosing it over HTML 4.01, which is also a mature specification.
      So I should choose HTML 4.01 so that when the HTML 5.0 spec is released, all of my content will be ready for it?

      Mmmmmkay.
      --
      Despite what EULAs say, most software is sold, not licensed.
    28. Re:XHTML by Bogtha · · Score: 1

      So I should choose HTML 4.01 so that when the HTML 5.0 spec is released, all of my content will be ready for it?

      I haven't got the foggiest what you are on about, sorry. Where did I say anything about HTML 5.0?

      --
      Bogtha Bogtha Bogtha
    29. Re:XHTML by slcdb · · Score: 1
      Is he trying to tell us he has clients that need business or something?
      IE doesn't support XHTML. But that doesn't mean that it can't handle XHTML. It actually handles it just fine: it treats it as HTML when served up as text/html. So his clients and their business will be just fine with XHTML, thank you.

      Sadly for his clients, when XHTML's day comes and HTML is relegated to the junk heap, they'll be spending a lot of extra time and money converting their dusty old HTML to XHTML. But they could have avoided it by just marking up their content in XHTML all the while.

      And Ian Hickson's argument is even worse than the original author's. Ian's argument boils down to this: you might run into trouble when you start serving XHTML, which you had previously been serving as text/html, as application/xhtml+xml. So, he argues, don't serve XHTML as text/html. Wow. Brilliant. That logic is so screwed up, that I can't even comment.
      --
      Despite what EULAs say, most software is sold, not licensed.
    30. Re:XHTML by slcdb · · Score: 1
      Where did I say anything about HTML 5.0?
      That's just it! You didn't! Because there never was a 5.0, there is not now a 5.0 and there never will be a 5.0. In other words, HTML is a dead-end standard. XHTML is the only path forward from there.

      So what do you think of this statement now:
      ... there isn't any point in choosing it [XHTML] over HTML 4.01, which is also a mature specification.
      They both give the same end result on current UAs. One has a future, one does not. Which makes the most sense to choose?
      --
      Despite what EULAs say, most software is sold, not licensed.
    31. Re:XHTML by nateziarek · · Score: 1

      I suppose you are correct to some extent that I've fallen into the HTML vs xHTML+CSS camp. I never used CSS before I started writing with xHTML and even though I know HTML is fully compatible with CSS, I never did think of it like that. So I will grant you that much prejudice on my part.

      I like all of my tags closed. It satisfies my logical center.

      Can I close all of my HTML tags, uh, elements with no errors? Absolutely.

      If I forget to close one of those and run it through the validator do I get any errors? Nope. Not without a custom DTD. For that reason alone I prefer xHTML.

      I agree that HTML is all about data structure, while the CSS should be about the layout. I just feel that xHTML takes it a step further by forcing (in my mind) a better standard. I'm not saying it is a huge leap, but it is something.

      The only metaphor I can think of - and it sucks - is writing.

      When I finish a sentence, I could very well add a dozen spaces before starting the next sentence. People would realize that one sentence had ended and another began. Instead we use endmarks (.?!). I just feel like the same sort of logic that applies there applies itself equally well to a mandatory closing of end tags.

    32. Re:XHTML by slcdb · · Score: 2, Insightful
      So are you saying we should ignore them and focus on developing standards-compliant sites that aren't accessible to 80% of your user base?
      No. I'm only saying that it's not wise to implore people to avoid using XHTML, which renders just fine in IE by the way, and instead use an older standard which has no future.

      Extra tags needed to embed scripts? Well, if that's just too much work for you, then stick with HTML. See how much work it is for you in "8-10 years" to convert all of your HTML content to XHTML (and I'm sure it will be sooner than you think). Or, you could just start using XHTML now.

      The meat of the original author's argument, that XHTML has no benefits over HTML when served as text/html, doesn't withstand even just a little scrutiny. It has the inherent benefit that it is the only path forward from HTML. There are other lesser benefits as well.
      --
      Despite what EULAs say, most software is sold, not licensed.
    33. Re:XHTML by Bogtha · · Score: 1

      Because there never was a 5.0, there is not now a 5.0 and there never will be a 5.0.

      The WHATWG intend to submit their work to the W3C, so there could well be an HTML 5.

      They both give the same end result on current UAs. One has a future, one does not.

      XHTML 1.0 has no future either. It will always be XHTML 1.0. Your documents won't magically upgrade themselves to XHTML 2.0 or whatever. Furthermore, user-agents won't stop supporting HTML for about a decade *.

      XHTML causes problems now. Today. And you are worrying about potential problems a decade from now? You're focusing on the wrong problem. Switching to XHTML before all major user-agents support it is premature optimisation.

      * Internet Explorer 6.0 is four years old, people are still using 5.5, 7.0 won't support XHTML. If 7.0 is released tomorrow, four years for everybody to upgrade to 7.0, and another four years for everybody to upgrade to 8.0, makes it about 2013 until we can stop supporting HTML, assuming Internet Explorer is the slowest major user-agent.

      --
      Bogtha Bogtha Bogtha
    34. Re:XHTML by Bogtha · · Score: 1

      If I forget to close one of those and run it through the validator do I get any errors? Nope. Not without a custom DTD. For that reason alone I prefer xHTML.

      But it's not an error in HTML. It's like considering an English essay wrong because it doesn't use question marks at the beginning and end of a sentence. Sure, it would be a mistake to omit the opening question mark in a Spanish essay, but that doesn't make the English essay any less right.

      You don't have to write your own custom DTD either. If you had followed the link in Spartanicus' article, you would see that there's one already written. All you have to do is point your validator to it.

      I agree that HTML is all about data structure, while the CSS should be about the layout. I just feel that xHTML takes it a step further by forcing (in my mind) a better standard.

      Like I just said, HTML vs XHTML has nothing whatsoever to do with structure versus layout. They are the same.

      --
      Bogtha Bogtha Bogtha
    35. Re:XHTML by nateziarek · · Score: 1
      But it's not an error in HTML


      and I think it should be. Since I can't change the HTML standard, I use xHTML.

      I fully understand your point (and excellent analogy, BTW). When I code, I prefer to close all of my tags. With xHTML all I have to do is validate. I don't have to find a custom DTD to validate with. I'm having a hard time understanding what is wrong with that. When I want some choclate ice cream I buy chocolate ice cream. I don't buy vanilla because "all I have to do is add chocolate."

      HTML vs XHTML has nothing whatsoever to do with structure versus layout


      I'm rereading my posts, but I don't think I said anything about that. I said that, for data structure (perhaps I should say "content"?), which is all HTML and xHTML should be, I prefer xHTML because it forces me to adhear to a set of rules that are slightly more strict than that of HTML.
    36. Re:XHTML by Bogtha · · Score: 1

      When I code, I prefer to close all of my tags. With xHTML all I have to do is validate. I don't have to find a custom DTD to validate with.

      Now you don't have to with HTML either, you've had one supplied for you.

      I'm having a hard time understanding what is wrong with that.

      Don't get me wrong, I have nothing against you wanting to close all your elements manually. But you can do that easily with HTML too. It's not as if using that custom DTD is difficult, is it?

      But there are real problems with XHTML. Things like being forced to use certain character encodings. Things like having the DOM change subtly. Or not being able to use some forms of Javascript.

      You can fix your toolset to make the HTML you write stricter. You can't fix browser incompatibilities, and you can't make XHTML do things like imply TBODY elements.

      XHTML is simply less compatible. If the two document formats were equally compatible, then sure, I'd pick XHTML too, for exactly the reasons you state. But they aren't.

      HTML vs XHTML has nothing whatsoever to do with structure versus layout

      I'm rereading my posts, but I don't think I said anything about that.

      That's how I read "I agree that HTML is all about data structure, while the CSS should be about the layout. I just feel that xHTML takes it a step further...".

      I said that, for data structure (perhaps I should say "content"?), which is all HTML and xHTML should be, I prefer xHTML because it forces me to adhear to a set of rules that are slightly more strict than that of HTML.

      The structure of HTML and XHTML documents are virtually identical. The syntax of XHTML is stricter. But syntax is easy. The content is a matter of structure, so I don't see how XHTML can help in any way with that.

      --
      Bogtha Bogtha Bogtha
    37. Re:XHTML by porneL · · Score: 1

      Unlike these guys on /. who know everything...

      First argument omits well-formedness requirement, but other are actually true.

      There are common misconceptions about XHTML. Like pride in making XHTML Transistional (take slashdot, add more slashes!) and sending it as text/html (surely HTML parser works better with cooler name and extra syntax errors!).

    38. Re:XHTML by Bogtha · · Score: 1

      So I use following if statement to decide what to serve: array_key_exists('HTTP_ACCEPT', $_SERVER) && stristr($_SERVER['HTTP_ACCEPT'], 'application/xhtml+xml') && !array_key_exists('HTTP_X_FORWARDED_FOR', $_SERVER) && !array_key_exists('HTTP_VIA', $_SERVER)

      No, that's still broken. Use the Vary header, that's what it's for.

      I know about the request header Accept priority thing but practically it does not get used to demote XHTML AFAIK.

      I've definitely seen it in the wild in a non-niche user-agent. If I remember correctly, older versions of Mozilla do this.

      --
      Bogtha Bogtha Bogtha
    39. Re:XHTML by Bogtha · · Score: 1

      People, go read this extremely sensible presentation instead of the bullcrap above, and show it to your bosses.

      Table layouts vs CSS layouts has nothing to do with HTML vs XHTML. You can have table layouts with XHMTL and CSS layouts with HTML, and vice versa.

      --
      Bogtha Bogtha Bogtha
    40. Re:XHTML by Bogtha · · Score: 1

      I am saying that the XHTML branch is the only branch of HTML that's still being developed

      That's not true.

      These people are trying to throw out the br tag. Not deprecate it. Yank it.

      Why not? If you need to separate content into individual lines, that's what the <l> element type is for.

      --
      Bogtha Bogtha Bogtha
    41. Re:XHTML by wootest · · Score: 1

      I know about what the WHATWG does, and I think it's good work in the right direction. However, I meant development of a new (X)HTML version -- WHATWG clearly defines their specs as extensions to existing such HTML versions and the DOM -- which only W3C deals with, and which I thought was painfully clear. Obviously I was mistaken.

      If you need to separate content into individual lines, that's what the <l> element type is for. Indeed. And if I need to style my text, that's what stylesheets are for. Better optimists than myself would doubt thinking even one third of the web is using stylesheets yet, and the CSS2 standard has been out for seven years now. Deprecating font tags and so on for CSS made sense, as it was a vastly better system, but switching one tag in favor of another which is just a different kind of tag is just change for change's sake.

      I'm okay with stuff being changed if it ends up improving the situation vastly. (The improved role of the object tag and the new section tag are both examples of this, and I salute them.) But I am not okay with aesthetic tweaks - changing an empty tag to a container tag for the hell of it, completely and needlessly throwing backwards-compatibility to the wind, and not by mistake, but *by intention*. Am I supposed to be happy that it'll still be there in a different shape? Am I supposed to rest assured that the capable hands are not even just raising the question of basically renaming tags for the hell of it, but actually doing it?

      (Some of you might drag up the argument of a smidge of added semantic purity. To which I will say that you are talking to someone that's all about semantic purity, but that this is more lunacy than anything else.)

    42. Re:XHTML by Bogtha · · Score: 1

      However, I meant development of a new (X)HTML version -- WHATWG clearly defines their specs as extensions to existing such HTML versions and the DOM -- which only W3C deals with, and which I thought was painfully clear. Obviously I was mistaken.

      The intention has always been that WHATWG will submit their work to the W3C once it is done, which could well result in HTML 5. The fact that the initial development is taking place outside of the W3C doesn't matter, a number of W3C recommendations have started out elsewhere.

      switching one tag in favor of another which is just a different kind of tag is just change for change's sake.

      No, it's not. There are sound reasons why well-designed markup languages use elements as containers and not processing instructions. For instance, you can't select individual lines in CSS when they are marked up with <br>, but you can with <l>.

      Either the <br> element is changed to <l> at some point, or we have to put up with it for eternity. As XHTML has been developed with the express intention that it not be backward-compatible, it's the ideal time to make a change such as this.

      But I am not okay with aesthetic tweaks - changing an empty tag to a container tag for the hell of it, completely and needlessly throwing backwards-compatibility to the wind

      If XHTML weren't already backwards-incompatible, then I'm sure that <br> would stick around. But you are talking as if XHTML would be backwards-compatible, and it's being thrown away for <l>'s sake. That's not the case. XHTML is already backwards-incompatible. They might as well take the opportunity to throw out the cruft while they can. Otherwise it'll still be haunting us decades from now.

      --
      Bogtha Bogtha Bogtha
    43. Re:XHTML by HeroreV · · Score: 1
      which renders just fine in IE by the way
      No it doesn't. IE can only render it as styled XML (no links, etc) or tag soup unless it uses XSLT to translate it into HTML. Don't blatantly lie.
      an older standard which has no future
      Ever heard of a thing called HTML 5? It's in the works whether you believe it is or not.
      See how much work it is for you in "8-10 years" to convert all of your HTML content to XHTML
      If you're coding valid HTML now, it's easy as pie.
      There are other lesser benefits as well.
      Like?
    44. Re:XHTML by wootest · · Score: 1

      The intention has always been that WHATWG will submit their work to the W3C once it is done, which could well result in HTML 5. The fact that the initial development is taking place outside of the W3C doesn't matter, a number of W3C recommendations have started out elsewhere.

      Good point, but in that case you could claim that HTML development inside W3C could never go stale. What I'm saying is that *inside the W3C, no work is currently being done on making a new backwards compatible version of HTML*, just XHTML 2.0. My point isn't that talented people can't submit new versions, my point is that there are people in W3C responsible for earlier versions of HTML, and that they should work on a new one instead of this. I think that the W3C should never *not* work on a new version.

      Look, I agree with what you're saying on semantics. You can match one line with CSS, for example, as a result of a good model. I am not against the model. It's a good model. However, I think it's lunacy to go with the ideal model in this case.

      Some people want XHTML 2.0 to be The Perfect Markup Language, by, like you say, "throwing out the cruft". I don't honestly think that it would be out before 2010 if it was, or that it could be that and still be HTML at all. And, as an effect of this, I'm also having a hard time seeing this standard ever getting widely implemented because the browsers that currently hold a 85%+ market share would have to go out of their way to support this explicitly and they haven't historically been any good with it. I'm not against a good markup language. I'm against it stealing attention from HTML for the time being, because I fear that at the end of the day, what's not HTML will remain a niche market in web browser support, just as proper XHTML handling is today.

    45. Re:XHTML by slcdb · · Score: 1
      No it doesn't. IE can only render it as styled XML (no links, etc) or tag soup unless it uses XSLT to translate it into HTML. Don't blatantly lie.
      CSS Zen Garden is a well-known website that uses XHTML (yes, the emphasis there is on CSS, but they use XHTML exclusively as well). There's also A List Apart and countless others which I won't bother linking to because you can easily find them if you google XHTML. Yes, I know they're sent to IE as text/html, but the markup is XHTML so don't bother arguing that. Ian Hickson already tried that and failed miserably.

      Also, there's no need to be an ass and call me a liar. Especially when you're wrong. You just made yourself look real stupid. Luckily for you, I'm probably the only one reading this.
      Ever heard of a thing called HTML 5? It's in the works whether you believe it is or not.
      Not that I'm calling you a liar, but I don't believe you. Please, if you're going to make claims like that, a link to the relevant standard (or draft) would be appropriate. And, no, the WHATWG's Web Applications 1.0 is not HTML 5.0. Yes, sometimes it is unofficially referred to as such, but it is not, as it's official name indicates. It is merely a group of extensions, but those extensions, if adopted, will apply equally to XHTML. So does that make it XHTML 3.0 or some other nonsense?
      If you're coding valid HTML now, it's easy as pie.
      That may be true if you have tools to convert case, add closing tags, quote all attributes, remove deprecated attributes, etc. But it's a whole lot easier if you code XHTML now. There's no denying that.
      Like?
      Some of the other replies to the original parent post mention other benefits (like stricter structure) and delve into the details. No need for me to duplicate here.
      --
      Despite what EULAs say, most software is sold, not licensed.
    46. Re:XHTML by slcdb · · Score: 1
      The WHATWG intend to submit their work to the W3C, so there could well be an HTML 5.
      More likely, any work that WHATWG does and is adopted, will be officially incorporated only into XHTML.
      XHTML 1.0 has no future either. It will always be XHTML 1.0.
      Uuuugghh. Ladies and gentlemen, this is Chewbacca. Chewbacca is a Wookiee from the planet Kashyyyk...
      XHTML causes problems now. Today.
      CSS Zen Garden is a great example of a site that uses XHTML exclusively. It works fine in all major current browsers, including IE, now. Today.

      Any problems people might encounter trying to upgrade their content to XHTML, are not problems with XHTML itself, but more likely problems stemming from the implementors not doing it right.
      Furthermore, user-agents won't stop supporting HTML for about a decade *.
      That may be. But all the major user-agents already support XHTML, so switching to XHTML is not, as you claim, "premature optimisation".
      --
      Despite what EULAs say, most software is sold, not licensed.
    47. Re:XHTML by ubernostrum · · Score: 1

      Of course it has poor support for XHTML: when IE was last released (6.0) XHTML was still brand-new.

      Consider these inconvenient facts:

      • The first working draft of XHTML 1.0 was made public in December of 1998.
      • XHTML 1.0 became a W3C Recommendation in January of 2000.
      • Internet Explorer 6 was released in October of 2001.
      • XHTML 1.0 did not introduce any new tags or attributes, and did not remove any tags or attributes; it is element-for-element identical to HTML 4.01.
      • Microsoft is a member of the W3C and had access to and input on every single draft of XHTML 1.0.

      Even if we decide to be generous and say that Microsoft's IE team couldn't take advantage of the working drafts of XHTML 1.0, that means that they had around twenty months in which to implement something that didn't involve any new tags or attributes, and on which they'd had been providing input and receiving constant updates for nearly three years previously. Would it really have been that hard?

    48. Re:XHTML by Exaton · · Score: 1

      Yes indeed, it is only after posting that I recalled that the first part of that presentation is about abolishing table layouts.

      Rapidly, however, from page 8 for instance, it veers on to semantical structure, and the ubiquitous separation of presentation and content.

      All very evident nowadays, of course...

    49. Re:XHTML by mike.newton · · Score: 1
      Just curious -- not attacking or anything -- but why HTML 4 as opposed to XHTML 1 Strict? Is it because of the content type issues with a certain browser, strict XML compliance was too difficult, or simply that only purists ever seem to care? ;-)
      I'd go with the last one, because XHTML 1.0 is "A Reformulation of HTML 4 in XML 1.0" Same elements, same attributes, almost the same syntax. The only big difference is that open elements have to be closed. For example, <br> becomes <br />; this is a bit of a hack, but that's another story. The famed Appendix C has a complete list of compatibility guidelines.

      (From a guy who's web pages are in XHTML, served as XHTML)
    50. Re:XHTML by HeroreV · · Score: 1
      but the markup is XHTML
      What's your point? Broken HTML that would qualify as XHTML if were sent as such is better than correct HTML?
      the WHATWG's Web Applications 1.0 is not HTML 5.0
      They want it to be, and it may eventually be. See the section on DOM Feature strings. In one place, they even refer to Web Applications 1.0 as HTML 5 several times. In any case, my point was that there are still people interested in HTML and that it is nowhere near dead.
      But it's a whole lot easier if you code XHTML now. There's no denying that.
      I deny that. It's just as easy to code valid HTML as it is to code valid XHTML.

      For me, working with XHTML and HTML has been the same for the most part. When a browser supports XHTML 2.0, I'll use it (whether that's horribly stupid or not) and then translating from XHTML to HTML and back may not be so easy, but for now I can do it without any trouble at all.
    51. Re:XHTML by Fweeky · · Score: 1

      IE only "supports" XHTML because it, like most other browsers, uses a tag-soup parser which even breaks standards HTML was originally based on. This isn't a good starting point for something that's supposed to be cleaner, especially when you get into the more complex issues associated with dual-mode XHTML-as-HTML/XHTML-as-XML. Makes it easier? Guffaw. All these sites which think they're using XHTML are in for a surprise when they try switching to XML mode and find half their JavaScript breaks, and that really, their CMS isn't that great at serializing well-formed XML. Sites which manage to do it properly may well get a cookie, but "easier" isn't something I think they're going to be touting.

      But don't mind me, I've only been doing this for 9 years, what do I know? Or Hixie for that matter, who the hell does that guy think he is?

      Thanks for playing Pointless Interwub Argument 4.5. Your turn.

    52. Re:XHTML by slcdb · · Score: 1
      Broken HTML that would qualify as XHTML if were sent as such is better than correct HTML?
      How is it broken HTML? The XHTML specification clearly states that valid XHTML may be labeled as "text/html". That does not mean it's "broken" HTML. User agents will interpret it that way (not that HTML user agents care about broken HTML, they have always happily accepted it). But the document itself is still valid XHTML.

      As for the point? The point is that your content is ready for the future -- and without any drawbacks if you know what you're doing.

      they even refer to Web Applications 1.0 as HTML 5 several times
      The funny thing, though, is that in all five places the "5.0" applies equally to content authored in XHTML. Does that mean that they are working on both HTML 5.0 and XHTML 5.0? No. They are working on extensions that could be used with HTML as well as XHTML. But in all probability, if their recommendations are ever adopted, they'll probably only officially be applied to XHTML, because W3c is no longer interested in HTML because, well, it has no future :)

      I deny that. It's just as easy to code valid HTML as it is to code valid XHTML.
      No, you're denying that XHTML is easier to code than HTML. I agree. But, that's not what we were talking about. What is undeniable is that it is easier to start authoring in XHTML, than it would be to put off authoring in XHTML until later and then converting all of the HTML to XHTML.
      --
      Despite what EULAs say, most software is sold, not licensed.
    53. Re:XHTML by slcdb · · Score: 1
      IE only "supports" XHTML because it ...
      Yeah, I saw that after I posted it. My original post mentioned that IE does not support XHTML, and now I'm contradicting myself. It's because I got sloppy. What I meant was that IE renders XHTML just fine. And it does.

      But don't mind me, I've only been doing this for 9 years, what do I know? Or Hixie for that matter, who the hell does that guy think he is?
      That makes everyone else noobs? There's only room for one or two knowledgable people?

      I've read Hixie's entire rant on why XHTML as text/html is "harmful". But his real argument in there is that "switching" from text/html to application/xhtml+xml may not be as easy as authors would think. That may be true, if said authors don't understand what it is they are doing or aren't careful. But that's not XHTML's fault. And it isn't good enough reason for folks who do know what they're doing, like you supposedly do, to not use XHTML full stop.

      Thanks for playing Pointless Interwub Argument 4.5. Your turn.
      Actually, you're right. This is pointless. Slashdot should just serve up application/xhtml+xml and lock the IE weenies out. Slashdot's target audience isn't likely running IE at all anyway. And for that rare bird who is semi-intelligent but for some puzzling reason actually still uses IE (I know -- seems like a paradox), it might even help spread Firefox.
      --
      Despite what EULAs say, most software is sold, not licensed.
    54. Re:XHTML by HeroreV · · Score: 1
      The point is that your content is ready for the future
      Ok, but if you're not going to send it as XHTML (yet), why not convert it into HTML before sending it? It's not difficult.
      it is easier to start authoring in XHTML, than it would be to put off authoring in XHTML until later and then converting all of the HTML to XHTML.
      Ok, I'll agree with you here, but it's really not that difficult. Still a little bit easier though than converting HTML into XHTML.
    55. Re:XHTML by Fweeky · · Score: 1

      "What I meant was that IE renders XHTML just fine. And it does."

      Mostly. Can you even put in an XML prologue without it screaming and running away to quirks mode yet? :/

      "And it isn't good enough reason for folks who do know what they're doing, like you supposedly do, to not use XHTML full stop."

      Sure, I'm not saying it is; thing is most XHTML users are in the camp that doesn't really know what they're doing, and even those that do are often constrained by legacy systems and other developers/users which are resistant to being retaught. But seriously, even when that isn't an issue, is there really a big reason to use XHTML 1 because of some vague notion that it'll make migrating to a new spec a few years hence easier? Why not just make sure your web-apps are written nicely enough so it's easier to add closer to when it'll actually be useful, and use that flexibility now for more immediately useful stuff like Atom/RSS feeds? Why introduce unnecessary complexity?

      "Actually, you're right. This is pointless."

      Well, I dunno, some might say avoiding work is a perfectly valid point ;)

      "Slashdot should just serve up application/xhtml+xml and lock the IE weenies out"

      Unfortunately Slashcode is one of those legacy applications which are resistant to change. Messy Perl and a million user-input HTML elements is hardly the perfect system to be serializing XML from; serving XHTML as XML is all fun and games until something trivial breaks and a million users get a Syntax Error. Be permissive in what you accept indeed...

      BTW, is your URL supposed to redirect to some eOpinions TFT review? :)

    56. Re:XHTML by slcdb · · Score: 1
      Can you even put in an XML prologue without it screaming and running away to quirks mode yet? :/
      Nope. It will still go into quirks mode. But any time I author new content, I use the XML prologue anyway. My reasoning is that even when IE is not in quirks mode, it still doesn't render many CSS stylings correctly. So, no matter what, I end up needing to utilize IE's conditional comments to load up a "special" stylesheet, just for IE, that overrides styles in the real stylesheet with variants that make the content look right in IE.

      The only time I can get away without a "special" stylesheet is if I'm clever enough to avoid any styles that IE doesn't render properly. With simple designs, this is surprisingly often possible.
      Be permissive in what you accept indeed...
      That's a very good point. It's one of the founding principles of the Internet and the one thing that keeps the whole damn thing running at all. Perhaps that's what we deserve for letting web standards (the W3C) exist independently of the IETF.
      --
      Despite what EULAs say, most software is sold, not licensed.
    57. Re:XHTML by slcdb · · Score: 1

      Oh, and thanks for reminding me to forward my URL elsewhere. My experiment with epinions is done ;)

      --
      Despite what EULAs say, most software is sold, not licensed.
  11. The Big Move by qw(name) · · Score: 2, Informative

    It's good to see that you're moving on to something more modern. HTML 3.2 is very antiquated and isn't CSS friendly. It would more work to move to XHTML 1.0 Transitional but I would think that it would pay off big dividends in the future.

    1. Re:The Big Move by Sentry21 · · Score: 2, Informative

      I'm curious as to what you mean when you say 'HTML 3.2 ... isn't CSS friendly'. the CSS1 recommendation is actually older than the HTML 3.2 recommendation by about a month. Sure, it's not as CSS-friendly as, say, HTML 4.01 or XHTML 1.x, but I don't think 3.2 is explicitly unfriendly.

    2. Re:The Big Move by qw(name) · · Score: 1

      That's a good point. Maybe I should have stated that as you did, "isn't as CSS-friendly..."

      Thanks.

    3. Re:The Big Move by Bogtha · · Score: 1

      HTML 3.2 is very antiquated and isn't CSS friendly.

      Slashdot never used HTML 3.2, they used tag soup. You can use CSS with HTML 3.2 just fine. In fact, you can use CSS with HTML 2.0 just fine.

      --
      Bogtha Bogtha Bogtha
  12. Slashdot.... testing??? by FortKnox · · Score: 2, Interesting

    After almost 8 years, Slashdot's HTML is finally getting an overhaul.

    I'm more surprised that after 8 years, slashdot is testing something on a machine that isn't the main server.

    Seriously, while you guys are changing things, how about changing it so ALL code changes go through regression testing along with some major user testing before you drop ut into the production servers. We all dislike 503s, and we have see a TON of bugs pop up (like last weeks 'unable to see comments' for several hours).

    --
    Good quote, too many chars. Seriously, the slashdot 120 char limit sucks!
    1. Re:Slashdot.... testing??? by tgd · · Score: 2, Insightful

      This is a site that hires, or at least otherwise uses the services of, Zonk.

      And you're surprised they don't test anything?

    2. Re:Slashdot.... testing??? by tgd · · Score: 1

      Okay seriously... Troll?

      Clearly someone didn't see Zonk's postfest on Friday night / Saturday morning. ;-)

    3. Re:Slashdot.... testing??? by Anonymous Coward · · Score: 0

      I didn't mod you, but I also didn't see the postfest. Link?

    4. Re:Slashdot.... testing??? by tgd · · Score: 1

      Just go back to the new articles a couple days ago.

      It was an orgy of double posting and lack of critical thinking.

    5. Re:Slashdot.... testing??? by Anonymous Coward · · Score: 0

      The search function is currently unavailable. Please use this instead.

      Nothing to see here. Please move along.

  13. I groan saying this... by Moridineas · · Score: 1, Redundant

    but...

    Is slashcode slashdotted??

    1. Re:I groan saying this... by wbren · · Score: 2, Funny

      No, the new site design is just a blank gray window with a never-ending browser status animation culminating in a message box that says "Host unavailable". I bet that only took three lines of CSS code.

      --
      -William Brendel
    2. Re:I groan saying this... by T-Ranger · · Score: 2, Funny

      My bet is that they rewrote slash in Ruby on Rails, and as a result it actually takes negative storage space. slashcode isnt realy slashdotted, the extra hard drives that are popping out of that server have knocked out the ethernet line....

    3. Re:I groan saying this... by ultranova · · Score: 1

      No, the new site design is just a blank gray window with a never-ending browser status animation culminating in a message box that says "Host unavailable".

      If the animation never ends how can it culminate in anything ?-)

      --

      Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

    4. Re:I groan saying this... by wbren · · Score: 1

      The... but then the animation it... umm... stops but starts back up again.... the message box pops up and uhh... it culminates.

      --
      -William Brendel
  14. From Slashcode.com by evil-osm · · Score: 1

    If you'd like to see what Slashdot might look like you can activate the Slashdot stylesheet on Slashcode.com in Firefox by choosing View > Page Style > Slashdot. I'm sure you can do the same thing with other browsers but you're on your own for the specifics of how to do so.

    --


    E.

    Never rub another man's rhubarb - The Joker
  15. Why do this? by L.+VeGas · · Score: 1

    If it ain't broke... oh, nevermind.

    1. Re:Why do this? by Pike · · Score: 5, Insightful

      Um, because:

      Though a few KB doesn't sound like a lot of bandwidth, let's add it up. Slashdot's FAQ, last updated 13 June 2000, states that they serve 50 million pages in a month. When you break down the figures, that's ~1,612,900 pages per day or ~18 pages per second. Bandwidth savings are as follows:

      * Savings per day without caching the CSS files: ~3.15 GB bandwidth
      * Savings per day with caching the CSS files: ~14 GB bandwidth

      Most Slashdot visitors would have the CSS file cached, so we could ballpark the daily savings at ~10 GB bandwidth. A high volume of bandwidth from an ISP could be anywhere from $1 - $5 cost per GB of transfer, but let's calculate it at $1 per GB for an entire year. For this example, the total yearly savings for Slashdot would be: $3,650 USD!

      Remember: this calculation is based on the number of pages served as of 13 June, 2000. I believe that Slashdot's traffic is much heavier now, but even using this three-year-old figure, the money saved is impressive.

    2. Re:Why do this? by FireFury03 · · Score: 1

      Remember: this calculation is based on the number of pages served as of 13 June, 2000. I believe that Slashdot's traffic is much heavier now, but even using this three-year-old figure, the money saved is impressive.

      For extra bandwidth savings they should also think about using client-side XSLT. Send all the styling XHTML data to the clients as an XSLT stylesheet along with the CSS stylesheet, both the XSLT and CSS get cached by the browser and from then on you're just shifting the actual _content_ over the network. Definately a Good Thing.

    3. Re:Why do this? by farker+haiku · · Score: 5, Funny

      Remember: this calculation is based on the number of pages served as of 13 June, 2000. I believe that Slashdot's traffic is much heavier now, but even using this three-year-old figure, the money saved is impressive.


      Welcome to 2005.

      --
      Your sig(k) has been stolen. There is a puff of smoke!
    4. Re:Why do this? by Pike · · Score: 1

      well...let's not push our luck :)

    5. Re:Why do this? by Anonymous Coward · · Score: 2, Insightful

      The figures were three years old, when that article was written two years ago. 3 + 2 = 5, LOL!

      Welcome to reading the fucking article.

    6. Re:Why do this? by _DangerousDwarf · · Score: 1

      Uhmmm I am not sure I would trust someone's figures when they can't even get the right answer from subtracting 2000 from 2005! :)

      I do agree that the traffic is much higher now!

    7. Re:Why do this? by Anonymous Coward · · Score: 0

      So what about someone who is too lazy to click the link and see that the article quoted was written in November of 2003?

    8. Re:Why do this? by appleprophet · · Score: 1

      The thing is that once you graduate from $10/month shared hosting plans, the $X/gigabyte model doesn't really apply anymore. Slashdot certainly has a dedicated internet connection, instead of paying for bandwidth on a meter. It's unlikely that their pipe is completely saturated, so I am sure that they have tons of bandwidth to spare.

    9. Re:Why do this? by Alioth · · Score: 1

      Reducing bandwith is always a good idea (it speeds up site access for a start) but considering most hosting providers now let you have around 1TB per server with no bandwidth charges, cutting bandwidth usage probably won't make any changes to how much it costs to run Slashdot.

    10. Re:Why do this? by adpowers · · Score: 1

      Hahaha, great reply. It has just the right amount of words to drive the point home. It isn't cluttered with extra and yet it still manages to pack a punch by insulting the grandparent.

    11. Re:Why do this? by DianeOfTheMoon · · Score: 1

      Welcome to 2005.

      Welcome to 1999...wanna hear a really great joke?

      --
      Problems are like gifts, it's better to give than to receive
    12. Re:Why do this? by big+daddy+kane · · Score: 1

      Yeah, but does $3,650 cover the expense of a team of web designers or programmers or whatever to redo a site?

    13. Re:Why do this? by Pike · · Score: 1

      The quote was from an article, which I linked, that was written two years ago.

      2005 - 2 - 2000 = 3

  16. Comment removed by account_deleted · · Score: 4, Funny

    Comment removed based on user account deletion

  17. But... by daniil · · Score: 1

    ...does it validate?

    --
    Man is a slave because freedom is difficult, whereas slavery is easy.
    1. Re:But... by Dynedain · · Score: 1

      HTML Validation

      CSS Validation

      In short, as of posting, no. There is 1 error in the CSS (and 2 warnings) and 8 errors in the HTML, all of which look to be fairly trivial to correct.

      --
      I'm out of my mind right now, but feel free to leave a message.....
  18. finally... lol by kiskoa · · Score: 1
    A List Apart, the design magazine, did it nearly two years before!

    Let me quote something from that article:


    Before you panic because I'm picking on Slashdot, let me inform you that I asked Rob "CmdrTaco" Malda, the guru behind Slashdot, for permission to post this information, and he stated in his reply email:



    Have fun. Feel free to submit patches back to us if you come up with anything useful. Slashdot's source code is open source and available at www.slashcode.com.



    --
    If Yoda so strong in Force is, why words in right order he cannot put?
    1. Re:finally... lol by joeljkp · · Score: 4, Informative

      Here's one explanation, from CmdrTaco's Journal:

      "Pudge has been working a lot on that problem. Specifically we've got scripts to fix HTML in all editor & user contributed content spaces. A lot of this is under way already. Old comments are being automatically fixed in the background. HTML in articles from 1998 is being corrected. Scripts are working very hard. And in some cases, tired editors have been re-reading stories from 1998 to correct HTML errors that boggle the mind. None of this is perfect, so don't be to surprised if you find something wonky. Feel free to mail me URLs if you see it. We've got almost 60,000 articles, 900,000 users, and like 13 million comments. There will be mistakes."

      --
      WeRelate.org - wiki-based genealogy
    2. Re:finally... lol by pretentiousPPC · · Score: 1

      60K?? Does that include all the dupes as well?

      --
      Artist will always make art.
  19. Browser compatibility testing by Hulkster · · Score: 1, Funny

    I tested the CSS version with wget and it looks good ... ;-)

    1. Re:Browser compatibility testing by La+Gris · · Score: 1

      Yes, the css look nice with telnet as well.

      me@thing:~$dig www.slashcode.com +short
      66.35.250.197

      me@thing:~$ telnet 66.35.250.197 80
      Trying 66.35.250.197...
      telnet: Unable to connect to remote host: Connection timed out

      me@thing:~$ telnet 66.35.250.197 80
      Trying 66.35.250.197...
      telnet: Unable to connect to remote host: Connection refused

      me@thing:~$ telnet 66.35.250.197 80
      Trying 66.35.250.197...
      Connected to 66.35.250.197.
      Escape character is '^]'.
      GET /base.css HTTP/1.1
      Host: www.slashcode.com

      HTTP/1.1 200 OK
      Date: Tue, 06 Sep 2005 16:53:22 GMT
      Server: Apache/1.3.31 (Unix) mod_perl/1.29
      X-Powered-By: Slash 2.005000
      X-Bender: The laws of science be a harsh mistress.
      Last-Modified: Fri, 02 Sep 2005 20:15:57 GMT
      ETag: "8cc-2438-4318b2fd"
      Accept-Ranges: bytes
      Content-Length: 9272
      Connection: close
      Content-Type: text/css

      body, div, form, h1, h2, h3, h4, h5, h6, #links ul li, #links ul, #topnav, img
      {
                      padding: 0;
                      margin: 0;
      }

      --
      Léa Gris
  20. Re:w00t by VJ42 · · Score: 1

    And whilst you'ra st it, mabe you can make slashcode validate currently it the validator outpts this: http://validator.w3.org/check?verbose=1&uri=http%3 A//slashdot.org/

    --
    If I have nothing to hide, you have no reason to search me
  21. Tinfoil hat -- the firefox rendering bug..... by Anonymous Coward · · Score: 0
    The only reason I used IE for many years was the firefox-slashdot-rendereing bug.

    Seems now that the firefox slashdot rendering bug is fixed, the old broken /. can no longer be used to drive people away from F/OSS to Internet explorer. (for example, I switched totally to firefox)

    Because this bug is fixed, I bet Microsoft (the buyer of quite a few /. ads) is no longer as interested in supporting /. Perhaps this is a strategy to implement IE-specific CSS to get people to switch from firefox to IE again

  22. Change? by bazmail · · Score: 0

    we fear change.

    *raises hands to block out the light.....*

  23. next you'll be telling us by Anonymous Coward · · Score: 0, Troll

    you fixed the american flag icon with the wrong number of stripes.

  24. 404 by DavidBartlett · · Score: 1

    We have slashdotted the future.

    --

    -DB-
    E-mail is like a prison: a prison with no walls... and no toilet. -Strong Bad
  25. Does the new version... by Pivot · · Score: 1, Funny

    Come with a spell checker for submitters?

    1. Re:Does the new version... by Anonymous Coward · · Score: 0

      how about a dupe checker?

    2. Re:Does the new version... by JHromadka · · Score: 4, Informative

      Yes, it's called Safari.

      --
      "The objective of securing the safety of Americans from crime and terror has been achieved." -- John Ashcroft
    3. Re:Does the new version... by Carewolf · · Score: 1

      Just use Konqueror...

      Please.

  26. Who is Making the Changes? by eno2001 · · Score: 2, Insightful

    Is this in response to that big story last year where someone actually redid Slashdot's main page in CSS to show just how easy it would be to do? Kind of funny in a way because people who usually want to prove how easy something is to accomplish have no idea of just how much glue sits behind the scenes. That's usually what makes these kinds of changes so difficult and fraught with rendering errors, coding slips and the like. Even moreso when you only have a handful of decent people working on the system and a ton of mediocre people making up the majority of the development team. When it comes to systems this big and complicated, it's a wonder they work at all. So who will be making these CSS changes?

    --
    -"...bad old ideas look confusingly fresh when they are packaged as technology" - Jaron Lanier (Digital Maoism on Edge.o
    1. Re:Who is Making the Changes? by omega9 · · Score: 1
      Just for reference:

      The "someone" that redid Slashdot was A List Apart, more commonly refered to as ALA. It was a two part series.


      ALA is an awesome sight for real-world web development. Also interesting is that they've recently redesigned their site as well and moved to Ruby On Rails in the process.
      --
      I'm against picketing, but I don't know how to show it.
    2. Re:Who is Making the Changes? by eno2001 · · Score: 0, Troll

      Before you start criticizing people who do this stuff for a living, why don't you wake up and smell the coffee? In case you're not aware, there have been a lot of developments in content management systems since Slashcode was created. A lot of the innovation (thanks to Sharepoint Portal and Frontpage) has happened on the Windows platform where completely overhauling a site is something that can be accomplished in minutes by any decent Windows admin. Hell. You don't even need coders, or HTML designers. All you need is to train your network admin on the use of FrontPage and provide him with a decent media library to choose looks and feels from. But, since you and your buddies here are stuck in the bad old days where everything is tweaked in a text based config file, you've got to make a big deal out of this switch to CSS and claim that it's a big event. It's not and it shouldn't be treated as such. It's just another document and if you really know what you're doing, you'll be able to make the changes from within MS Word. The key is to cut non-essential staff (all Unix admins are non-essential these days). But you keep trying to drag us back to 1970. We'll get you eventually. It's only a matter of time.

      --
      -"...bad old ideas look confusingly fresh when they are packaged as technology" - Jaron Lanier (Digital Maoism on Edge.o
    3. Re:Who is Making the Changes? by DarKnyht · · Score: 1

      Yes, but the point is to clean up the code and not to throw in a bunch of Frontpage crap code into the document.

      --
      Voting them all out of office, now that's change I can believe in.
    4. Re:Who is Making the Changes? by eno2001 · · Score: 1

      That's my point exactly. The grandparent post seems to have some clue about just how complex these kinds of changes can be and why you can't just point and click your way to a new website with FrontPage or SharePoint Portal. At best, you might get a generic mockup of what a real site should look like using those tools. But the fact is that it it's not custom coding, it's never going to fulfill your business needs. That's why projects like Slashcode and Wiki are so important. They are much more flexible than anything you'll ever see coming out of Redmond.

      --
      -"...bad old ideas look confusingly fresh when they are packaged as technology" - Jaron Lanier (Digital Maoism on Edge.o
    5. Re:Who is Making the Changes? by metamatic · · Score: 1
      Kind of funny in a way because people who usually want to prove how easy something is to accomplish have no idea of just how much glue sits behind the scenes.

      True, but we can estimate how much glue the editors are sniffing from the frequency with which they post blatant duplicates of articles.

      --
      GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
    6. Re:Who is Making the Changes? by DarKnyht · · Score: 1

      Eno2001 wrote, "Before you start criticizing people who do this stuff for a living, why don't you wake up and smell the coffee? In case you're not aware, there have been a lot of developments in content management systems since Slashcode was created. A lot of the innovation (thanks to Sharepoint Portal and Frontpage) has happened on the Windows platform where completely overhauling a site is something that can be accomplished in minutes by any decent Windows admin. Hell. You don't even need coders, or HTML designers. All you need is to train your network admin on the use of FrontPage and provide him with a decent media library to choose looks and feels from. But, since you and your buddies here are stuck in the bad old days where everything is tweaked in a text based config file, you've got to make a big deal out of this switch to CSS and claim that it's a big event. It's not and it shouldn't be treated as such. It's just another document and if you really know what you're doing, you'll be able to make the changes from within MS Word. The key is to cut non-essential staff (all Unix admins are non-essential these days). But you keep trying to drag us back to 1970. We'll get you eventually. It's only a matter of time."

      Eno2001 then wrote in response to me, "That's my point exactly. The grandparent post seems to have some clue about just how complex these kinds of changes can be and why you can't just point and click your way to a new website with FrontPage or SharePoint Portal."

      All I have to ask is where does Eno2001 get their drugs from that they can see their response can be rationally concluded from their original post?

      --
      Voting them all out of office, now that's change I can believe in.
  27. Jay Sherman says, by sjoplin · · Score: 0
    1. Re:Jay Sherman says, by Anonymous Coward · · Score: 0

      Without reading your subject line I thought you were referring to the "stinger" from MST3K's "Pod People" episode.

      I guess I'm simply a bigger geek than I thought.

  28. Poetic Justic by SumDog · · Score: 1

    You know I can't seem to get to the site. Ah the slashdot effect on...well...slashdot. It's almost poetic

  29. Stylish by Anonymous Coward · · Score: 0, Funny

    I vote for the entire site to be made in Shockwave. CSS is for suckers.

  30. Holy Living Fuck! by Anonymous Coward · · Score: 0, Funny

    Duke Nukem Forever is just about to be released too!

  31. File not found by CubicleView · · Score: 4, Funny

    Hi, could everyone stop clicking on the link for a minute so I can open it, thanks.

  32. Dupe by Maxwell'sSilverLART · · Score: 3, Insightful

    This has already been done, about two years ago. See http://www.alistapart.com/articles/slashdot2/ and particularly http://www.uwplatt.edu/web/webstandards/slashdot.h tml

    --
    Moderate drunk! It's more fun that way!
    1. Re:Dupe by SuperDuG · · Score: 1
      http://www.alistapart.com/articles/slashdot2/


      Wow, I thought it was weird when I kept seeing "SuperDuG" in the screenshots. Then I recognized it as one of the stories I posted a few years ago.


      I'm famous?

      --
      Ignore the "p2p is theft" trolls, they're just uninformed
    2. Re:Dupe by Suppafly · · Score: 1

      I'm famous?

      No..

    3. Re:Dupe by PhilHibbs · · Score: 2, Funny

      No, you're a sex bot.

    4. Re:Dupe by Matt+Perry · · Score: 1
      This has already been done, about two years ago.
      Ha! You might want to read this page if you're wondering why Slashdot ignored those efforts to help them.
      --
      Slashdot: Failed Car Analogies. Amateur Lawyering. Anecdote Battles.
    5. Re:Dupe by PetoskeyGuy · · Score: 1

      If I remember correctly Taco did post about this some time back. The author only converted the final rendered HTML of /. to proper CSS. Anyone with a bit of skill could do that.

      The reason it didn't hit slashcode proper was that it was a mess of code that was hard to follow. There were reasons the html was buggy was because the code making it was buggy.

      I'm guessing it's cleaner now, it's been several years since that article, and longer since I've looked at slashcode.

    6. Re:Dupe by Phroggy · · Score: 2, Insightful

      Sorry, but you have no idea what the hell you're talking about.

      Taking a static tag-soup HTML page and rewriting it to use compliant code and CSS is a major chore, and that's what was done in those two examples. But to convert a completely dynamic site like Slashdot is a whole 'nother kettle of fish. CmdrTaco has been saying for YEARS that they'd like Slashdot to be redone with valid HTML and CSS, but it's just been too massive a task, and nobody else has stepped up to the plate for the same reason.

      So no, this hasn't been done before, and it really is a big deal.

      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
    7. Re:Dupe by SuperDuG · · Score: 1

      am too :-(

      --
      Ignore the "p2p is theft" trolls, they're just uninformed
  33. Did /code get /.'d? by QuietLagoon · · Score: 1

    I get no response from server....

  34. You slashdotted Slashcode! by MarkEst1973 · · Score: 1

    You insensitive clod!

  35. Re:MOD PARENT UP by VJ42 · · Score: 1

    Greasemonkey will probably let you do it.

    --
    If I have nothing to hide, you have no reason to search me
  36. Sigh by suso · · Score: 4, Insightful

    Of course I know what HTML is. I was trying to be funny (appearently wasted effort). The joke is that HTML is old. For slashdot to only be using HTML makes it old. Something so old that people forgot about it.

    Oh nevermind.

    1. Re:Sigh by GoClick · · Score: 1

      I knew you were kidding *pat* *pat* *pat* there there....

      So when are articles going to get dates with years on them?

    2. Re:Sigh by Anonymous Coward · · Score: 1, Informative

      Look at the articles URL

    3. Re:Sigh by daniil · · Score: 4, Informative

      Ages ago. Go to Preferences -> Homepage (or just click here), and set Date/Time Format to something other than the default. And then forget to click Save.

      --
      Man is a slave because freedom is difficult, whereas slavery is easy.
    4. Re:Sigh by fyngyrz · · Score: 1
      HTML will remain more important than CSS until the day that CSS behaves as well (meaning, consistently) as HTML does.

      If that day ever comes.

      It doesn't do as much good as you think to jump thru CSS hoops if it only works on some browsers, and it does no good at ALL if you code it so that it works on Explorer, which is outright broken and sucks with regard to CSS. At this point in time.

      So while you were trying to be funny, the fact is, you weren't funny. Because your base assumptions were incorrect.

      --
      I've fallen off your lawn, and I can't get up.
    5. Re:Sigh by qbwiz · · Score: 1

      What you said doesn't make any sense. It's very hard to use CSS without HTML (although it does work for XML). It, then, is very unlikely that CSS will ever become more important than (X)HTML. The great-...-grandparent was contrasting HTML and XHTML.

      --
      Ewige Blumenkraft.
    6. Re:Sigh by Hurricane78 · · Score: 1

      > and it does no good at ALL if you code it so that it works on Explorer

      IE? Are you trying to tell me that there are slashdotters who use the IE except for the trolls??
      OMFG, slashdot is really gowng down the hill. ;)
      No really! ;)

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
    7. Re:Sigh by bprime · · Score: 1

      For slashdot to only be using HTML makes it old.

      The site is hosted in Korea, you insensitive clod!

    8. Re:Sigh by gnarlin · · Score: 1

      I guess HTML must be from Korea then!

      --
      A bad analogy is like a leaky screwdriver.
  37. Re:Finally, Slashdot Slashdotted, Literally! by Anonymous Coward · · Score: 0

    Just be glad that they din't link to the main site an brought that down.

  38. Hell froze over by paulius_g · · Score: 5, Funny

    Damn,

    It's getting cold down here.

          - Satan

    1. Re:Hell froze over by Anonymous Coward · · Score: 0

      I can fly!

      - Pig.

  39. Re:MOD PARENT UP by IMarvinTPA · · Score: 1

    Or go download the GreaseMonkey script for it...

    (I'd link it, but the site is having difficulties.)

    IMarv

  40. Still buggy - wait for new slash sites by Lord+Satri · · Score: 1

    I decided to make my dreams come true and have my own slashsite. Wanting to migrate my successful GIS / RS mailing list to slash. http://www.matox.com/agisrs

    SlashCSS is not "ready yet". I though it would be easy to setup the site, but even with a lot of help from the slash mailing lists and http://www.lottadot.com/ . A few weeks will be required for our launch announcement.

    SlashCSS is really a great step in the right direction, however, my advice, if you're planning building a slash site, wait a little while, the whole process will be easier for you.

    We chose slash over other CMS http://www.cmsmatrix.org/ mainly because of the great (even if flawed) moderation system.

  41. Pinch me, I'm dreaming!! by Cally · · Score: 0, Offtopic
    Slashdot user since before there were user accounts (and when they were launched, alas! I thought "why would I want to waste time registering for an account? They'll probably just sell my email address to spammers...")

    There's been a hell of a lot of water under the bridge since the late 90s, for me personally, for the Wacky World of Computinga and Geekdom, and the world in general... OSX on Intel... 9/11... the Iraq war... the slow inexorable rise of Linux and Free Software... the 'Slash' code was finally released (after many fun years taking the piss out of Taco because it was closed!)... DEC was bought by Compaq, Compaq bought by HP... IBM drank the koolaid and started pushing Linux.... Lucas released three of the worst films ever made... Matrix I... all the trollers and crapfloods (come back UG the open-source caveman, all is forgiven!)

    And many other happy memories of hours wasted at work. And home. And I've changed from a Microsoft / Access developer to Perl, Apache, MySQL, become a real proper developer using Linux as a workstation and CVS... designed & built the system that automatically produces and releases antivirus updates... worked for a dotcom that went titsup... been unemployed... and managed to move over to fulltime network security / pentesting. But enough of my yakkin'...

    --
    "None are more hopelessly enslaved than those who falsely believe they are free." -- Goethe
    1. Re:Pinch me, I'm dreaming!! by bad_outlook · · Score: 1

      if you're dreaming of slashdot, I think it may be time to leave home and go out for awhile.

    2. Re:Pinch me, I'm dreaming!! by zztzed · · Score: 1
      alas! I thought "why would I want to waste time registering for an account? They'll probably just sell my email address to spammers..."
      Yes, if only you'd foreseen the potential for uid-based bragging rights like I did!
    3. Re:Pinch me, I'm dreaming!! by the+phantom · · Score: 1

      Slashdot user since before there were user accounts (and when they were launched, alas! I thought "why would I want to waste time registering for an account? They'll probably just sell my email address to spammers...")

      No kidding... it took me two or three years before I decided to register a user. Oh, well.

    4. Re:Pinch me, I'm dreaming!! by Cally · · Score: 1

      Well, no; actually, it was just a figure of speech...

      --
      "None are more hopelessly enslaved than those who falsely believe they are free." -- Goethe
    5. Re:Pinch me, I'm dreaming!! by Cally · · Score: 1
      No kidding... it took me two or three years before I decided to register a user
      ISTR noticing that two-figure UID owners were taunting those lamer n00bs with three figure UIDs... at that point the cat was out of the bag and the scramble began in earnest.
      --
      "None are more hopelessly enslaved than those who falsely believe they are free." -- Goethe
  42. Re:Sorry for being a luddite but.. by syrinx · · Score: 1

    Slashdot works and it works well.

    LOL, mod parent funny.

    --
    Quidquid latine dictum sit, altum sonatur.
  43. Re:Sorry for being a luddite but.. by Lardmonster · · Score: 2, Insightful

    "I just want to be able to read articles and comments. Period."

    Sure.

    But blind / partially sighted / physically disabled folks want to read articles and comments too. Period.

    And CSS helps make websites more accessible.

    --
    The more advanced the technology, the more open it is to primitive attack
  44. Bug Report by johnkoer · · Score: 5, Funny

    I tried this and it seems to be kicking out quite a few duplicate stories. Is that normal?

    1. Re:Bug Report by gottabeme · · Score: 1

      Mod me down, but I think they broke the stupid detector too.

      --
      "Those who consume the bulk of goods are those who make them. We must never forget this secret of our prosperity."
  45. Re:Sorry for being a luddite but.. by Anonymous Coward · · Score: 0

    you've got it backwards

    slashdot is horribly broken. it follows old standards and it doesnt follow them good. theres tons of page rendering problems

    css isn't flash, slashdot isnt going to become shockwave.com its just going to become standard compliant.

    css is what sites should be developed in now, its the new standard and slashdot needs to catchup and use it

  46. The document contains no data. by Thaelon · · Score: 0, Redundant

    Ladies and gentlemen it has finally happened.

    Slashdot has slashdotted itself.*

    *Ok, so slashdot slashdotted www.slashcode.com. Slash slash slash......slash

    --

    Question everything

  47. Re:Sorry for being a luddite but.. by cyborg_zx · · Score: 1

    There are numerous advantages of using CSS with HTML rather than using HTML alone - not least of which is that the old way is just fugly to maintain. As far as the user is concerned it has advantages too. For example it makes life a lot easier if you're using Lynx on a webpage that uses CSS and HTML standards properly. That goes for other accessability conerns as well.

    IMHO the old Netscape way of doing styles with et al is broken, dead, and should be expunged from the Internet.

    I don't know if you've ever tried developing with it but I stopped doing things the old way right after I found out about it.

  48. in other news by rayde · · Score: 2, Funny
    Duke Nuken Forever is being released! On the Phantom Gaming Console. Which will be running Longhorn!

    seriously though, this is a good thing, hopefully this will allow for user-chosen themes, etc. and way to get http://it.slashdot.org/ to not look like baby poo.

    1. Re:in other news by minus_273 · · Score: 1

      and Red Sox won the world series, we know who deep throat is and Macs now run on intel processors..

      --
      The war with islam is a war on the beast
      The war on terror is a war for peace
  49. WOW! by N3wsByt3 · · Score: 1

    Merely 8 years, and the code already gets an update!

    With the high level of IT nerds around here, one can only guess what's next! Maybe something wild... like maybe slashdot will become readable when you use Firefox, for instance!

    The skype is the limit!

    --
    --- "To pee or not to pee, that is the question." ---
    1. Re:WOW! by frinkacheese · · Score: 1

      Errm, I use Firefox - which bit exactly is unreadable?

    2. Re:WOW! by Anonymous Coward · · Score: 0

      There is, or was (I don't see it anymore) a long standing problem with Firefox totally misrendering Slashdot into an unreadable blog at times.

    3. Re:WOW! by Anonymous Coward · · Score: 0

      lol I said blog, I meant blob.

      I think both statements tend to be accurate.

  50. Re:Sorry for being a luddite but.. by nateziarek · · Score: 1

    Yes, CSS can cause people to go crqzy with design and layout and fluff. There was an article once in The Onion about a guy who got a new Photoshop filter and used it on everything. CSS can be a lot like that. However, CSS is also the future (hell current) of web design. It can cut bandwidth usage and in general make the pages "flow" better. Also, by using CSS (& I hope xHTML, haven't been able to look at SlashCode yet), you seperate content from layout, making it easier to offer Slashdot on other devices (like PDAs or Phones, etc). Slashcode isn't quite broke, but it probably doesn't work as well as a modern, popular CMS should.

  51. huh? by bad_outlook · · Score: 3, Interesting

    finally, being as /. is such a tech site, it's about time to bring things into this century. Hell, I rework my site constantly, I still can't believe /. went so long with old/outdated/non-validated code. perhaps it could be a quarterly thing to update things in the future.

    1. Re:huh? by RUFFyamahaRYDER · · Score: 1

      The quarterly thing would be good. Maybe we can band together and create a Slashdot Zen Garden! =)

      Like this!

  52. maybe apple ... by mbaudis · · Score: 1

    maybe apple using switching the mac main processors from powerpc to some intel breed? though, this is even more unlikely, i think.

  53. Cover(Index) Page good ...Comments page bad by Anonymous Coward · · Score: 0

    (I'm posting as AC because I already modded another comment)

    The index page looked great, but when I clicked on a comment page, it was horrible and misshapen.

    (I don't know if that was because the server was struggling under load and perhaps delivered only part the page and no style??).

  54. Waiiiiiiiiiit... by scenestar · · Score: 1

    You want /. to adapt to IE's raped standards?

    Even after slashdot had headlines stating Internet explorer was a "cancer to the web"?

    Go eat a rock.

    IE should be effectively killed.

    --
    perpetually dwelling in the -1 pits
    1. Re:Waiiiiiiiiiit... by egriebel · · Score: 2, Insightful
      You want /. to adapt to IE's ... standards? .... IE should be effectively killed.

      Y'know, that's a great idea, why target what is most prevalent on the Internet when one can target for some superior solution which NOBODY has completely implemented.

      I guess next articles for you are:

      • The OSI standard and you
      • Why I love Betamax
      • "Pragmatic," the new four-letter word
      • "The most elegant solution": how I've spent hours thinking rather than doing.
      • Don Quixote, a model for our times
      --
      ACHTUNG! Das computermachine ist nicht fuer gefingerpoken und mittengrabben. Ist nicht fuer gewerken bei das dumpkopfen.
  55. Re:Sorry for being a luddite but.. by schon · · Score: 1

    From the slashcode page:

    this might bring savings of 10GB of bandwidth PER DAY, while making each reload a little faster for everyone

  56. Slashcoded? by dzfoo · · Score: 0, Redundant

    Wow, Slashcode has been Slashdotted... how fitting.

          -dZ.

    --
    Carol vs. Ghost
    ...Can you save Christmas?
  57. Performance gain by Barryke · · Score: 0, Redundant
    take a look at Slashcode.

    Timeout.
    Is it just me or has slashcode been slashdotted?

    Serious, i'm curious as to what the performance figures on the servers look like; before -and- after the overhaul.
    --
    Hivemind harvest in progress..
  58. Re:Sorry for being a luddite but.. by Proteus · · Score: 5, Insightful

    Who cares? Three main groups:

    People with disabilities prefer CSS because it allows them to trivally alter layout and visual presentation in a way that works for them. For example, some people have trouble seeing low-contrast presentations; they can insert their own CSS into a CSS-aware page to make any site readable.

    The folks who pay for the bandwidth tend to like CSS because it costs less to serve (properly implemented, that is). CSS separates style from content, so the style can be cached while smaller content pages are tranferred on request. This makes a better end-user experience and costs less to provide.

    Developers and designers like CSS because it follows the excellent practice of separating view from data. It's easier for a developer to make changes to the underlying code because they worry less about breaking the view; likewise, a designer can make layout tweaks without affecting other areas of code. Clean separation makes fewer bugs.

    --
    We may not imagine how our lives could be more frustrating and complex—but Congress can. – Cullen Hightower
  59. Slashdotted by Jeff+Hornby · · Score: 1

    Looks like I'm going to have to change my sig!!

    --
    Why doesn't Slashdot ever get slashdotted?
  60. 'lite' version by jmarkantes · · Score: 1

    With slashcode not responding, I haven't seen it yet, but I hope the 'lite' version also improves with the css overhaul. I've only read the site in the lite version, and it always jolts me when I periodically see it's full drab look.

    Yeah yeah, user style sheets are doable, but not yet terribly convenient. At least while things are beta.

    Just a couple cents.
    J

  61. Re:Sorry for being a luddite but.. by Chatterton · · Score: 1

    You are a troll.

    Slashdot doesn't work well. I get 100+ warning with tidy on nearly any slashdot page (except the post a comment page where I have 'only' 21 warnings). Yes I am an HTML purist like a lot of the bests C/C++ coder doesn't like ANY warning at the end of a compilation. I write web site for a pleasure and I absolutly don't like warnings or error because generaly that's the first signs of incompatibility on some web browsers.

    Secondly we are not talking about fancy flash animation but CSS. CSS as nothing to do about fancy flash animations. CSS is good for people with disability who can modify it locally to adapt a site at their needs (think biggers fonts, adapt the page layout...). And CSS is the standard. HTML 3.2 is dead.

    I stop here else I will use some explectative not to be read by young people :/

  62. Light with No Icons by mzs · · Score: 1

    All I want is for these to remain as a preference option since that is what I use.

  63. Wonderful by Master+of+Transhuman · · Score: 0, Troll


    Now the dupes will be prettier.

    Is there such a thing as CSS for Zonk?

    --
    Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
  64. CSS Reboot? by Anonymous Coward · · Score: 0

    Slashdot should take part in the CSS Reboot.
    http://www.cssreboot.com/

  65. Slashcode /.ed??? by christose · · Score: 0, Redundant

    Slashcode's been ./ed??? :S

  66. Times New Roman SUCKS!!! by ndrtkr · · Score: 0, Troll

    Get rid of it please!!!
    Bring Verdana or something more pleasant in...

    --
    - live from Costa Rica !
  67. Fortunately by the_mighty_$ · · Score: 1

    The "design for all browsers" paradigm isn't a good one. It promotes the use of non-compliant browsers. It's much better to design to the standards no matter what.

    Fortunately, in today's world it is possible to use standards AND design for all (modern) browsers at the same time! I've done it with several sites. Of course, you wont be able to support browsers like Netscape 4, but come on folks, this is 2005. Anyone still using browsers like that is an idiot, and likely wont even notice that the CSS isnt displaying correctly.

    --
    VI VI VI - the editor of the beast!
    1. Re:Fortunately by arkanes · · Score: 2, Informative
      Fortunately, in today's world it is possible to use standards AND design for all (modern) browsers at the same time!

      Well - no. Not unless what you actually mean is "use a small subset of CSS 1". And even then there are minor incosistencies and differences that can end up biting you (although they often won't). If you want your site to work in IE, and you do, then you either need to stick with minimal CSS support, or have forked or otherwise hacked up CSS. Period. Additionally, if you want to support IE 5 (not nearly as rare as Netscape 4), you have to be aware of the broken box model and work around it via hacks. IEs behavior prior to IE 6 (with the right doctype) is just plain wrong and CSS written for it will *not* work in other browsers.

    2. Re:Fortunately by thc69 · · Score: 1
      Netscape 4, but come on folks, this is 2005. Anyone still using browsers like that is an idiot


      Any Slashdot readers using NS4 are probably disallowed from using anything else by corporate policy.

      What's wrong with the existing html, anyway?
      --
      Procrastination -- because good things come to those who wait.
    3. Re:Fortunately by NickFitz · · Score: 5, Insightful
      <rant>

      Absolute nonsense. I implement sites for major commercial organisations which use standards-based CSS 1 and 2.1, and they work just fine cross-modern-browser - IE-Win, IE-Mac, Opera, Firefox, Safari, you name it. And when I say "just fine", I mean "look identical to the pixel", as well as scaling seamlessly for visually impaired users, being fully accessible to assistive technologies, having semantically pure markup and degrading gracefully in ye olde browsers.

      On my current project I combine floating, absolute positioning and just about every other CSS technique in the book, and out of 1800+ lines of CSS across the entire site, just 13 are to cater for IE's brokenness.

      Everything one needs to know to make standards-compliant sites that work in today's browsers is out there (including avoiding the IE-5-Win box model problem), but many "web designers" are so lacking in an understanding of the technologies with which they work that they can't or won't improve. I see new sites produced using nested tables, for goodness sake; I used those techniques myself last century when there was no alternative, but these people really need to get with the programme.

      It's the same problem that leads to so many useless implementations in any field: the vast majority of people are unwilling to undertake a process of constantly improving and refining their skills, and the employers aren't sufficiently well-informed to make the distinction between those who work hard to make the best possible use of the available technologies, and those who read a book about HTML in 1997 and have been marking time ever since.

      Luckily things are now changing, and clueful organisations are demanding people who can work with standards. A lot of people who think they understand how to produce a web page are going to be looking for alternative employment over the next year or so unless they catch up on the advances made over the last few years.

      </rant>

      Thank you for listening; have a nice day :-)

      --
      Using HTML in email is like putting sound effects on your phone calls. Just say <strong>no</strong>.
    4. Re:Fortunately by spectre_240sx · · Score: 3, Interesting

      Taken from A List Apart:

      "Perhaps the biggest benefit of this particular example is the bandwidth savings:

              * Savings per page without caching the CSS file: ~2KB per request
              * Savings per page with caching the CSS file: ~9KB per request

      Though a few KB doesn't sound like a lot of bandwidth, let's add it up. Slashdot's FAQ, last updated 13 June 2000, states that they serve 50 million pages in a month. When you break down the figures, that's ~1,612,900 pages per day or ~18 pages per second. Bandwidth savings are as follows:

              * Savings per day without caching the CSS files: ~3.15 GB bandwidth
              * Savings per day with caching the CSS files: ~14 GB bandwidth

      Most Slashdot visitors would have the CSS file cached, so we could ballpark the daily savings at ~10 GB bandwidth. A high volume of bandwidth from an ISP could be anywhere from $1 - $5 cost per GB of transfer, but let's calculate it at $1 per GB for an entire year. For this example, the total yearly savings for Slashdot would be: $3,650 USD!

      Remember: this calculation is based on the number of pages served as of 13 June, 2000. I believe that Slashdot's traffic is much heavier now, but even using this three-year-old figure, the money saved is impressive."

    5. Re:Fortunately by arkanes · · Score: 1
      That's great. I'm happy for you. THE FACT REMAINS: If your site works in IE, it works because either a) you ignore large parts of CSS 1 and 2 which IE does not implement or b) you browser sniff (either literally or via stuff like the CSS parser hacks) to present browser specific CSS. Period. Also, if you think that floating and absolute positioning are both good and unusual CSS, then you need a whack from the cluebat.

      By the way, your site is not pixel identical in Firefox & IE. I bet its different in Safari, too, although I can't check right now. It was a silly thing to claim anyway, as the only way to create pixel-identical sites is to not use any of the elements or CSS attributes that aren't rendered pixel identical across all browsers, which only supports my point.

    6. Re:Fortunately by h4rm0ny · · Score: 1


      What's wrong with the existing html, anyway?

      It could be better. Do we need another reason?

      --

      Aide-toi, le Ciel t'aidera - Jeanne D'Arc.
    7. Re:Fortunately by Nurf · · Score: 2, Informative

      I like the sound of what you say. I would love to be able to do CSS web sites that work on everything.

      I am a very technical guy who is usually designing and building hardware and software. However, I am in a small company, and am going to end up producing a web site for it whether I like it or not.

      Soo.. could you provide a few links or names of books that I read that would allow me to make web sites in the way you describe? Assume someone who is used to being given a pile of books in a new subject, and has a working prototype running in about three weeks. I normally sit down and just start implementing stuff, using the books as a continuous reference. Then I redo the stuff I did badly, once I know more about the subject. I suppose this means that little code snippets are of the most use to me, along with good explanations of what is actually going on.

      I realise you may have better things to do, but I am interested in what you consider to be "good" sources of information for this; you approach is one I appreciate.

      Thanks

      --
      ---
    8. Re:Fortunately by MP3Chuck · · Score: 1

      Just to expand on your stats there, ESPN switched to XHTML/CSS a while back and are now Saving 2TB of bandwidth every day . And those traffic numbers are from 2003. Not to mention the file size savings inherent in properly formed HTML (as opposed to Tag Soup a la Slashdot).

    9. Re:Fortunately by Anonymous Coward · · Score: 0

      Remember: this calculation is based on the number of pages served as of 13 June, 2000. I believe that Slashdot's traffic is much heavier now, but even using this three-year-old figure, the money saved is impressive."

      It's 2005 now -- where have you been for the last two years?

    10. Re:Fortunately by NutscrapeSucks · · Score: 1

      Number are totally baloney because Slashdot is served gzipped.

      For this example, the total yearly savings for Slashdot would be: $3,650 USD!

      OOH, three whole thousand dollars!!! Going to be a great XMas party this year!

      Seriously, are you impressed with that? This ain't a mom-n-pop operation. I wouldn't be surprised if the site redesign cost VA Linux $100K. Even if it cost half that, and even with bullshit figures, your cost analysis falls right on its ass.

      About the only business reason to justify such a redesign is so /. doesn't look so hypocritical it's daily blathering about how great web standards are. As you can see, when you break down they numbers, the case isn't always there.

      --
      Whenever I hear the word 'Innovation', I reach for my pistol.
    11. Re:Fortunately by Confuzzled · · Score: 1
      On my current project I combine floating, absolute positioning and just about every other CSS technique in the book, and out of 1800+ lines of CSS across the entire site, just 13 are to cater for IE's brokenness.


      I don't know what version of IE you're using, but I find constant problems with IE. No support for fixed elements, no support for transparent pings (alpha loader hack), flawed box model, etc. etc.



      One problem I still haven't found a solution for is how to center an image, with unknown size (dinamically generated), vertically.

    12. Re:Fortunately by NickFitz · · Score: 1

      THE FACT REMAINS: If your site works in IE, it works because either a) you ignore large parts of CSS 1 and 2 which IE does not implement or b) you browser sniff (either literally or via stuff like the CSS parser hacks) to present browser specific CSS. Period.

      Since we're shouting, THE FACT REMAINS: a) no, and b) no. Period.

      By the way, your site is not pixel identical in Firefox & IE. I bet its different in Safari, too, although I can't check right now.

      As the site to which I'm referring hasn't yet been launched, you can't possibly know. If you mean my personal site (which was clearly not the subject of my post), you ought to know that that's a standard WordPress template, used by thousands of sites. One day, when I'm not so busy achieving the impossible, I'll get around to implementing a design of my own; until then I couldn't really care less what somebody else's design looks like cross-browser.

      For now, it's back to making lots of money out of the things you say can't be done.

      --
      Using HTML in email is like putting sound effects on your phone calls. Just say <strong>no</strong>.
    13. Re:Fortunately by NickFitz · · Score: 1

      A few good places to start:

      On the book front, must-reads include: Designing with Web Standards by Zeldman, Eric Meyer on CSS and More Eric Meyer on CSS, and Dan Cederholm's Web Standards Solutions.

      Also, Veerle Pieters has a very useful hyperlinked PDF of CSS resources; the associated blog page has more details.

      That lot should get you started :-) Hope that helps.

      But be warned: like you I'm a hard-core, long-term technical bod, who's done everything from embedded systems software to web development, and it's only after 3 years, absorbing everything I could learn about CSS in theory and practice, and particularly how to conquer the Great Satan IE, that I've finally got to the point I referred to in my original post. To be perfectly honest, I couldn't believe it when I only needed 13 lines of hacks to tame IE on a very complex design.

      So when you start, the best bit of advice I can give you is: code and test to Firefox first. If something looks a bit off, check it in Opera 8, and in Safari if you have access to a Mac. Once you've got it working across those three, everything that goes wrong in IE is IE's fault, not yours. That's when you start applying the hacks found at Position is Everything and other places, until IE finally falls back into line.

      It's not as bad as it seems; if you have the kind of logical mind that goes with writing code, you'll soon begin to discern the patterns underlying IE's peculiar behaviour. (Virtually everything can be tamed using the Holly Hack, explained at Position is Everything, linked above.)

      Good luck, and Enjoy :-)

      --
      Using HTML in email is like putting sound effects on your phone calls. Just say <strong>no</strong>.
    14. Re:Fortunately by NickFitz · · Score: 1

      A bit hackish, but try:

      html, body {
      --
      Using HTML in email is like putting sound effects on your phone calls. Just say <strong>no</strong>.
    15. Re:Fortunately by NickFitz · · Score: 1

      Damn, must remember the Tab key moves me to "Submit" :-)

      Take 2:

      Assuming you just have a page containing an image having id="myImage" try:

      html, body {
      height: 100%;
      min-height: 100%;
      }

      #myImage {
      position: absolute;
      top: 50%;
      left: 50%;
      margin-top: -25%;
      margin-left: -25%;
      }

      (Or something like that.) Have a look at Centering Block Element on the css-discuss mailing list wiki.

      --
      Using HTML in email is like putting sound effects on your phone calls. Just say <strong>no</strong>.
    16. Re:Fortunately by arkanes · · Score: 1
      See, you're a liar. I do this for a living as well, and I make a lot of money at it. There is no way to get 100% feature parity between IE and Firefox. If you're willing to spend a fair amount of time on IE behaviors, DHTML, and maybe some ActiveX controls, you can get pretty close, but then we're far beyond the realm of what you can with CSS (and you'd have spent a lot less time on a Flash site), and that doesn't address the stuff that Firefox does wrong that IE does right (although I can only think of one example off the top of my head).

      If your site renders identically on IE and Firefox (to the pixel, no less!), and you're not using any browser specific markup or sniffing tricks, then you are using a minimal subset of CSS. Anyone who claims anything else is lying. Here's a short list, inspired by what I've been doing in my own work in the last couple days, that you are not using:

      • position: fixed
      • input type="file" with styling. Firefox applies styles poorly/not at all to this control.
      • the table-layout attribute and the related display attributes, like table-cell and table-row
      • The fieldset tag, sort of - you can't get Firefox to mimic the IE default display, but you could change them both to some third value. Which reminds me, I should file a bug for anti-aliasing of rounded borders.
      • The overflow element applied to a TBODY. So annoying!
      And then of course theres the various IE extensions, as well. So you aren't using overflow-x or overflow-y, either.

      All this presumes you're only supporting IE 6, too. If you're supporting earlier versions, like IE 5 and 5.5, then theres a lot more things you aren't doing. This all comes under option A.

    17. Re:Fortunately by Anonymous Coward · · Score: 0

      >> Of course, you wont be able to support browsers like Netscape 4, but come on folks, this is 2005. Anyone still using browsers like that is an idiot, and likely wont even notice that the CSS isnt displaying correctly.

      If you use @import to call the CSS file, then NS4 will get completely unstyled content; and that content will be very fast loading as it will contain only basic HTML blocks, no cruft.

    18. Re:Fortunately by zobier · · Score: 1
      Is this what you mean with the fieldset?:
      <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
      "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transition al.dtd">
      <html xmlns="http://www.w3.org/1999/xhtml">
      <head>
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
      <title></title>
      <style type="text/css">
      <!--
      fieldset {
      -moz-border-radius: 5px;
      }
      legend {
      color: blue;
      }
      -->
      </style>
      </head>
      <body>
      <form action=".">
      <fieldset>
      <legend>fieldset</legend>
      <input /><button>button</button>
      </fieldset>
      </form>
      </body>
      </html>
      I suggest not using blue for the legend tho'.

      Also I have managed to get scrollable table bodies working the same in ie && ff but it's pretty dirty.

      --
      Me lost me cookie at the disco.
    19. Re:Fortunately by arkanes · · Score: 1
      Gecko, at least in my build of firefox, renders -moz-border-radius with an ugly unaliased curve. In the small border that matches the IE one, its nasty and jagged. By the way, you forgot to change the border-style to line - it's rendered as groove (or ridge? I forget) by default

      And yeah, scrollable table bodies in IE is a mess. It's pretty easy if you can set explicit column widths, but if you want to keep the self-sizing columns then it's a ton of nasty, nasty, DHTML work. In mozilla it's trivial. I cried like a baby when I saw how easy it was, after spending several days implemented an imperfect solution for IE.

    20. Re:Fortunately by Nurf · · Score: 1

      Thanks!

      --
      ---
  68. Konqueror by AskMeLater · · Score: 0

    Slashcode.com totally barfs while using konqueror. I tried all available stylesheets, but no luck. Of course, I can barely get the page to load at this point.

  69. Too many IE users to not work around IE bugs. by hellfire · · Score: 5, Insightful

    Allow me to list people who would be denied the goodness of slashdot if you didn't create something that allowed IE to be compatible:

    1) People who for some stupid reason or another can only use IE at work and don't have enough control of their PC to install something better.
    2) Geeks and nerds who do not fall into the category of computer nerd. There are science geeks, english geeks, political geeks, math geeks, but just because one is a geek about one thing doesn't mean they are geek about computers.

    I'm all for scolding IE for not complying to standards, but since MS's philosophy of embrace, extend and extinguish is still in use in IE, don't allow yourself to be extinguished by designing a page that doesn't work around I.E. bugs and cut off major portions of your audience.

    --

    "All great wisdom is contained in .signature files"

    1. Re:Too many IE users to not work around IE bugs. by Geshem · · Score: 2, Insightful

      3) Geeks and nerds who prefer IE although knowing what there is to know.

      Yes, I use IE even after reading most of what people has to say about the subject.
      I don't mind the security issues that much, since I don't surf to pr0n and crackerz sites. Also, it's not like Firefox is completely bugless. De-Facto, I'm using IE as my browser for several months now without any spyware/trojans on my comp.

      As for why not use Firefox? It takes too much time to load, and it's too heavy on the memory (I actually like to have other programs running along with my broswer, thank you)

      --
      || Geshem ||
    2. Re:Too many IE users to not work around IE bugs. by LWATCDR · · Score: 1

      "2) Geeks and nerds who do not fall into the category of computer nerd. There are science geeks, english geeks, political geeks,"
      The science geeks can stay. If we where free of the english and political geeks....

      I have to say that point two doesn't see logical to me at all. My wife is on a scrap-booking forum and lots of them use Firefox! I would think that anyone that visits Slashdot is capable of installing Firefox.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    3. Re:Too many IE users to not work around IE bugs. by ruiner13 · · Score: 1

      What we need is an ActiveX control for IE which will let you run firefox inside of IE.

      --

      today is spelling optional day.

    4. Re:Too many IE users to not work around IE bugs. by hellfire · · Score: 1

      If it doesn't make sense to you that a person highly intelligent about some subject such as astronomy could be completely computer dumb then you are assuming that everyone who reads slashdot is only here because they are linux geeks who do heavy coding. Slashdot is "news for nerds" but my point is not everyone who reads slashdot is computer savvy, even if they read every firefox posting here. Some are more interested in the social and scientific articles which barely scratch upon computer and technical areas.

      --

      "All great wisdom is contained in .signature files"

    5. Re:Too many IE users to not work around IE bugs. by LWATCDR · · Score: 1

      Dude the people on the forum my wife visits are women that cut out cute shapes of paper and use them to decorate pictures of their kids!
      These are not Linux geeks that do heavy coding! You do not have to read every Firefox posting to know what Firefox is.
      The only valid reasons I see for supporting IE at this time are.
      1. Some people may not have the option to install software.
      2. Some people may not have a broadband connection so downloading Firefox may take too long to be practical.
      3. I do not know but is there a standard compliant browser available for WINCE and Palm devices? I know that WINCE has IE.

      IMHO by default Slashcode should support nothing but standard CSS. If a browser is detected that does not follow the standards it should be redirected to a functional even if not full featured page that uses the subset of standards that browser supports.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    6. Re:Too many IE users to not work around IE bugs. by tepples · · Score: 1

      Some people may not have the option to install software.

      Other than people surfing the Internet in a public library, should these people be viewing entertainment web sites on company time anyway?

      Some people may not have a broadband connection so downloading Firefox may take too long to be practical.

      Firefox Setup is 4.7 MB. Most dial-up Internet connections are v.90 or v.92, which can download a file that size in 20 minutes. How is that impractical?

      I do not know but is there a standard compliant browser available for WINCE and Palm devices? I know that WINCE has IE.

      Opera for Mobile is out now on all these phones, and a port of Mozilla to handheld devices is being worked on (see Minimo roadmap).

    7. Re:Too many IE users to not work around IE bugs. by LWATCDR · · Score: 1

      "Other than people surfing the Internet in a public library, should these people be viewing entertainment web sites on company time anyway?"
      They may be doing it on there lunch hour or on a break, at school during free time, or at an Internet Cafe.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
  70. slow load time by Anonymous Coward · · Score: 0

    Is it just me or slashcode takes ages to load?
    tested on firefox 1.0.6 and IE6.

  71. Doesn't validate by StonedRat · · Score: 0

    While it's a huge improvment over the current slashdot code, it still doesn't even validate. at least not using the coral cached version:

    http://validator.w3.org/check?verbose=1&uri=http%3 A//www.slashcode.com.nyud.net%3A8090/

    --
    "Religion is the most malevolent of all mind viruses." - Arthur C. Clarke.
  72. Be Careful! Re:css!! by CDMA_Demo · · Score: 1

    Once some of us start testing the CSS seriously we'll be greeted with messages like "Please don't bother us for 72 hours"!!! Are you sure you want everyone on Slashdot to test the CSS yet?

  73. Well, surprise! by Z00L00K · · Score: 1
    /code just got /.:ed!

    Anyway, it seems to be a good idea, I hope that the coders take help from the HTML Validator and the CSS validator!

    Both tools are very useful to track down bugs in web page construction. Even if the warnings sometimes seems to be ridicolous or stupid they actually serve a purpose. Current /. is working OK in most browsers, and I hope that the new one also will be as good.

    Otherwise - I think that /. is a wonderful forum, even though it sometimes seems to be a bit limited. It's a tough balance between being able to maintain freshness and being able to feed information in a reasonable volume. There are branches of /. today like the politics, hardware and IT, but some posts may actually fit on a branch even though it isn't displayed on the main page. Same goes fr the polls, why not a politics poll on the politics server?

    --
    If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
  74. Re:Sorry for being a luddite but.. by Anonymous Coward · · Score: 0

    ... who cares about CSS? Slashdot works and it works well. It aint broke so why fix it?

    Even if you ignore all the other benefits, this will save large amounts of bandwidth.

    I'm not interested in flash pages and fancy fluffy layouts and all that other crap that comes along with site "upgrades"

    You might have noticed that "CSS" and "Flash" are spelled differently. That's because they are different things. If you think CSS and Flash are the same thing, you're not qualified to comment on this.

    I just want to be able to read articles and comments. Period.

    Since this will use less bandwidth, you'll be doing this faster than before.

    Seriously, what's your beef with CSS?

  75. it would help by Anonymous Coward · · Score: 0
    if the server was actuly running...

    (master@laptop) (~/tmp)-$ nc -vvv www.slashcode.com 80

    DNS fwd/rev mismatch: www.slashcode.com != slashcode.com

    www.slashcode.com [66.35.250.197] 80 (www) : Connection refused

    sent 0, rcvd 0

  76. Re:MOD PARENT UP by StonedRat · · Score: 1

    And the current scripts to do this will likely break once the new code is in place.

    --
    "Religion is the most malevolent of all mind viruses." - Arthur C. Clarke.
  77. Re:Finally, Slashdot Slashdotted, Literally! by loconet · · Score: 4, Funny

    Add to that the fact that Slashdot is moving to css, Apple using Intel, Apple Shipping 2 Button Mice, Debian 3.1 was released and this year seems to be turning into be the pivotal point for hell to hold the winter olympics.

    --
    [alk]
  78. OMG! by Comatose51 · · Score: 2, Funny
    What have the editors done!? They posted a link back to Slashdot so now they're going to Slashdot Slashdot and create a Internet blackhole where the same articles get posted over and over again!

    I kid, I kid.

    --
    EvilCON - Made Famous by /.
  79. Performance by DoofusOfDeath · · Score: 1

    I tried to view the CSS version, but it was Slashdotted!

    (I'm joking and serious.)

  80. Bug report by naspa · · Score: 1

    Yup, slashdotted already!

    Self referencing pointer: slashdot slashdots itself into the blackhole of infinite loop.

  81. Don't like it? by Anonymous Coward · · Score: 0

    Then change the default font in your UA!

    1. Re:Don't like it? by Carewolf · · Score: 1

      He is talking about the CSS version. He is obviously not using Firefox or other Netscape browsers defaulting to Serif.

      In case you've tested the CSS in a Serif default browser you will noticed a very tine Times New Roman fonts

  82. CSS Yeah Yeah... by lxs · · Score: 1

    What we really want is SlashFlash! With animated buttons, swooshing sounds and banners about a deranged amphibian imitating some kind of motor vehicle.

    1. Re:CSS Yeah Yeah... by Fyuocuk · · Score: 0

      You've got mail! Check out my journal! You win! Congratulations!

  83. From the css article? by aweiland · · Score: 1

    Is this the result of the article from a while back (I don't have the link) where a guy redid the slashdot front page using proper (x?)html/css positioning?

    It was well done and a good example on how to properly do something like this.

  84. did hell just freeze over? by bdigit · · Score: 1

    or have my eyes decieved me? Say it ain't so taco? You are actually listening!? What next a dupe checker?

  85. Re:MOD PARENT UP by VJ42 · · Score: 2, Informative

    An (almost) comrehnsive list of greasemonke\slashdot user scripts.:
    http://dunck.us/collab/GreaseMonkeyUserScriptsSpec ific#head-ec4846dd1f06f8efd2d256a59577b3faaebbbf12

    --
    If I have nothing to hide, you have no reason to search me
  86. awesome by Suppafly · · Score: 1

    if only slashcode wasn't slashdotted so I could test it out.

  87. I'm getting the hacks ready... by Regnard · · Score: 1

    Seriously, I haven't seen the new template but I hope the CSS will stick to basic stuff.

    --
    Need a color? Try 100 random colors
  88. Dead Domain? by Anonymous Coward · · Score: 0

    The link doesn't work for me...

  89. hmm... by XO · · Score: 1

    looks like it's slashdotted. odd.

    Works fine in Opera, by the way.

    --
    "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
  90. This will allow us to save Slashdot from itself! by aftk2 · · Score: 1

    I'd like to join the multitude welcoming Slashdot into 2005 (hell, welcoming Slashdot into 2002/2003, actually) and give them all at a pat on the back.

    What's the biggest boon of this change? Custom stylesheets. When Slashdot's IT theme debuted, it was met with much scorn and derision, and rightfully so. A number of solutions appeared, including mine, which was a JavaScript bookmark that redirected the user to the same article, but using hireadesigner.slashdot.org as the URI, thereby removing the hideous pseudo-tan.

    Well, now we won't have to worry about that. We can whip up a custom stylesheet, and apply it, and we're done, with much less effort than attempting to use a custom stylesheet to modify Slashdot's current bevy of table cells and nested font tags.

    While you're out there, Slashdot admins, why not add in the ability for us to define a custom stylesheet, and save it in our user profile? I know browsers will do this, but do most browsers have per-site custom CSS stylesheets? Give us some options.

    At any rate, that's a minor feature request. Thumbs up, Slashdot.

    --
    concrete5: a cms made for marketing, but strong enough for geeks.
  91. Will it look like Google? by joelsanda · · Score: 1

    Once we move Slashdot, work will begin on a new look & feel.

    Will the new UI look just like Google's?

    --
    The Luddites were ahead of their time.
  92. Re:Sorry for being a luddite but.. by Cid+Highwind · · Score: 1

    Slashdot works and it works well.

    No, it doesn't, at best it works sorta okay most of the time.

    Any website where reloading the front page repeatedly gives you different layouts each time is fundamentally broken. Search for "slashdot" in bug reports at bugzilla.mozilla.org, and look at how many mozilla/firefox "bugs" are caused by slashdot's invalid HTML.

    --
    0 1 - just my two bits
  93. It's been done by 7x7 · · Score: 1

    Two years ago A List Apart ran an a set of articles where they did this exact thing.

    Part 1 Part 2

  94. Slashdot stats by Anonymous Coward · · Score: 0

    Where can we find slashdot stats. How many users use each platform and how use each browser?

  95. Excellent! by Cloud+K · · Score: 1

    Works great on Opera (styled and unstyled) which is a definite good sign.

    Kudos to Slashdot for finally embracing the type of web design that puts the *user* first instead of the webmaster. Sure, it can be a little fiddly to get things looking right with CSS especially if you try to mimic tables with it (which you have to do if you want to validate to Strict, IIRC) but in the long term it makes the site a *lot* easier to maintain and more user friendly.

    For those unsure of the benefits of using either HTML4.01 Strict or xHTML1.0 Strict (better) some of them I can think of are:

    - The data is separate from the presentation. This means that disabled users, people with screen readers etc are happier as they can view the site in a way that's accessible to them instead of the way the author dictates. It also means benefits for non-disabled users who can view the site in reduced functionality web browsers, PDAs etc just by overriding the CSS template, or design their own "skins" etc.

    - It makes updates (e.g. adding a link) far easier as there is *no* style code in the HTML - it's generally just a matter of adding another LI or DIV tag with the appropriate class and the CSS will do the "make it pretty" bit.

    - Nicer on bandwidth

    - If you validate to both (which I hope gets done) then you have a very good chance of the site working and looking the same on all decent web browsers including IE.

    - You show that you care about your users. Providing you validate it and run it through webxact as well.

    1. Re:Excellent! by Ahnteis · · Score: 1

      Tables can still be used for tabulated data.
      The difference is that tables aren't to be used for page layout.

  96. Dupes by Anonymous Coward · · Score: 0

    How about adding a feature to prevent dupes from apearing on the main page?

    For that I would buy a subscription :)

    1. Re:Dupes by mdecarle · · Score: 1

      A javascript to contract part of the comments would be nice. Sometimes, we see people comment on the way their sister painted her toenails yesterday, and there's a complete thread about that. Usually though, I want to see replies to a certain posting, and I have a lot of trouble finding them.

    2. Re:Dupes by mdecarle · · Score: 1

      Actually (yes, I reply to myself), there's agood example.

      Today, I find a post about comparing MySQL with PostgreSQL. Could be an interesting read, except that the first post is about SCO (sigh).

      So, there's screens of blabber about a recent deal between MySQL AB and SCO (Inc. ?). I'ld like to be able to click a little square with a minus sign in it, so I don't need to read that crap.

  97. Standards Problems by Oculus+Habent · · Score: 3, Insightful

    I discussed this with a friend some six years ago. The problem with standards like HTML and CSS can be summed up in one word:

    MAY

    By putting the word may into a standard, you make the standard non-standard. If you can't reliably depend upon CSS to render a dashed line on a border, why do you even provide it? Two completely compliant browsers can give you a different picture, depending on their choice to implement optional components.

    There are enough issues with non-compliant browsers that we don't need to build issues into the standards!

    --
    That what was all this school was for... to teach us how to solve our own problems. -- janeowit
    1. Re:Standards Problems by Haeleth · · Score: 5, Insightful

      If you can't reliably depend upon CSS to render a dashed line on a border, why do you even provide it?

      Do share: just how do you propose to get a blind user's screen reader to render a dashed line on a border?

      Wait, wasn't that what you meant? Oh dear, it looks like you're going to have to concede that you don't actually want CSS to guarantee anything of the sort, doesn't it?

      Two completely compliant browsers can give you a different picture, depending on their choice to implement optional components.

      Oh lord, you're not another of these clueless people who think that the idea of CSS is to make sure sites look identical everywhere, are you?

      The fact that two completely compliant browsers can produce totally different results is a feature. You might want your website to have green text on a red background in letters five pixels high, but if I'm nearsighted and colourblind, I damn well don't want my browser to render it that way! As a less extreme example, you might want your site to be laid out in three vertical columns, but if I'm browsing it on a mobile phone, I sure won't object if my browser decides to render it as one column instead.

      Pixel-identical rendering? You can keep it. I want to use fonts I can read, colours I can stand, layouts I can navigate. CSS lets me do all that just by providing my own stylesheet. You know, I'm really not terribly unhappy with that.

    2. Re:Standards Problems by Ulven · · Score: 1

      You miss the point. The GP isn't saying that you being able to override his stylesheet is a bad thing. He is saying that if the CSS calls for a dashed line, that is what a browser should render. (User stylesheets, mobiles phones, text browsers etc apart) If I code a standards compliant site and look at it in FireFox, Opera and IE then it should look the same in all of them. Not have the same line dotted, dashed or solid, depending on what the developers thought was best.

    3. Re:Standards Problems by Shaper_pmp · · Score: 1

      Yes. Yes. Yes. Yes. Yes.

      Can I come and work for you? <:-)

      By bosses think HTML is an alternative for Photoshop (for advertising material/graphic design), or for Visual Basic (for user-interfaces). They just can't seem to get their heads around the idea that you produce the content, and let the user-agent decide how best to display it - as far as they're concerned, they'd rather shut out a significant proportion of their userbase, simply to allow them to specify designs down to the pixel.

      And I'm not joking about the Visual Basic (multi-million pound company, and half of our products are written in VB <:-) - they want pixel-perfect positioning (which is no joke when designing to standards and supporting IE). The entire company seems to view X/HTML/CSS's variability as a source of annoyance, rather than its single most important feature.

      Just last week I had to take a carefully-designed flow-layout page and recode the CSS to make it fixed-width, absolute positioning, at 1024x768 pixels wide.

      Why? Because the Director of Customer Support has a large monitor, and didn't like the fact re-flowed (to keep everything on the screen!) when people browsed in smaller windows. When I pointed out that, although the page wouldn't re-flow for anyone running at a resolution under 1024x768 (>25% of our userbase), it would mean they have to sideways-scroll every time they reached theend of a line. His answer: "Yeah, well, frankly we don't care about selling to anyone running smaller resolutions than mine". Odd, I thought we wanted to sell to anyone who'd buy... but I guess that's why he's the Director and I'm the guy on probably a third of what he's earning...

      And why was the Director of Customer Support involved in a marketing website decision? It's just that sort of company.

      --
      Everything in moderation, including moderation itself
  98. Re:Finally, Slashdot Slashdotted, Literally! by bhtooefr · · Score: 1

    On a more serious note, I think Jon Katz wrote some articles that drew enough attention to /. that it took /. down...

  99. Ludicrous by eruanno · · Score: 0

    That notion is fine and all in an ideal world, but you must understand that we're nothing close to ideal. Though it would be great for all websites to be developed using standards, forcing browsers to conform, this just isn't the case. For example, look at IE -- need I say any more?

    What mankind ought to do and what we actually do aren't necessarily the same.

    Just try to think outside of the ideal and into reality. Even the most creative poet must think realistically when he needs to find a pencil and paper to write his creations down on.

    M.T.

    --
    "Support Bacteria - Its the only culture some people have" - Circa 1985
  100. Slashcode is Tango Uniform by still+cynical · · Score: 1

    Did someone forget to give the gerbils powering Slashcode some Mountain Dew before this was posted?

    Clearly a case of the right hand not knowing which foot the left hand is shooting.

    --
    Ignorance is the root of all evil.
  101. Coral Cache by hummassa · · Score: 1
    --
    It's better to be the foot on the boot than the face on the pavement. ~~ tkx Kadin2048
  102. Frontpage? by Anonymous Coward · · Score: 0

    A lot of the innovation (thanks to ... Frontpage) has happened on the Windows platform ... [and] can be accomplished in minutes by any decent Windows admin.

    Innovation... hohohahaha...

    Frontpage... heeheehahaha...

    Decent Windows admin... WOOHAHAHAHAHAHAHAAAAA...

    +5 Funny!

  103. wow! by dep01 · · Score: 1

    Goodbye 8-track, hello cassette!! Welcome to 1998, Slashdot!

    --
    "hey, could you pass me a paper towel? er.. I mean... DEPLOY ABSORBTION PANEL!"
  104. Put indexes at bottom of document please by La+Gris · · Score: 1

    But blind / partially sighted

    who uses Braille or Speach would much appreciate if, navigation, sponsors and other indexes, except the last comment summary, went to the bottom of the html document.

    This would avoid having to skip all the same j^H^Hk common indexes sequentially to reach actual news and comments.

    --
    Léa Gris
  105. Congratulations on your wasted effort by ackthpt · · Score: 1
    Of course I know what HTML is. I was trying to be funny (appearently wasted effort). The joke is that HTML is old. For slashdot to only be using HTML makes it old. Something so old that people forgot about it.

    Not exactly funny. I still do development to a 3.2 specification whenever practicable. For a large site, such as slashdot.org it makes sense to be moving to CSS based code, but for many of the smaller sites I develop, some of which are application generated, I find developing a CSS for each to be a pain in the tuckus and beyond the needs anyway. I once worked on a CSS which was bigger and more unwieldy than I was happy with, and some changes meant revisiting the HTML side to redesign (very painstaking work.) If you want to set up simple pages and worry not about what's impacted by changes to a CSS straight HTML works very well. Remember, Keep It Simple, Stupid.

    Oh nevermind.

    I believe the proper phrase is 'Oh, bugger!'

    --

    A feeling of having made the same mistake before: Deja Foobar
    1. Re:Congratulations on your wasted effort by goldspider · · Score: 1
      "I once worked on a CSS which was bigger and more unwieldy than I was happy with, and some changes meant revisiting the HTML side to redesign (very painstaking work.)"

      The fundamental reason for CSS is to separate structure and display. I suspect that if you had to modify HTML to correct display issues, then you hadn't completely separated structure (which belongs in HTML) from display (using CSS).

      Granted, migrating a non-compliant site to compliant HTML/XHTML and CSS can be tedious and frustrating (I'm going through the same with my personal site), but in the end you will have much better code, and future re-designs can be done entirely in CSS with much less effort.

      --
      "Ask not what your country can do for you." --John F. Kennedy
    2. Re:Congratulations on your wasted effort by ackthpt · · Score: 1
      he fundamental reason for CSS is to separate structure and display. I suspect that if you had to modify HTML to correct display issues, then you hadn't completely separated structure (which belongs in HTML) from display (using CSS).

      Try a fickle user. Constant change meant revisiting both, which was one of the reasons for the CSS becoming such a fiasco.

      --

      A feeling of having made the same mistake before: Deja Foobar
    3. Re:Congratulations on your wasted effort by dave1212 · · Score: 1

      I'm very sympathetic to this issue.

      Clients can drive you nuts with multiple changes. (things they should have thought about in the first place)

      One thing I did o get around that was to establish a set number of changes allowed once the final design was signed off on per month, and charge for any changes over and above that amount.

      It's hard enough to get them to decide when it's up to their idea of what it should look like.

  106. Re:huh? (that's a GREAT IDEA!) by bad_outlook · · Score: 1

    No kidding, if we had something like this, geeks could 'choose' what CSS they wanted Slashdot to display with, and set that in their prefs. I for one would love a nice, modern but MINIMAL Slashdot site. Yes there would have to be limits on what could be done, as ads would need to be part of the CSS, but that could be handled by anyone who would checkin the CSS and make it avail for users via their own prefs. I like this idea allot!

  107. Useful style by edson+at+lies.cl · · Score: 0

    .dupe { visibility:hidden }

    --
    i have found, you can find,happiness in slavery!
  108. Will it work in Linux? by LordJezo · · Score: 0

    Any plans on releasing a Linux version or is this going to be yet another Windows only update?

  109. Rounded Corners by jaycontonio · · Score: 0

    Instead of using images for your rounded corners, why not adopt part of css3 early and use the border-radius [webkit] property? It's only supported in safari so far but once the rest of the browsers adopt this it will shave a lot of images off the site, therefor, speeding it up a bit. Plus they look so damn good!

    1. Re:Rounded Corners by handslikesnakes · · Score: 1

      Gecko has -moz-border-radius, and I think that Opera might have -o-border-radius.

  110. 503 Unavailable by nacturation · · Score: 1

    And also keep in mind that you can't fix slashdot's server-side code/configuration using CSS.

    --
    Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
  111. Just CSS?!?! by fbg111 · · Score: 1

    We want AJAX, RIA, and Web 2.0, you insensitive clods!

    --
    Flying is easy, just throw yourself at the ground and miss. -Douglas Adams
  112. Slashdot skins by scovetta · · Score: 1

    Why doesn't /. try to implement a few buttons at the top right hand corner of the screen (and maybe a drop-down) to on-the-fly choose another skin? And maybe remember my setting too.. I'd like to see cleaner fonts and some other things, and instead of writing my own stylesheet just for me, it'd be neat to just click the "Scovetta's Stylesheet" button and have it switch over.

    Just my $0.02. I think the new page looks great. I'm looking forward to Duke Nukem Forever coming out next week.

    --
    Wer mit Ungeheuern kämpft, mag zusehn, dass er nicht dabei zum Ungeheuer wird. --Nietzsche
  113. Re:Sorry for being a luddite but.. by bhtooefr · · Score: 1

    Hmm...

    Testing the Opera SSR mode (which enables any mobile stylesheets the site has) on Slashcode doesn't give a page that looks any different from Slashdot in SSR mode.

    This is important, as AvantSlash is shutting down (due to breakage, and apparently there won't be a need for it) when Slashdot rolls out CSS. http://slashdot.org/palm is a pathetic excuse for a AvantGo version of Slashdot. And, the CSS version doesn't have a mobile stylesheet, with information hiding so that only the relevant parts show up, so it'll be just as bad as regular Slashdot.

    So, will I have to fork AvantSlash when Slashdot changes to CSS? I hope not...

  114. Re:Finally, Slashdot Slashdotted, Literally! by iluvcapra · · Score: 3, Funny

    Here we are at the apocalypse, and we still never got to play Duke Nukem Forever.

    Yeah, I went there.

    --
    Don't blame me, I voted for Baltar.
  115. Put content first! by iamcadaver · · Score: 1

    Please, before another 8 years go by, put the stories just after the title. This makes it much less aggravating for cell phone and PDA browsers. Not to mention text browsers like 'links' which is my second favorite /. browser out there.

    You can still position everything just fine with CSS for graphical browsers, they won't see a difference. But for text browsers, users won't have to hit Page Down forty times before getting to the first story.

    --
    Before I part with'em: two pennies weigh ~4.996+/-0.014g, have a zinc core, and the face of Lincoln. You can keep 'em.
  116. Netscape Communicator 4.7x by Anonymous Coward · · Score: 0
    As long as this site remains legible in Netscape Communicator, either with or without CSS (I usually disable Javascript altogether anyway), that's fine with me. The "other" browser at work is definitely not an alternative.

    I'll be more than happy to test Netscape's compatibility.

  117. Folks, just admit defeat here, OK by melted · · Score: 1

    digg.com rules.

    1. Re:Folks, just admit defeat here, OK by focitrixilous+P · · Score: 1
      Alright, I've seen the digg link a few times, and I want to respond.

      Digg is not better than /.

      If you think /. is a google and apple wank-fest, try digg. Currenty on the front page (among others) is a MySql vs Postgre flamewar, a DS vs PSP flamefest, the google search rack story that's on /., a seagate ad, and a google nonstory.

      Plus the comments are non-threaded which makes discussion difficult, and the average number of comments is 10 to 20, half of which are one liners, and the other half are hideously unreadable. 2 or 3 of the comments are insightful. Even the trolls aren't as good at digg.

      That said, Digg is now on my bookmarks toolbar. I don't comment much, but it's alright for when /. is 503 or I've read all the stories already.

      --
      SAILING MISHAP
  118. Lynx mode? by Pegasus · · Score: 1

    CSS? That sounds like some modern buzzword. Lynx mode is still the best way to read slashdot on my trustworthy VT320.

    I wonder, is it going to stay?

  119. *Ahem* by Anonymous Coward · · Score: 0

    Slashdot slashdotted slashdot.

  120. sniff by Kuku_monroe · · Score: 1

    I already miss the old slashdot...

    --
    //WR
  121. Re:Sorry for being a luddite but.. by XO · · Score: 1

    I like to view slashdot through the "Nostalgia" Opera CSS mode. It makes it all look like a beloved Commodore 64.

    --
    "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
  122. Microsoft tactics by tehshen · · Score: 1

    Putting off features people have wanted for years, only to add them when people start going elsewhere... Hmm, didn't we attack Microsoft for doing this?

    --
    Guy asked me for a quarter for a cup of coffee. So I bit him.
  123. In other news... by nsasch · · Score: 1

    Duke Nukem Forever has come out.

    --
    Make your computer faster: rm -rf /mnt/windows/
  124. Why not XSL? by Bin+Naden · · Score: 1

    Why isn't slashdot migrating to XML coupled with XSL? It's the future afterall!

    --
    There should be a "-1:Groupthink"
  125. Let me use Sans fonts by Tester · · Score: 4, Interesting

    Using the layout as slashcode, it seems that the font is specified to be Serif everywhere... I much prefer to read on-screen stuff with a sans font, which is my default. Please dont specify the font and just use my browser's default... Please remove "font-family: serif;" from the body{}

    Thank you,

    Tester

    1. Re:Let me use Sans fonts by hackstraw · · Score: 2, Interesting

      Please dont specify the font and just use my browser's default... Please remove "font-family: serif;" from the body{}

      I guess that is a valid request, but you are in the minority, and slashdot actually does fonts "correctly".

      For most people, a proportionally spaced serif font is easier to read for the body of a document, and a proportionally spaced sans-serif font is better for thing like headlines or section titles. However, after just typing that I went to a number of popular news sites, and they use sans-serif fonts everywhere.

      Is my font data only applicable to printed text and not text displayed on a screen? Personally, I'm a fan of the way slashdot does their fonts (in the right browser :)

    2. Re:Let me use Sans fonts by SpamJunkie · · Score: 2, Insightful

      If this is actually important to you use a browser that can override specified fonts.

      Thank you,

      Everyone else

    3. Re:Let me use Sans fonts by Psiren · · Score: 2, Interesting

      For most people, a proportionally spaced serif font is easier to read for the body of a document, and a proportionally spaced sans-serif font is better for thing like headlines or section titles.

      That's generally true for print, I'm not so sure about on screen reproduction (anyone care to offer any case studies?). The theory is that the serifs are supposed to help guide your eye, so it's easier to see what the letter is. However, given the relatively low resolution of screens, it doesn't seem to work as well for me. I certainly prefer serif fonts, and have told my browser to always override the font to my own preference.

    4. Re:Let me use Sans fonts by Sartak · · Score: 1

      Isn't the ability to change the layout of a page one of the driving forces behind migrating to CSS? If you don't like the font, just use your own stylesheet.

    5. Re:Let me use Sans fonts by TeknoHog · · Score: 1
      You can always choose 'Light' from the preferences, to give a simple layout which uses your default font. I use this, as the usual Slashdot layout is utterly unreadable IMHO.

      I think some browsers can override the CSS with your own version, which is why the CSS version of Slash is quite interesting.

      --
      Escher was the first MC and Giger invented the HR department.
    6. Re:Let me use Sans fonts by Cyno · · Score: 1

      For most people, a proportionally spaced serif font is easier to read for the body of a document, and a proportionally spaced sans-serif font is better for thing like headlines or section titles.

      I'm curious how you came to this conclusion. Can I see your data?

    7. Re:Let me use Sans fonts by Cyno · · Score: 1

      I prefer to use alterslash.org. Its had sans-serif fonts and an rss feed of slashdot for years.

      If I dislike something I usually find an alternative instead of requesting changes.

      If ( they really want my page views ) { they'll ask me what I want. } else { I just assume they don't care. }

    8. Re:Let me use Sans fonts by Just+Some+Guy · · Score: 1
      Is my font data only applicable to printed text and not text displayed on a screen?

      At least one source gives the opposite advice for screen displays (but recommends your scheme for printing). The general consensus among the web designers I've talked to is serif for headlines, sans- for the body.

      --
      Dewey, what part of this looks like authorities should be involved?
    9. Re:Let me use Sans fonts by hackstraw · · Score: 1


      I studied fonts and other silly stuff when I was in "Human Factors Engineering". Sorry, I didn't keep my notes for the citations, but I explicitly remember reading that and it is very common to find the serif - sans-serif motif used in print like newspapers, books, and magazines.

      Actually, I made it all up.

    10. Re:Let me use Sans fonts by Yakman · · Score: 1

      I hope they keep "Light" mode in the new interface. Everytime I go to someone elses PC where I'm not logged in and look at /. I can't stand looking at the "full" design.. it's just so "heavy" :)

    11. Re:Let me use Sans fonts by TeknoHog · · Score: 1

      One great thing about CSS is that when you take it away, you're left with a 'Light' page. At least when it's designed sensibly. For example Wikipedia looks and works great in non-CSS browsers, just like the 'Light' Slashdot.

      --
      Escher was the first MC and Giger invented the HR department.
    12. Re:Let me use Sans fonts by Naikrovek · · Score: 1

      that's what user stylesheets are for, so you can override a site's formatting.

      the styles CASCADE down from the page to your browser, taking new styles on the way. the first "c" in css stands for "cascading".

      create a user stylesheet and tell your browser to use it.

  126. Konqueror and Firefox on FreeBSD 5.4 by WgT2 · · Score: 1


    Both browsers display the code without a problem. I personally think Konqueror's display looks better. Perhaps because of the text in the lower right hand column when viewed in Firefox: the titles look too big..

  127. Move content to top of output... by Orrin+Bloquy · · Score: 2, Interesting

    ...and use CSS to reposition the sidebar/navbar content below it. Half the point to using CSS for accessibility is to avoid going through navlinks at the beginning of every page. I hear these guys managed it across their site without compromising performance in IE 6 or spectacular hacks (and yes, it was tested in IE, Safari, Firefox, Opera and Konqueror).

    For the curious, the left and right navbars are absolutely positioned and the central content has left/right margins which mimic their width, to achieve the same liquid layout.

    The HTML4.0 thing is bullshit, plain and simple. Authoring tools like Dreamweaver work better when working within XHTML spec, just lose the XML prolog until The Brave New World of XML-parsing UAs is here and we can stop serving text/html. XHTML1.0 Transitional plays nice with every UA I've tested, from Netscape 4.7 up.

    --
    "Made up/misattributed quote that makes me look smart. I am on /. and I must look smart."
    1. Re:Move content to top of output... by IpalindromeI · · Score: 1

      The HTML4.0 thing is bullshit, plain and simple. Authoring tools like Dreamweaver work better when working within XHTML spec

      In case you weren't aware, they aren't using "authoring tools" to produce Slashdot's pages. It's generated by code on the webserver. They don't have any need for what benefits XHTML does offer, so why use it and risk the incompatibilities? I still don't understand why everyone is so up-in-arms about using HTML 4.1. It's not like browsers are going to suddenly stop rendering it correctly, so what difference could it possibly make to you?

      --

      --
      Promoting critical thinking since 1994.
  128. But can it validate? by uodeltasig · · Score: 2, Informative

    Is it really too much to ask that you run your site through a validator?
    Really come on now, I'm sure you've duped the 'importance of validating' articles before. And what's up with HTML Strict, why not XHTML strict? Get your nerd programming skills together.

    --
    Hey look no pointless curley braces or semicolons... just like Python
  129. Mobile phone and PDA support???? by Anonymous Coward · · Score: 1, Interesting

    I am glad to see this CSS refreshening of the Slash looks, but I was *very sad* to see that there is STILL no automatic detection for mobile browser support! I tried with my AvantGo, Pocket IE, my phone's Openwave UP.Browser and Netfront browsers and NONE of these are supported properly.

    To make things even worse the CSS version of Slashdot is not as compatible anymore with these mobile browsers as they are not so CSS-capable as desktop browsers are. In other words: sh*t. :(

    What I need is a special mobile version of Slashdot that loads AUTOMATICALLY when the 10-15 most popular mobile browsers hit the slashdot.org site.

  130. On lynx, w3m... by higon · · Score: 0

    It looks just like normal blogs which sucks. I needed to scroll 2-3 pages down to read main contents.

      CSS sounds neat, but I prefer tables, really.

  131. mod parent up by TheJorge · · Score: 5, Insightful
    Cheers. Save perfectly identical rendering is not the realm of HTML/CSS. There are plenty of technologies out there that allow full control over layout. A bitmap comes to mind.

    But I think there is a point somewhere in there to be made. Remember HTML 1.0? Simply the fact that tags like STRONG, H1-H6, and ADDRESS exists points pretty clearly to the intent to allow a site to describe what was being presented but allow the browser to determine how it was presented. Of course, there were a load of problems with this and people's ideas of how it should be used, and we like to think we've come a long way. But in truth, we're still doing the same things.

    Rather than trying to be the control-freak with everything exactly positioned, it's far more useful (and elegant to program) to have a site which can do without X, Y, or Z and still convey all the information it did before. A site that degrades gracefully may not impress the casual user, but the casual user will be able to use it.

    Look at the most successful commercial sites out there today. Google's front page and search results are viewable in every possible browser I can come up with. eBay is one of the ugliest sites in existence, but its content is available to nearly any browser. Hit amazon.com with Lynx and you can still buy things.

    Successful web sites are not pretty. They're functional. CSS is a tool to make more functional pages. Yes, you can also make them prettier, but if you set out with that as your goal, you'll fail the more important one.

  132. BUG: Text Selection Doesn't Work in Firefox by Anonymous Coward · · Score: 0

    On the slashcode main page:

    Find an article with two paragraphs of text, such as the current "Slash + CSS" article at the top.

    Start selecting the text in the middle of the second paragraph. Drag the mouse up and try to continue selecting text in the first paragraph.

    Can't do it.

    Or, try selecting ALL the text in just one paragraph, first character to last. Right about when you get to the last character, you have to be precise within about one pixel, or the selection goes to just a single bit of text in the first line.

    1. Re: BUG: Text Selection Doesn't Work in Firefox by grondu · · Score: 1

      It works correctly using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050906 Firefox/1.4 ID:2005090607 (today's Deer Park branch nightly build).

      --

      I'm the urban spaceman babe, but here comes the twist... I don't exist

  133. Dream come true by rahuja · · Score: 1

    When I developed a quick and dirty table-less CSS-based website using the sample code from glish, I always wondered why our beloved Slashdot is still using tables for layout. I couldn't be happier than I am to find that new code does away with those overused TABLE tags. Way to go!

  134. Full text by IainHere · · Score: 2, Funny

    Since the site is slashdotted, here's the article text (it's funny, laugh!)

    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
                            "http://www.w3.org/TR/html4/strict.dtd">
    <html>
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
    <meta name="description" content="Slash + CSS -- article related to Slash.">
    <title>Slashcode | Slash + CSS</title>

    <link rel="stylesheet" type="text/css" media="screen, projection" href="//www.slashcode.com/base.css" >
    <link rel="stylesheet" type="text/css" media="screen, projection" href="//www.slashcode.com/comments.css" >
    <link rel="stylesheet" type="text/css" media="screen, projection" href="//www.slashcode.com/ostgnavbar.css" >
    <link rel="stylesheet" type="text/css" media="screen, projection" href="//www.slashcode.com/slashcode.css" title="Slashcode" >
    <link rel="Alternate stylesheet" type="text/css" media="screen, projection" href="//www.slashcode.com/slashdot.css" title="Slashdot" >
    <link rel="stylesheet" type="text/css" media="print" href="//www.slashcode.com/print.css" >

    <!-- start template: ID 169, ssihead;misc;default -->

    Sorry - I'm not allowed to show you any more because it violats the posting filter. Stay tuned for the next exciting installment.

    1. Re:Full text by Anonymous Coward · · Score: 0

      Continuing today's story, this just in from the W3C validator.

  135. Obligatory? by NereusRen · · Score: 1

    I, for one, welcome our new CSS-wielding Slashdot webmaster overlords.

    ...

    No, seriously, what took you so long? We've been waiting for you guys for, like, ever.

  136. You can't test your own software? by Anonymous Coward · · Score: 0

    What, the /. nerd-kings can't test their own software? You want us to do all the work for you? I expect software to be perfect by the time it reaches beta, and I learned this by reading /.

  137. print.css non-optimal (bug?) by ottffssent · · Score: 1

    Firefox 1.0.6 / Windows XP

    Slashcode.com. Print preview.

    The topic / search icons at the top of the page (not the ones associated with individual stories) are being printed in an unordered list with bullets at the top of the page. I see no reason why these should print. Using the display property, some print-version-specific intro could be printed to introduce the page, but those icons are just a waste of space (about half a page at present).

    A quick glance through print.css indicates this is the intended behavior, though I may have missed something.

  138. Most useful web interface ever: Google news by Alaska+Jack · · Score: 1

    Google news has the most useful web interface I've ever seen: The "tree" view, which shows you exactly where you are in the hierarchy in a pane off to the left. I've always wondered why this paradigm never caught on -- it's so useful and intuitive. I'd love to see Slashdot adopt it.

    (If you don't know what I'm talking about, go to Google News, search for Britney Spears, click on the first result, then go up to the top of the screen and click on the "view as tree" link.)

    I urge the Slashdot gods to consider implementing something like this.

          - AJ

    1. Re:Most useful web interface ever: Google news by Jussi+K.+Kojootti · · Score: 1

      You mean Google Groups, I suppose. It's a nice interface, but I really don't see what it would bring to the slashdot-experience...

    2. Re:Most useful web interface ever: Google news by Alaska+Jack · · Score: 1

      Damn, I did mean Google Groups. Great, I probably just blew my chances of ever seeing it on slashdot.

      In response to your second comment, all kinds of sites have recognized the utility of having an overview of a comment thread, so you can tell at a glance who is replying to whom, and so on. Yes, I know about nested comments and threading, but I still find /.'s implementation of those pretty dicey.

      Most sites that do provide this sort of overview do it at the top or bottom of a page, like this:

      http://forums.nasioc.com/forums/showthread.php?t=6 03725

      I think Google Groups' vertical implementation is better.

            - AJ

    3. Re:Most useful web interface ever: Google news by Alaska+Jack · · Score: 1

      Gyaaa, I meant Google Groups. Stupid! Stupid! Stupid!

              - AJ

  139. Cubs win Series! by Anonymous Coward · · Score: 0


    I better rush right home, too, 'cause my wife will finally give me some back door action!

    What a great day this turned out to be.

  140. This page is not Valid HTML 4.01 Strict! by savuporo · · Score: 1
    --
    http://validator.w3.org/check?uri=http%3A%2F%2Fwww.slashdot.org Errors found while checking this document as HTML5!
  141. Re:Sorry for being a luddite but.. by ajuin · · Score: 1
    People with disabilities prefer CSS because it allows them to trivally alter layout and visual presentation in a way that works for them. For example, some people have trouble seeing low-contrast presentations; they can insert their own CSS into a CSS-aware page to make any site readable.

    Actually, they don't. Pixel-precise css layouts (and numerous css hacks) make client-side stylesheets a nice idea in theory mostly.

    Secondly, the use of CSS for layout has lead to a lot of web designers pretty much neglecting the presentability of plain HTML. Open Slashcode in lynx and you'll see what I mean; three pages of (mostly) irrelevant links before you get to the articles themselves.
    Keep in mind, an individual using a screen reader will have to read or listen to all of these links before getting to the content.

    CSS, like all the layout tools for the web that preceded it, is something that needs to be applied with great care if usability is to be maintained.

  142. Re:Finally, Slashdot Slashdotted, Literally! by yason · · Score: 1

    I can buy winter Olympics in Hell anytime, but if we see no cycling dupe loop between Slashcode and Slashdot about this update, I'll be amazed.

  143. JavaScript? by ImaLamer · · Score: 1

    You must be new here. Most slashdot visitors have turned off Javascript or are still using Lynx.

  144. html 4.01? are you serious? by portscan · · Score: 2, Interesting

    let's see:
    HTML 3.2 - 1997
    HTML 4.01 - 1999 (!)
    XHTML 1.0 - 2000, revised in 2002
    XHTML 1.1 - 2001

    Welcome to the year 1999. The future is now. While I appreciate the efforts of the Slashcode developers, I would like to point out that it is still possible to write spectacularly awful code in HTML 4.01. Yes, it is possible to do so in XHTML, but it is more difficult. My one request to the developers (and believe me, you will thank me when maintaining this code base) is to use <div> tags, lists, and CSS positioning for layout instead of tables. It makes your code so much cleaner and easier to edit. In fact, to me it is the main benefit of CSS.

    (If you remember this article, posted to /. a while back, it goes through some of the steps of converting a static image of a /. page to XHTML and CSS)

    1. Re:html 4.01? are you serious? by nagora · · Score: 1
      On the other hand, XHTML is a pile of shit designed by idiots. Just look at the "Differences with HTML 4" section:

      • Documents must be well-formed. Okay, this one's fair enough in theory, although meaningless in reality.
      • Element and attribute names must be in lower case. Stupid, moronic change for no purpose. Anyone that uses LI distinctly from li should be shot, and anyone that thinks you should be allowed to should be shot along with them.
      • For non-empty elements, end tags are required. Stupid, moronic change for no purpose. A paragraph break is an event, unlike embolding. It does not need a closing tag. HTML is not XML or even SGML, nor does it have to be.
      • Attribute values must always be quoted Why? What does this achieve?
      • XML does not support attribute minimization. That's because it's brain-dead. Why pollute HTML with XML's mistakes?
      • Oh, well, you get the idea; it just goes on and on.

      XHTML is based on the entirely erroneous idea that Hypertext should be some generalised data storage system. It shouldn't. It should be an easy, flexible method of marking up text for a browser to render to the user. IT IS NOT A FUCKING DATABASE. In particular, HTML does not need to validate. It should, sure, but no one's going to tolerate a browser that simply refuses to display malformed markup. The browser simply HAS to make a stab at rendering, and to hell with DTDs and the rest of it - that's just classic XML masturbation.

      Goddamn XML people and their "one size fits all" approach to everything.

      TWW

      --
      "Encyclopedia" is to "Wikipedia" what "Library" is to "Some people at a bus stop"
    2. Re:html 4.01? are you serious? by portscan · · Score: 2, Insightful
      You clearly have strong opinions on the matter, but allow me to address some of your questions.
      • The difference between "well-formed" (and by this I think they mean content separated from style) documents and messy table-filled documents where all the styling is in the text is huge. As a developer, it is frustrating at first, but lovely in the long run to have good style imposed on you. The restrictions are light and the benefits are immense
      • Case insensitivity in HTML is an unnecessary feature. All it does is make code slightly more confusing and difficult to read.
      • Terminating each element is highly desirable, so your document is broken up cleanly into distinct sections, which can be easily identified and consequently rendered. A paragraph break is an event, however, the paragraph itself is an element of the document structure. The <p> and </p> tags signify the beginning and end of each paragraph. Then you can use style sheets to describe how paragraphs should be rendered. If you just want line returns, use <br />.
      • Quoting attributes makes code more clear and less error-prone. When the whole value is in quotes, there is no ambiguity as to what the value should be and what might be a typo or extraneous information. Surely you can imagine a situation where the next bit of text after an attribute would be a valid part of that attribute. and there is ambiguity as a result
      • Removal of attribute minimization also just makes fore cleaner, more deliberate code which clears up ambiguity. Surely you cannot be decrying the omission of a feature that you call "brain-dead."
      As you can see, XHTML aims to make HTML more clean, standardized, and reusable. It aims to remove ambiguity and clutter from the code and separate the distinct realms of content and design (which is done using stylesheets). No, it is not perfect, but having switched from HTML to XHTML, I find it to be a much more pleasent environment to code in.
    3. Re:html 4.01? are you serious? by nagora · · Score: 1
      think they mean content separated from style

      I don't think that is what they mean, I think they just mean "validates".

      Case insensitivity in HTML is an unnecessary feature. All it does is make code slightly more confusing and difficult to read.

      And easier to write. NO language, HTML, C++, Perl, whatever, should be case sensitive. It simply increases the number of errors (and often they are hard errors to find) for zero return. Having two variables (or whatever) which differ only in case is BAD programming of the highest order. Allowing it in your langage is bad design.

      A paragraph break is an event, however, the paragraph itself is an element of the document structure.

      No it's not. The DIV and SPAN tags and a few others are structure; paragraphs are formatting pure and simple. There is no point in having /p or /li tags as p and li achieve all that is needed. If HTML were a database language then perhaps the requirement for closing tags would be more than pedantic timewasting from a committee more concerned with making work for itself than producing useful standards.

      Quoting attributes makes code more clear and less error-prone.

      Yes, sometimes. Making it a requirement is pointless and causes errors, particularly when dealing with numerical data. Quotes are hardly ever needed in HTML; why make more work for the author?

      Removal of attribute minimization also just makes fore cleaner, more deliberate code which clears up ambiguity.

      It makes for redundant and confusing code for, once again, zero benefit to the user or author, and is a classic piece of brain dead design. Any time you find yourself having to type something like 'clicked="clicked"' you know the language designer is an anally retentive buffoon.

      As you can see, XHTML aims to make HTML more clean, standardized, and reusable.

      If that's what it's aiming for, it missed. It's less clean with the addition of extra tags and attributes which add nothing to the utility except some extra chances to make a mistake, it may indeed standardise HTML but it is standardising it to a database language rather than a useful text markup language, and in fact it does nothing much for reusability as it happens in the real world - again, the designers' confusion between what a markup language has to do and a data storage language has to do leads to pie-in-the-sky theorising with no regard to the real world.

      No, it is not perfect, but having switched from HTML to XHTML, I find it to be a much more pleasent environment to code in.

      Well, you must be a masochist with RSI, then! XHTML is badly designed, wordy, error-producing, needless, garbage.

      Always remember: the more rules you have, the more mistakes you will make. HTML is not something that needs formal proving; it is not rocket science and shouldn't be.

      TWW

      --
      "Encyclopedia" is to "Wikipedia" what "Library" is to "Some people at a bus stop"
    4. Re:html 4.01? are you serious? by portscan · · Score: 1

      Perhaps we should just agree to disagree. For me, there is XHTML, and for you, there is still HTML. I guess it ends up being a matter of taste. If /. moves to HTML 4.01 with CSS (and hopefully CSS positioning, not tables) then I guess that is progress.

      I rather like the structure and aesthetic of the "box model," but I suppose I can see how someone might find it a bit pedantic if the want to "just code." I still believe that in the long-term, XHTML produces more maintainable and cleaner code, but I will cease to try to convince you of that.

      For me, going back to HTML seems like a huge step in the wrong direction especially if I am using a language like perl or php to generate my (X)HTML, but to each his own.

      Also, I would like to take issue with your point that more rules lead to more mistakes. A programming (or markup) language is simply a set of rules. I think that there is a point beyond which rules cease to be helpful, but you need to have some rules! The designers of XHTML believed (and I agree) that HTML was too loosely structured, which led to bad rendering and difficult to maintain code. I mean, look at Slashdot, which is only now being upgraded 7 years later since it was too much work to do it. Try to see it as a matter of taste. If you have not done any serious work in XHTML with CSS formatting and layout, then I suggest you try it out a bit. I guess part of the point of having each tag be closed is that CSS knows where to stop the formatting. Given this closed model, it is very simple to apply formatting to a document and then chage it on the fly.

    5. Re:html 4.01? are you serious? by nagora · · Score: 1
      I really can't see why you think CSS is connected with XHTML. I use HTML 4 with CSS all the time; the box model of layout is fundimental to the way I work (which is often dynamically in PHP and Perl). XHTML adds nothing to that, and as far as I'm aware does not try to add anything to that which is not in HTML 4.

      TWW

      --
      "Encyclopedia" is to "Wikipedia" what "Library" is to "Some people at a bus stop"
  145. fonts look bad compared to Slashdot by billmil · · Score: 1
    Hi,

    I'm using firefox 1.0.6 on Gentoo and the fonts for the *article bodies* on the slashcode/css look very bad compared to the ones on slashdot. (grainy, not smooth, etc).

    i.e. the stuff in these two tags:

       



    I know linux decently, but don't know (and dont' care to know) about fonts and font configuration. I would prefer slashdot to look good with minimal fuss in the realm of font configuration.

  146. CSS is nothign without good HTML by __aaitqo8496 · · Score: 1
    Can we get a fix to the HTML first? Maybe some relavent tags? How about a dash of
    • or
    • here and there.

      I'm glad to see the step in the right direction, but slashcode looks like garbage without a stylesheet; it should degrade gracefully
  147. Re:Finally, Slashdot Slashdotted, Literally! by TeknoHog · · Score: 2, Funny

    So will this be the year of Linux on the desktop?

    --
    Escher was the first MC and Giger invented the HR department.
  148. old browsers by slothman32 · · Score: 1

    I'll get flamed for this but what about us non-CSS people. NS4 technically works but like usual makes everything in one long page rather than the table layout it is now. Of course nobody likes tables but there still seems a way to do it.
    I, and probably all of Slashdot, still like Google's method. Nothing. It works on every browser ever made.
    Can a subsite be made that effectively copies the slashdot.org site but keeps it in the current form? I saw another comment that said many people with other browers, perhaps Lynx, can't use it either. I don't know that though.
    Why I use NS4, because it is fast, very fast. At least it is on WIN95. I could upgrade to another computer to run another OS but that would cost money and this computer works fine for most cases.
    Now I understand why people hate NS4 with a vengence. They hate it more than IE. As far as I know it is just because it is old or because the standards chanaged and it of course couldn't and didn't.
    People call me an idiot. I don't upgrade just because I can. I hate change except when it is REALLY benefitial. Most of those times it is expensive and requires the throwing out of good usuable stuff. A chair or a 350MHZ computer is perfectly fine. Well unless I need the newest and greatest.
    I did find a couple of things that privoxy could change that does make it look good. I think:

    s/border:.*([;}])/$1/gsU

    is required.

    --
    Why don't you guys have friends or journals?
    1. Re:old browsers by Accipiter · · Score: 1

      Boo fucking hoo. Honestly, if you're going to run outdated software and hardware, you have absolutely no right to complain when something doesn't work on your computer. Do you bitch that Doom 3 doesn't run on your Pentium II?

      Keep using Netscape 4. Internet won't miss you.

      --

      -- Give him Head? Be a Beacon?
      (If you can't figure out how to E-Mail me, Don't. :P)

  149. New SlashCode is illegible on Treo 650 by Darkforge · · Score: 1
    I've just filed a bug: [ 1283326 ] CSS: New SlashCode is illegible on Treo 650

    I bet it's probably illegible on other handheld devices as well... try it on yours!

    --

    When I moderate, I only use "-1, Overrated". That way, I never get meta-moderated!

  150. A List Apart by nfotxn · · Score: 1

    Awesome, it only took Slashdot two years since somebody wrote them a tutorial on how to do it.

    --

    _nfotxn

    1. Re:A List Apart by IpalindromeI · · Score: 1

      Yes, A List Apart took a couple pages, fixed the mark-up, and added CSS. A ten year old can do that. What A List Apart did not do was help rewrite the code that generates that mark-up. Rather a bigger task, that.

      --

      --
      Promoting critical thinking since 1994.
  151. CSS font-family by hisstory+student · · Score: 1

    I can't believe that somebodies statistics show that the average Slashdot reader prefers a serif font. I'm sure if they look a poll on the question, the vast majority of readers would prefer sans-serif. True, one's browser can be forced to use whatever one prefers, but there actually are times when one's favorite is simply not what's appropriate. Oh well, such is.

    --
    Heard any good sigs lately?
  152. well then by kronchev · · Score: 1

    im on a pda right now and browsers are 5-6 years behind the rest of the internet, so i cant see the skins presented...but i always laughed that ye ol slashdot was far behind standards. regardless, CSS
    lets me make a custom skin to get away from eye-splitting green on white.

  153. Who needs WML? by Mustang+Matt · · Score: 1

    I hadn't heard that term in a while but aren't WML and HDML dead as can be since most mobile devices have HTML browsers now?

    WML and HDML are a nightmare at best. I won't be missing them if sites don't continue to support them.

    --
    The man who trades freedom for security does not deserve nor will he ever receive either. - Benjamin Franklin
  154. Job Offer by aero2600-5 · · Score: 1

    I received an e-mail today about this job posting. They're looking for an experienced web developer, but an expert in slashcode would likely be able to get the job as it would be pretty useful.

    It's also a great excuse to relocate to Las Vegas, but you don't have to.

    Aero

    --
    Please stop hurting America -- Jon Stewart
  155. Re:Finally, Slashdot Slashdotted, Literally! by Anonymous Coward · · Score: 0

    In other news Duke Nukem Forever will be released in October.

    (I apologize.)

  156. Opera 8.02 by adolfojp · · Score: 1

    The slashcode page looks and works great in Opera 8.02

  157. a quick css review by kavin · · Score: 2, Informative

    it does not validate[1] -- you've got 2 typos:

    line 242: "#adminfooter label , #adminfooter legend,{". remove the comma
    at the end of the selector, and then line 488: "#usermenu ul.menu
    a.end... padding: 5px 11px 0 0 2px;". you've got 5 values for the
    padding property. it only takes 4 (for top, right, bottom and left,
    respectively).

    other suggestions:

    - use descriptive names for classes. i'm seeing things like: #misc,
    #frame and it's hard to remember what you're styling when you've
    labelled it in a rush and just given it a placeholder for a name. other
    class names are bound to locations (like #topnav) which is meta-semantic
    rather than semantic and confusing since it's easy enough to decide to
    css position it elsewhere and then you're going to have to change the
    code again. (the point of css is to separate content from
    presentation, so take the presentation out of your class names/ids and
    leave it up to the css properties.) also, there are known quirk issues
    with underscores in class names, eg your: #index_qlinks-content. rather
    use hypens.

    - for screen media, use a default font of sans-serif (you're using
    serif). sans-serif is proven easier on the eye on low resolution devices
    (like your monitor).

    - when specifying a colour, you're encouraged to always provide both
    foreground and background colours in the same css rule, as it's often
    not obvious what the cascade will do and you can easily end up with
    illegible text. for example, at least replace your:

    a { color: #066; }

    with:

    a { color: #066; background-color: inherit; }

    - you're using a mixture of css unit measurements. if you want text to
    resize and print easier, try replacing the pixel (px) measurements with
    ems or percentages (aka fluid layout). or provide a print stylesheet.

    - i'm not sure on this[2], but apparently most elements do not have
    intrinsic width and when you float something you should give it a width
    even if it's just a width:auto.

    - p

    --
    1.
    W3C CSS Validator results for http://www.slashcode.com/slashdot.css
    http://jigsaw.w3.org/css-validator/validator?uri=h ttp%3A%2F%2Fwww.slashcode.com%2Fslashdot.css&userm edium=all

    2.
    Visual formatting model
    http://www.w3.org/TR/REC-CSS2/visuren.html#floats

  158. Re:Sorry for being a luddite but.. by Kjella · · Score: 1

    Developers and designers like CSS because it follows the excellent practice of separating view from data. It's easier for a developer to make changes to the underlying code because they worry less about breaking the view;

    Apart from one thing, which is easier on the browser than the developer. I really hate that you can't define constants. No, not variables, constants. For example:

    define foreground #ff00ff;

    div.foo {
            color: [foreground];
    }

    div.bar {
            color: [foreground];
    }

    I know you can do:

    div.foo div.bar {
            color: #ff00ff;
    }

    but it is very confusing to see everything that applies to div.foo if you have it that way. In addition you could have:

    div.foo {
          (CSS)
    }

    div.foo div.otherbar {
          (CSS)
    }

    etc etc.

    Kjella

    --
    Live today, because you never know what tomorrow brings
  159. On stylesheet switching by pe1chl · · Score: 1

    Of course with "a good browser", you can select the stylesheet to use when alternative stylesheets are available. In IE you can't.
    But even "good browsers" like Firefox, Mozilla and Opera don't handle this correctly. When you click on a link that fetches the next page from the same site, the style sheet selection is undone and you again need to pull out the same 3-level menu selection to switch style to the one you want.

    Only Konqueror handles this "correctly", by remembering the style you selected for tht site.
    However, solutions using a cookie are available, like the one describled in this article on A list Apart: http://www.alistapart.com/articles/alternate/

    When using this method, some clickable widget on the page can be used to select style, while the menu item still works.
    Slashdot should incorporate something like this, or the stylesheet selection will be useless to 99% of its users.

  160. Try not to imitate the old Slashdot. by boring,+tired · · Score: 1

    The new site looks nice, but be careful about making it look like the old slashdot, because if you don't do it perfectly, it comes off looking like a cheap imitation. It might be better to change the look just a bit, so it looks like a new improved (but still familiar) site.

  161. Jesus. Just Jesus. Jesus.... by Anonymous Coward · · Score: 0

    What kind of CRAP is this? It's not FLAMEBAIT, you insufferable pompous asses...

    1. Re:Jesus. Just Jesus. Jesus.... by Anonymous Coward · · Score: 0

      What is FLAMEBAIT?

      Is it, like, like HTML?

  162. Slashdot upgraded.. by b100dian · · Score: 1

    ..TOO LAAAATE! Deer Park already fixed that!!

    oh, wait..

    --
    gtkaml.org
  163. I use lynx... by kula.shinoda · · Score: 1

    ... will it look better for me?

    --
    Real men don't write sigs
  164. you're doing it wrong ... by pbhj · · Score: 1

    .. too moral I expect.

    What you do is give them the standards compliant site and show them screen caps from Safari, Konq., Firef., Moz., etc. so they can see it works as required by the NSR (ie, the spec). Then charge extra to make it work in IE, after all it's the IE fixes that take all the time up, why not earn extra off them!?!

      80)>

    That said, it would be great if clients knew that when a page doesn't work in IE it's usually a browser issue. I look forward to the day:

    Client - "Your page looked terrible, so I upgraded my browser, now it's awesome"
    Me - "Great!"

    as opposed to

    Client - "You stink, this page looks like a crock of poo on IE5.1 on my Mac OS7. What am I paying you for - I could have done it myself in Word"
    Me - "Great!"

  165. Unblock the W3C validator by Apotsy · · Score: 1

    Are they going to un-block the W3C validator now? Currently it's 403.

  166. Re:mod parent up by Gunnery+Sgt.+Hartman · · Score: 1

    There are way too many "pretty" websites that are concerned about form over function. A lot of times these pretty websites tend to be just bandwidth hogs. Hopefully slashdot recognizes this problem and continues on with putting function above form.

    --
    [ ]
  167. A small tweak in the HTML by bcarl314 · · Score: 1

    Looking at the code I see this:...

    <label>
            Nickname
    </label>

    <input type="text" name="unickname" size="20" value="">

    While I applaude the use of label tags, for WAI / 508 compliance, it would better serve to properly associate the labels with the buttons using the for attribute in the label tag and the id attribut in the input tag.

    Example:

    <label for="form_nickname">
            Nickname
    </label>

    <input type="text" id="form_nickname" name="unickname" size="20" value="" />

    But that's just a nit pick. Oh, and close the input tags as well ;)

  168. Re:Sorry for being a luddite but.. by SeeTheLight · · Score: 1

    Could that be solved with a "Jump to Articles" or "Jump to Contents" link at the top of the links/navigation list and a "Back to Navigation" or "Back to top" link at the top of the content area that only displays when CSS is not being used?

  169. Aw, man.... by linebackn · · Score: 1

    It looks like I will finally have to upgrade from Netscape 3.0. Well, Moz and Firefox runs on Windows 95... probably will need more than 8 megs of ram unless I want it to take half an hour to start up again. Will upgrading to XP make my 486 faster?

  170. "migrate the current skin to CSS" by nmg196 · · Score: 1

    > as we migrate the current skin to CSS

    Why the flying FSCK would you want to do that? Slashdot is one of the most ugly and dated looking websites that still has users. Redesign the bloody thing from scratch. It's not like you wouldn't get several thousand volunteers...

  171. Just remember! by Snaller · · Score: 1

    * DON'T abuse stylesheets to lock fonts in a tiny (unreadable size), not for any default skin.

    * And DONT specify line height, since you can't disable that in MSIE when you tell it to ignore font sizes (meaning all letters end up on top of each other)

    * And DONT set the scroll bar to the same color as the background, making it invisible to some of us with less that optimal eyesight.

    thank you.

    --
    If Google really cared they would fix Android Chrome to reflow text, instead of discriminating
  172. CSS by Anonymous Coward · · Score: 0

    I browse Slashdot in Lite mode you insensitive clod.

  173. Mod up! by Hakubi_Washu · · Score: 1

    The parent is right, there are a few moronic mistakes left... Do it right, ok? And, though I like XHTML personally, I'd agree HTML 4.01 is probably the better choice for legacy support (sadly).

  174. Re:Finally, Slashdot Slashdotted, Literally! by out_sp0k1n · · Score: 1

    the best rapper is white, the best golfer is black...

  175. This is gonna ROCK! by halr9000 · · Score: 1

    I am SO gonna kick Taco's ASS on de_dust2!

  176. Slashdot Light by (1+-sqrt(5))*(2**-1) · · Score: 1
    Whatever you do, please preserve the Slashdot light option:
    Light (reduce the complexity of Slashdot's HTML for AvantGo, Lynx, or slow connections)
    and no icons option.
  177. I like it. by ManuelKelly · · Score: 2, Informative

    It looks pretty good on: Mozilla/5.0 (compatible; Konqueror/3.2; Linux) KHTML/3.2.3 (like Gecko)

    It even works well with the larger fonts I prefer to use.

  178. w00t by 834r9394557r011 · · Score: 0, Offtopic

    looks crisp and sexy. makes me wanna play with my nipples. ooh did I say that out loud.

    --
    w00t
  179. Re:Finally, Slashdot Slashdotted, Literally! by WilliamSChips · · Score: 1

    Now you're just talking crazy.

    --
    Please, for the good of Humanity, vote Obama.
  180. IE, pronounced AIIIEEEE! by tepples · · Score: 1

    I suspect that if you had to modify HTML to correct display issues, then you hadn't completely separated structure (which belongs in HTML) from display (using CSS).

    I suspect that one good reason behind preferring proven HTML techniques over their CSS counterparts (such as <table> vs. display: table-cell) was to make the site more compatible with legacy code that doesn't allow such a complete separation of structure from presentation.

  181. Lame doctype by Dracos · · Score: 1

    Come on, HTML 4.01 Strict? And it still has 4 errors on the front page?

    It's 2005, catching up to 2000 is kinda pointless. Go for XHTML 1.0 Strict.

  182. HI BONCH! by Anonymous Coward · · Score: 0

    Lameness filter encountered. Post aborted!

  183. Lynx lacks SSL by tepples · · Score: 1

    Hit amazon.com with Lynx and you can still buy things.

    No you can't. The official distribution of the Lynx web browser does not include SSL because of patent and/or export control issues that applied at the last major release of Lynx. Without SSL, you're sending credit card numbers in the clear to Eve, who can use them to attack your bank account.

    1. Re:Lynx lacks SSL by Baricom · · Score: 1

      It's not pretty, but it's possible to order from Amazon without SSL. You have to be willing to transmit your address information (but not necessarily your credit card) in the clear. Once you do that, Amazon will give you instructions to phone in your credit card number.

      It's not a good idea to send personal information without SSL, but Amazon will happily take your money anyway.

  184. Re:Finally, Slashdot Slashdotted, Literally! by Anonymous Coward · · Score: 0

    We're talking rap "music" and golf here. 'Best' has to be considered a relative term, i.e. still crap as human beings with no useful talents.

  185. Re:Finally, Slashdot Slashdotted, Literally! by robfoo · · Score: 1

    As soon as Duke Nukem Forever for Linux is released! :p

  186. The mistaken deprecation of li value by tepples · · Score: 1

    why HTML 4 as opposed to XHTML 1 Strict?

    One reason was the mistaken deprecation in HTML 4.01 of the value attribute of the li element, which was carried forward into XHTML 1.0. Some would claim that the value element has been superseded by CSS counters, but that's not acceptable for two reasons: First, no widely used web browser supports CSS counters. More importantly, if I want to express that an album's track list starts at 13 (see Follow the Leader by Korn), that's content, not presentation. But if I'm using a Strict DOCTYPE, I can't use deprecated attributes, not even mistakenly deprecated ones such as <li value="13">It's On!</li>.

    So why not use XHTML 1.0 Transitional? Others have explained the reasons, but I'll recap: Well over two-thirds of web users still use Microsoft Internet Explorer up to and including version 6 as their primary web browser, and IE up to and including version 6 does not support XHTML. No, Section C is not the answer. Or do you expect every web site owner to develop, test, debug, and deploy a filter that 1. reliably distinguishes between user agents that do support XHTML and those that do not, even when agents send broken Accept: headers, and 2. dynamically translates XHTML to HTML 4 for all IE users? And what about users of two different user agents behind the same caching proxy?

  187. Only in @media print, OK? by tepples · · Score: 1

    I studied fonts and other silly stuff when I was in "Human Factors Engineering". Sorry, I didn't keep my notes for the citations, but I explicitly remember reading that and it is very common to find the serif - sans-serif motif used in print

    If Slashdot CSS overrides the body text font to match prevailing standards in print publishing, it should do so within an @media print block. I too prefer Arial over TNR for on-screen body text.

  188. Use Sans fonts by default by Nailer · · Score: 1

    Just about every UI engineer is aware that humans can read sans serif fonts faster than serif fonts for low resolution (read: computer screen) content.

    1. Re:Use Sans fonts by default by testerus · · Score: 1

      ...can read sans serif fonts faster than serif fonts for low resolution (read: computer screen) content
      That has been true in the past, but the quality of fonts rendered on modern displays has improved dramatically due to subpixel-hinting and monitors with higher resolutions.

    2. Re:Use Sans fonts by default by Nailer · · Score: 1

      The improvements exist, sure, but still, the best monitor available right now can do 133 DPI, if I'm up to date. A hundred dollar printer can do 1200 DPI. So computer displays are indeed low resolution devices when compared to say, paper.

    3. Re:Use Sans fonts by default by Briareos · · Score: 1
      still, the best monitor available right now can do 133 DPI, if I'm up to date.


      With subpixel anti-aliasing (i.e. ClearType et al) on a TFT display you practically get three times the resolution horizontally (you still need 3 adjacent subpixels per black dot, but it can be positioned more accurately), which helps quite a bit...
      --

      "I'm not anti-anything, I'm anti-everything, it fits better." - Sole

    4. Re:Use Sans fonts by default by babbage · · Score: 1
      still, the best monitor available right now can do 133 DPI, if I'm up to date.
      With subpixel anti-aliasing (i.e. ClearType et al) on a TFT display you practically get three times the resolution horizontally (you still need 3 adjacent subpixels per black dot, but it can be positioned more accurately), which helps quite a bit...

      Wait, let me check my math here.

      So you're saying that, with the magic of advanced rendering technology [only for Windows, yes?] on a high-end & presumably expensive display, you can ideally get ... 133 x 3 = 399 or ... 399 / 1200 = 0.3325 ... So, about a third as good as you can do with a hundred dollar printer and a penny piece of paper ? Hm...

      Somehow, this doesn't exactly disprove the assertion that print quaility is still far better than anything a consumer computer can do on screen today, or in the foreseeable future.

    5. Re:Use Sans fonts by default by Briareos · · Score: 1
      So you're saying that, with the magic of advanced rendering technology [only for Windows, yes?]

      No. Sub-pixel antialiasing is also done by Xfree's font engines.

      on a high-end & presumably expensive display

      No. Have you checked TFT prices lately?

      , you can ideally get ... 133 x 3 = 399 or ... 399 / 1200 = 0.3325 ... So, about a third as good as you can do with a hundred dollar printer and a penny piece of paper ? Hm...

      Yes. Then again, if you read my previous reply carefully I just responded to the parent poster's claim that ~133DPI was the limit.
      --

      "I'm not anti-anything, I'm anti-everything, it fits better." - Sole

    6. Re:Use Sans fonts by default by babbage · · Score: 1
      So you're saying that, with the magic of advanced rendering technology [only for Windows, yes?]
      No. Sub-pixel antialiasing is also done by Xfree's font engines.

      But then you're stuck using XFree :-)

      Anyway the point wasn't to be a troll about it -- and in hindsight, I apologize if I came across that way. I'm just pointing out that while subtle tricks like subpixel rendering can do a good job at making the most of existing display technologies, even with their help, you're still getting a small fraction of the resolution available to even the cheapest of printers -- and those printers can often go much sharper if you want them to.

      In order to get anywhere near the quality of print, display technologies need to either get radically more clever, or have to be superceded by something much finer grained. The way things are now, and have been for the past decade or more, display resolutions are an order of magnitude coarser than print ones, and on the whole, even things like TFT and subpixel rendering have not done enough to close the gap.

  189. Please include a CSS/Theme for the original by beforewisdom · · Score: 1

    This is a great move.

    Please include a CSS/theme for the original look and feel to slashdot.

    The new default look takes away from slashdot's unique look and makes the site look like one among many web boards.

    Sorry.

    I guess I just like what you had off the bat.

  190. Re:mod parent up by NutscrapeSucks · · Score: 1

    Remember HTML 1.0?

    Well, I do, but 99.9% of the current web surfing population certianly doesn't remember HTML 1.0. They started using the web well into the age of tables, and therefore have certain expectations about websites, one being accurate layout.

    While a "degraded" site may be pefectly acceptable on a cellphone or lynx, it's going to be rarely adequate for anything the client considers to be a popular PC web browser.

    --
    Whenever I hear the word 'Innovation', I reach for my pistol.
  191. Re:Sorry for being a luddite but.. by tepples · · Score: 1

    I really hate that you can't define constants. No, not variables, constants.

    Have you tried generating your CSS with server-side scripting?

  192. OH GOD THANKS. by windwaker · · Score: 1

    It's about tiiiime. 3

    and the "what'z html joke" was in fact funny.

  193. Valid?!? by khenriks · · Score: 1
  194. Slashdot ain't done... by Anonymous Coward · · Score: 0

    till lynx won't run.

  195. heh...I have 4 mod points I'm losing by baegucb_18706 · · Score: 1

    without reading the comments. Just glad to see some movement ahead.

  196. The color of slashcode stinks. by ravee · · Score: 1

    I think a blue or green color suits it better.

    --
    Linux Help
    for all things on Linux
  197. Unicode by Anonymous Coward · · Score: 0

    http://www.slashcode.com/ is using iso-8859-1 for character encoding. Why not go with unicode like utf-8? It's kind of a big deal for people who use different languages.

  198. Privileges to install is not an issue by Anonymous Coward · · Score: 0

    If you don't have the right privileges to install another browser, use Portable Firefox (like I did at work without privileges). No install needed, unzip and run. You can ofcourse run it from a memorystick too.

  199. Re:Sorry for being a luddite but.. by Anonymous Coward · · Score: 0

    It's easier for a developer to make changes to the underlying code because they worry less about breaking the view.

    I'm currently on my lunch break at work having spent the morning repairing stylesheets that were broken by minor changes to the markup generated by our CMS system. Nice in theory, but in practice not so good. There are too many special cases in your average page due to the fact that the content is muddled in with advertising banners, headings, navigation bars and whatnot.

  200. Good job by AaronLawrence · · Score: 1

    I can only imagine the amount of tedium that has gone into this effort. Well done guys. And thank you.

    --
    For every expert, there is an equal and opposite expert. - Arthur C. Clarke
  201. Re:Jesus. Beneath your current threshhold by Anonymous Coward · · Score: 0

    What is
    "beneath your current threshhold" ?

  202. Re:Sorry for being a luddite but.. by Proteus · · Score: 1

    What you are missing is that it doesn't matter. If you have a CSS-aware browser, you can simply turn the entire annoying section off, move it, or change the way it flows to make it more navigable.

    Lynx-compatiblity just isn't important anymore, because even readers for the blind are more feauture-compatible than lynx. If reading the web in a text console is that important w3m or links work just wonderfully.

    --
    We may not imagine how our lives could be more frustrating and complex—but Congress can. – Cullen Hightower
  203. Is XML/XSL/XSLT too much to ask? by Anonymous Coward · · Score: 0

    XSLT was formalized in 1999. It's 2005.

    Having nice clean XML content and using XSLT for presentation would make it much easier for those of us who want to read slashdot in something other than a traditional web browser.