Memory Beta, non-canon Star Trek Wiki

A friendly reminder regarding spoilers! At present the expanded Trek universe is in a period of major upheaval with the continuations of Discovery and Prodigy, the advent of new eras in gaming with the Star Trek Adventures RPG, Star Trek: Infinite and Star Trek Online, as well as other post-57th Anniversary publications such as the ongoing IDW Star Trek comic and spin-off Star Trek: Defiant. Therefore, please be courteous to other users who may not be aware of current developments by using the {{spoiler}}, {{spoilers}} OR {{majorspoiler}} tags when adding new information from sources less than six months old (even if it is minor info). Also, please do not include details in the summary bar when editing pages and do not anticipate making additions relating to sources not yet in release. THANK YOU

READ MORE

Memory Beta, non-canon Star Trek Wiki
Advertisement

I removed the birthplace of ECS Horizon unless someone has a source for that, seems like an error accidentally copied from Mayweather's article. -- Captain MKB 11:16, July 9, 2010 (UTC)

Overlapping/"colliding" sections[]

Not all web browsers and computers have this problem, but on Google Chrome on a number of computers that I've checked, the bottom of the character information box covers half of the "Incomplete" status message box.

WikiCollision

I inserted extra space a few days ago to fix the problem, which obviously made it look worse for non-Chrome readers. Any ideas on how to address this? -- BlueResistance 11:44, June 16, 2012 (UTC)

Not sure this should be discussed on here but rather on its own talk page because this is an issue that deserves to be looked at. --Captain riggs 16:15, June 18, 2012 (UTC)
I'd be happy to make a separate talk page for this topic, but how would I go about doing that? Outside of starting talk pages for wiki articles, I have never done this before. Thanks! BlueResistance 19:05, June 18, 2012 (UTC)
There is a "clear" command that could be manually added on an article-by-article basis, but this isn't desirable because of the work involved. a better solution would be to enter whatever code is needed as a template.
however, this doesn't occur with other browsers, so i think the "top level" solution is best - add the code directly to the site's style sheet. that way, we don't have to write tons of code into every template. especially since this is an isolated case of one browser having an inferior way of handling something that works fine for everyone else. -- Captain MKB 19:22, June 18, 2012 (UTC)
Advertisement