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!
After almost 8 years, Slashdot's HTML is finally getting an overhaul.
What is a HTML?
If you do change to CSS beware as some CSS is IE specific, like list trees.
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!"
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!
Javascript + Nintendo DSi = DSiCade
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)
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.
Noooo. You killed slashcode.
Anyone have a cache?
from the oh-my-god-it's-actually-happening dept.
You can say that again.
You probably shouldn't click this.
Slashdot going to CSS? Has hell frozen over!? Windows gone GPL!? What's next?
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? ;-)
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.
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!
but...
Is slashcode slashdotted??
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
If it ain't broke... oh, nevermind.
Best Windows Freeware
Comment removed based on user account deletion
...does it validate?
Man is a slave because freedom is difficult, whereas slavery is easy.
Let me quote something from that article:
If Yoda so strong in Force is, why words in right order he cannot put?
I tested the CSS version with wget and it looks good ... ;-)
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
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
we fear change.
*raises hands to block out the light.....*
you fixed the american flag icon with the wrong number of stripes.
We have slashdotted the future.
-DB-
E-mail is like a prison: a prison with no walls... and no toilet. -Strong Bad
Come with a spell checker for submitters?
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
"It stinks!"
You know I can't seem to get to the site. Ah the slashdot effect on...well...slashdot. It's almost poetic
I vote for the entire site to be made in Shockwave. CSS is for suckers.
Duke Nukem Forever is just about to be released too!
Hi, could everyone stop clicking on the link for a minute so I can open it, thanks.
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!
I get no response from server....
You insensitive clod!
Greasemonkey will probably let you do it.
If I have nothing to hide, you have no reason to search me
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.
Just be glad that they din't link to the main site an brought that down.
Damn,
It's getting cold down here.
- Satan
The hip way to get your IP. No ads, ever.
Or go download the GreaseMonkey script for it...
(I'd link it, but the site is having difficulties.)
IMarv
Trusting software vendors is no smarter than trus
http://www.mirrordot.org/stories/1b76725873ab6a19b c7c2ca271002d1a/index.html
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.
Animoog.org
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
Slashdot works and it works well.
LOL, mod parent funny.
Quidquid latine dictum sit, altum sonatur.
"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
I tried this and it seems to be kicking out quite a few duplicate stories. Is that normal?
Johnkoerner.com
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
Ladies and gentlemen it has finally happened.
Slashdot has slashdotted itself.*
*Ok, so slashdot slashdotted www.slashcode.com. Slash slash slash......slash
Question everything
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.
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.
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." ---
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.
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.
bad_outlook
--
Is this vague enough for you?
maybe apple using switching the mac main processors from powerpc to some intel breed? though, this is even more unlikely, i think.
(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??).
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
From the slashcode page:
this might bring savings of 10GB of bandwidth PER DAY, while making each reload a little faster for everyone
Wow, Slashcode has been Slashdotted... how fitting.
-dZ.
Carol vs. Ghost
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..
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
Looks like I'm going to have to change my sig!!
Why doesn't Slashdot ever get slashdotted?
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
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
All I want is for these to remain as a preference option since that is what I use.
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!
Slashdot should take part in the CSS Reboot.
http://www.cssreboot.com/
Slashcode's been ./ed??? :S
Get rid of it please!!!
Bring Verdana or something more pleasant in...
- live from Costa Rica !
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.
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.
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"
Is it just me or slashcode takes ages to load?
tested on firefox 1.0.6 and IE6.
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:
3 A//www.slashcode.com.nyud.net%3A8090/
http://validator.w3.org/check?verbose=1&uri=http%
"Religion is the most malevolent of all mind viruses." - Arthur C. Clarke.
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?
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.
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?
(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
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.
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]
I kid, I kid.
EvilCON - Made Famous by
I tried to view the CSS version, but it was Slashdotted!
(I'm joking and serious.)
Yup, slashdotted already!
Self referencing pointer: slashdot slashdots itself into the blackhole of infinite loop.
Then change the default font in your UA!
What we really want is SlashFlash! With animated buttons, swooshing sounds and banners about a deranged amphibian imitating some kind of motor vehicle.
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.
or have my eyes decieved me? Say it ain't so taco? You are actually listening!? What next a dupe checker?
Got it finally: http://greasemonkeyed.com/tag/slashdot
IMarv
Trusting software vendors is no smarter than trus
An (almost) comrehnsive list of greasemonke\slashdot user scripts.:c ific#head-ec4846dd1f06f8efd2d256a59577b3faaebbbf12
http://dunck.us/collab/GreaseMonkeyUserScriptsSpe
If I have nothing to hide, you have no reason to search me
if only slashcode wasn't slashdotted so I could test it out.
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
The link doesn't work for me...
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/
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.
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.
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
Two years ago A List Apart ran an a set of articles where they did this exact thing.
Part 1 Part 2
Where can we find slashdot stats. How many users use each platform and how use each browser?
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.
How about adding a feature to prevent dupes from apearing on the main page?
:)
For that I would buy a subscription
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
On a more serious note, I think Jon Katz wrote some articles that drew enough attention to /. that it took /. down...
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
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.
Just put .nyud.net:8090 between the .com and the third /!!!
It's better to be the foot on the boot than the face on the pavement. ~~ tkx Kadin2048
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!
Goodbye 8-track, hello cassette!! Welcome to 1998, Slashdot!
"hey, could you pass me a paper towel? er.. I mean... DEPLOY ABSORBTION PANEL!"
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
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
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!
bad_outlook
--
Is this vague enough for you?
.dupe { visibility:hidden }
i have found, you can find,happiness in slavery!
Any plans on releasing a Linux version or is this going to be yet another Windows only update?
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!
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.
We want AJAX, RIA, and Web 2.0, you insensitive clods!
Flying is easy, just throw yourself at the ground and miss. -Douglas Adams
http://64.233.161.104/search?q=cache:1RFYjZrAz80J: www.slashcode.com/+slashcode&hl=en
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
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...
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.
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.
I'll be more than happy to test Netscape's compatibility.
digg.com rules.
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?
Slashdot slashdotted slashdot.
I already miss the old slashdot...
//WR
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/
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.
Duke Nukem Forever has come out.
Make your computer faster: rm -rf
Why isn't slashdot migrating to XML coupled with XSL? It's the future afterall!
There should be a "-1:Groupthink"
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
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..
...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
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
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.
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.
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.
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.
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!
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.
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.
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 /.
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.
High-speed Road Trip (18.000KPH)
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
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.
http://validator.w3.org/check?uri=http%3A%2F%2Fwww .slashcode.com%2F
nuff said ?
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.slashdot.org Errors found while checking this document as HTML5!
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.
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.
You must be new here. Most slashdot visitors have turned off Javascript or are still using Lynx.
Get your Unix fortune now!
let's see:
/. a while back, it goes through some of the steps of converting a static image of a /. page to XHTML and CSS)
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
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.
I'm glad to see the step in the right direction, but slashcode looks like garbage without a stylesheet; it should degrade gracefully
So will this be the year of Linux on the desktop?
Escher was the first MC and Giger invented the HR department.
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?
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!
Awesome, it only took Slashdot two years since somebody wrote them a tutorial on how to do it.
_nfotxn
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?
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.
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
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
In other news Duke Nukem Forever will be released in October.
(I apologize.)
The slashcode page looks and works great in Opera 8.02
it does not validate[1] -- you've got 2 typos:
h ttp%3A%2F%2Fwww.slashcode.com%2Fslashdot.css&userm edium=all
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=
2.
Visual formatting model
http://www.w3.org/TR/REC-CSS2/visuren.html#floats
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
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.
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.
What kind of CRAP is this? It's not FLAMEBAIT, you insufferable pompous asses...
..TOO LAAAATE! Deer Park already fixed that!!
oh, wait..
gtkaml.org
... will it look better for me?
Real men don't write sigs
.. 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!"
Are they going to un-block the W3C validator now? Currently it's 403.
Free Hans!
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.
[ ]
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
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?
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?
> 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...
* 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
I browse Slashdot in Lite mode you insensitive clod.
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).
the best rapper is white, the best golfer is black...
I am SO gonna kick Taco's ASS on de_dust2!
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.
looks crisp and sexy. makes me wanna play with my nipples. ooh did I say that out loud.
w00t
Now you're just talking crazy.
Please, for the good of Humanity, vote Obama.
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.
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.
Lameness filter encountered. Post aborted!
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.
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.
As soon as Duke Nukem Forever for Linux is released! :p
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?
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.
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.
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.
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.
I really hate that you can't define constants. No, not variables, constants.
Have you tried generating your CSS with server-side scripting?
It's about tiiiime. 3
and the "what'z html joke" was in fact funny.
"Result: Failed validation, 4 errors"w .slashcode.com%2F
http://validator.w3.org/check?uri=http%3A%2F%2Fww
till lynx won't run.
without reading the comments. Just glad to see some movement ahead.
I think a blue or green color suits it better.
Linux Help
for all things on Linux
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.
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.
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.
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
What is
"beneath your current threshhold" ?
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
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.