Tropers - The first of many exciting updates to TV Tropes is upon us! In this update, we focused primarily on making the header and side navigation bars consistent throughout the site. We also reworked a ton of the backend code to allow for easier and more rapid development as we move forward.
Some of you may love the new design, others may hate it. Either way, we would love to hear from you below. We are listening, I promise.
If you have a bug to report, please use the designated thread
on the Tech Wishlist and Bug Report to let us know about it.
Now get back to Troping!
edited 20th Apr '15 2:10:15 PM by drewski
No, I'm talking about a "Switch to mobile" version, not switch to desktop, which I see.
And seeing it on a phone is a given, since a phone will have a smaller resolution. I would like to see that option at larger resolutions as well.
When I shrink the window and it automagically switches to mobile, there is a Switch to Desktop option. If I use that and leave the window at its smaller resolution, there is a Switch to Mobile option. But with the window at regular resolution, there is no Switch to Mobile version.
edited 8th Feb '15 8:18:00 AM by SolipSchism
The "Switch to desktop" link only happens in the mobile version. Which appears based on width
◊
Yes, I'm aware of that, which is why I've explicitly mentioned it twice, including those exact words in the first sentence of my first post on the subject. My suggestion is that the option be available regardless of width.
edited 8th Feb '15 8:19:09 AM by SolipSchism
...whoops, misread your suggestion. Perhaps I should finish my coffee before commenting on things. ^_^;;
edited 8th Feb '15 9:44:01 AM by Sixthhokage1
Pshaw.
It's not a hugely necessary suggestion, just something I've always appreciated as an option.
But then, I believe the "mobile version" in this case is just a different stylesheet, so it probably isn't going to save any bandwidth one way or another. While traveling, I often prefer the mobile versions of sites that actually have separate pages in order to save bandwidth. It might not actually matter here.
edited 8th Feb '15 8:25:55 AM by SolipSchism
...Anyone else having a hard time editing posts in the mobile version?
It's happening on the desktop version on mobiles also.
That's the exact same error message I got.
Just flowing with it.
I've been occasionally getting HTTP 500 Errors (Internal Error) when accessing pages. Anyone experiencing the same thing?
EDIT: Never mind, I got it from other websites too. It seems the problem lies in my ISP.
edited 8th Feb '15 11:25:47 AM by FlowingCotton
Indiana Solo
Slight problem with the "darth wiki" Linked named in the folders are really hard to read with the black background.
I like the current look - there are probably a couple of minor things I would change, but it's quite alright as is. Besides, I am cautiously optimistic about all this talk of customization options.
Regarding the comments on colourblindness made over the last few pages, I am inclined to agree with those who've said that people will probably just have to wait until the customization comes in.
A potentially useful note for colourblind Mac users (I'm not sure if this will help, as I am not colourblind): to invert all colours on your computer screen (i.e. text becomes white on black), hit the Launchpad button and select System Preferences. Within System Preferences, click on the Universal Access icon. In the "seeing" section, display options are at the bottom of the window. You can click "white on black", which inverts the default colour setup. Now, this will probably funk up page images pretty bad, but it makes reading words pretty easy. Besides, reverse-disco psychedelic image mode is kind of entertaining.
rollin' on dubs
I love the mobile options, but what news of the "customization" has there been?
All night at the computer, cuz people ain't that great. I keep to myself so I won't be on The First 48
Uh, have the "drop/add to your watchlist" and "Thread watchlist" buttons changed places? Because I have an issue with that.
edited 9th Feb '15 9:16:05 AM by valozzy
![[up]](https://static.tvtropes.org/pmwiki/pub/smiles/arrow_up.png "[up]"){kind=icon}
Somewhere within the last 5 or 10 pages of this thread, it was talked about, and I believe Drewski confirmed that some customization options, including colour, would eventually be set up.
Trying out the mobile design. I like it. My only complaint is that sometimes the stuff on screen organizes itself in a wonky way. For example, here in the forums, poster's titles are besides their avatar, above the rest of their post's text. When seeing the list of subforums, the text organizes itself in a neat column, but isn't aligned with each other. Or maybe the sentences are too short to reach the right side of the page, Idk. In short, I don't have any complaint about the mobile design for now, sans minor nitpicks.
The history page is now readable on IE 9! FANTASTIC!
Whenever I click a link that is spoilered, the spoiler is automatically highlighted and the link doesn't go anywhere. Is anyone else having this problem?
The Cat Knows Where It's At
Extended Test.
No.
edited 9th Feb '15 9:36:07 PM by Zelenal
Let the joy of love give you an answer! Check out my book!
For SCIENCE!
Just checked that, and yes for me it acts like you double clicked the spoiler and the link doesn't do anything until you click it again.
Creepers: They're like raptors except they explode.
The Cat Knows Where It's At
What web browsers are you two using?
EDIT: For me, it only won't open the link if the spoiler is hidden. If it's visible, it works just fine.
edited 9th Feb '15 9:48:33 PM by Zelenal
Let the joy of love give you an answer! Check out my book!
For SCIENCE!
I'd assume it's caused by the fact that clicking it opens the spoiler now so that takes priority in effect, and yeah it works the same for me.
Creepers: They're like raptors except they explode.
(they/them)
For me (Firefox 35.0.1), the spoilered link is only clickable when the spoiler is visible. This seems like the right behavior — I've always found it annoying when I try to highlight a spoiler and instead accidentally link on a link I couldn't see.
Alright. If this is something that is supposed to happen, that's fine with me. I was just worried that I had found a glitch or that my browser (Google Chrome) had screwed up. I can deal with it just fine. Thank you.
Re: This post
Oh hey, yeah, the source segments on History pages are no longer black-on-dark-blue on my js-disabled IE9 work machine. Kudos to whoever implemented that fix!
Feature already in place, Solip
◊