Ah, yes, I missed the fact that there's an upper limit. Sorry about that!
Still. I'm not convinced that your design team did enough research, as the upper limit for CPL (charactes per line) lies way outside the norm. I honestly cannot think of any major web site (disregarding Wikpedia for a moment) that has more than 120 CPL. The standard seems to be somewhere between 60 and 80 CPL. The 200 CPL of Darwin is an extreme outlier. Reading lines that are so overly long is uncomfortable and I usually leave web sites that force me to read such overly wide texts immediately. Maybe I'm alone in this, but the fact that I was taught never to set text this wide in art school and the fact that it violates common practice leads me to believe I'm not.
On top of that Darwin doesn't handle zoom gracefully. The layout jerks around and reproportions every time I hit Ctrl-Minus or Ctrl-Plus. That's rather disorienting and unsightly. If you do want to set the text in a way that forces me to zoom, you should at least make the zooming comfortable.
There's apparently no upper limit for the width of the content area. On larger displays that results in a text width that makes reading very uncomfortable. Take a look:
To quote myself:
The expectations here were that we were going to get our old space back from how it was back at Monaco, but in reality the Darwin update only expands the width when zoomed in or out and we still get the same width on Oasis on normal screen (100%).
I hope that clarifies what I was trying to say.
I think I finally get it too. The margin is fine with me though. There's a lot of a wiki's flavor in that margin. Making it small is fine, but making it disappear would subtract too much from the design.
Personally I think that Darwin is a clear advancement for smaller screens. I checked it out on my netbook and I'm quite happy with it. But at the risk of repeating myself once too often: At higher screen widths the content area becomes too wide. That's a step backwards from Oasis to the indiscriminate full screen width of Monaco and Monobook. I actually thought all this time that one of the main goals of Oasis was to fix just that. It seems I was mistaken.
I'll have to find out whether this is fluid layout stuff or some other issue.
It's exactly 1200px wide on my screen. That's what it says in the CSS too. Is that not what you see? Or is it supposed to be something other than 1200px?
Here's what I see on my 1920 by 1200 display:
|normal zoom||large zoom|
|small window||large window|
|textarea is as wide as in Oasis||textarea is ridiculously wide||textarea is as wide as in Oasis|
Sorry. I don't :(
Wow! Well done!
My screen width is 1920 pixels. That means the text width is around 200 characters. That's very difficult to read. It becomes difficult for the eyes to maintain the precise horizontal movement. And it becomes even more difficult to find the beginning of the next line. Frequently the reader will get lost in the text. Reading efficiciency declines and so will the number of readers who make it to the last line. That's actually old news. There has been plenty of discussion and research about this topic. The Elements of Typographic Style specifically recommends 45 to 75 characters per line for block text. Granted, those recommendations were made with print in mind, but apart from wikipedia - which is a terrible example in this regard - I can't think of a single successful web site that does away with that recommendation completely. Unlimited character length is a bad idea.
Well, then it's still buggy. Less so than last year, but still.
Yup. Here too :)
I'm not entirely certain, but it may be a timing issue. It's hypothetically possible to click the button while the stylesheet is loading. What which browser would do in those exotic circumstances, is anyone's guess. I wrote a fix on that premise. Let me know if it works!
The order was wrong. The code that adds the event-handler to the button must come after the code that adds the button. Should be fixed now.
Yeah. Funny thing that. Wikia Poland is located in Poznań. Notice the funny acute on the letter n? I bet that doesn't work in Safari :D
This particular error seems to be caused by non-ASCII characters in the GEO cookie. So if you happen to live in a city with a háček or an umlaut in its name, you cannot use Safari for Wikia.
Sorry, I cannot test anything Wikia-related in Safari right now. Wikia is 100% completely dysfunctional in Safari for me. Dead as dead can be. I filed a bug report last November...
It's not a tardis-specific issue. The Share button works fine for me in Chrome and IE - here and over at tardis.