Journal gmhowell's Journal: My experience with the new interface 12
Well, it was easy to find the 'write in journal' link. Or is that from my slashbox? I dunno. I don't care. Second, it works better for me on IE 8.0 than it does on FF 3.6.
No FF compatibility, less readability than 2.0, inability to save preferences? Lame.
No wonder the number of comments to articles is down. Substantially by my seat of the pants estimation. Eighteen comments on a Android vs. Symbian troll article after 35 minutes? Anti-Apple troll article has 67 comments after three hours?!
They either wanted to drive down page views, will roll this back, or Netcraft will soon confirm it.
CT retirement plan (Score:1)
CT got paid plenty when /. was bought by whomever ever so long ago, but obviously the contract said he had to stay until some conditions are met - maybe low usgae, closure by parent.
So no bug fixes, then idle and now this.
I can see a plan by following the money.
Anyway it is a good conspiracy theory.
Journals are almost unusable (Score:1)
No separation between comments, seriously, wtf.
Holy _crap_ (Score:2)
I've been to /. since the redesign, but not to the journals. I left a comment off the E17-related article. I was surprised, as it seemed like the Slashdot interface finally worked.
This, on the other hand, is amazing crap. Did they fix it for the main areas of the site, and just uberbreak it for journals?
Re: (Score:2)
Yeah, the main areas of the site seem fine. I wonder if they simply forgot to provide CSS styles for the journal section.
Re: (Score:1)
<webdevgeekery>
For D1 at least (the only one I use), the markup for JE's in their default view is sent such that the last element in the following DOM path, copied from Firebug, is missing its "comments" ID:
Without that ID, the green and silver horizontal bars aren't applied, as neither are the textual stylings of the text for the silver bar. (And as a result of no green bar, the white text for that bar is
Re: (Score:2)
Needs a Flickr pool of screenshots of fail.
Also, seriously? You'd think after so many serial failures in rolling out site styling and UI updates, they'd have some kind of checklist to make sure they tested with an array of browsers, and in every general area of the site.
*shakes head*
Re: (Score:1)
An image gallery revealing the sheer breadth of Slashdot v3 fail would be quite amusing. Surely someone must've done one. I'm amazed at how many different ways I've been seeing the looks of this site being described. It's like it renders significantly differently for each browser line there is. But that's entirely likely to happen when you redesign your site using a bunch of non-standard styles and markup, like -moz and -webkit extension styles, and HTML 5 tags. But then why would a "freedom in softwar
Re: (Score:2)
No such pool or tagmeme appears to exist, yet.
EEEE (Score:2)
Why are all these comments light gray on white with no separation between them. This UI feels very strange to me.
Also, I can't seem to easily find replies to my comments. When I click on things in my messages, it goes to some other random point in the thread.
Re: (Score:2)
Works much better in Chrome 9 than in IE 8 or Firefox anything. But still broken in journals.
I think they've decided with this to just break journals. I don't think they like us any more.
Re: (Score:2)
Depends on what URL you used to get here. The link from the firehose http://slashdot.org/journal/260622/My-experience-with-the-new-interface#comments [slashdot.org] and the comments.pl version at http://slashdot.org/comments.pl?sid=1974762 [slashdot.org] both apply the "proper style" (won't say "work correctly"), but the userdir link http://slashdot.org/~gmhowell/journal/260622 [slashdot.org] (which is the link from your friend updates or from the top of the comments.pl page) gets the jacked up style.