Forum:Hover over text

From the RuneScape Wiki, the wiki for all things RuneScape
Jump to: navigation, search
Forums: Yew Grove > Hover over text
Archive
This page or section is an archive.
Please do not edit the contents of this page.
This thread was archived on 12 November 2010 by Liquidhelium.

I found [[w:c:chicken7:Sandbox|something]] on the [[w:c:chicken7|chicken7 wiki]] that might be interesting for this wiki too. Please see [[w:c:chicken7:User talk:Chicken7#Hover over sigexpand thingy|this page]](and with "quite much space" i mean this much) for what i mean(i can't show it here because it isn't added yet) I found what made the thing work on his wiki, which is at the bottom of [[w:c:chicken7:MediaWiki:Common.css|this page]]:

/* allows for expanding hidden sig sections */
.sighidden { display: none }
.sigexpand:hover .sighidden { display: inline }
.sigclick:active .sighidden { display: inline }

And i tested it on [[w:c:joeytje50|my wiki]] too([[w:c:joeytje50:Test|here]]) after adding it to [[w:c:chicken7:MediaWiki:Common.css|the common.css on my wiki]] too, and it works there too, so i don't see any problem with it. What i suggest is adding the above thing in the common.css of this wiki too, so that it could be used for quest guides, reducing space taken up because of this forum. I don't see any reasons why not, because there is nothing bad this could create.

It will be used like this:

<div class="sigexpand">(always visible text)<div class="sighidden">(hover over text)</div></div>

Suggested names

Please place your suggestions in the table below. Place the suggested name under the right column, without the <div class=" and "> around it. The "added by" column is there for the same reasons you have to sign

<div class="sigexpand"> <div class="sighidden"> Added by
showntext (example) hiddentext (example) JOEYTJE50TALKpull my finger

Discussion

Strong support - Per only advantages, and no disadvantages (imo), as nom. JOEYTJE50TALKpull my finger 17:57, October 21, 2010 (UTC)

Oh i found one small problem... If the content is added on another row, you can't click on links.(try hovering over "Quest req for Quest1" [[w:c:chicken7:User talk:Chicken7#Hover over sigexpand thingy|here]]) so i will ask chicken and quarenon for help how to fix that. I'll not go and try to fix it myself as i have no idea how mediawiki stuff works. JOEYTJE50TALKpull my finger 18:12, October 21, 2010 (UTC)
Quarenon fixed it. the problem was that div should be used instead of span. JOEYTJE50TALKpull my finger 03:54, October 24, 2010 (UTC)

Comment - Is it just or does it only work with monobook? Quest point cape.pngTalk Newbie856 edit count Nomad guideMusic icon.png 21:21, October 21, 2010 (UTC)

I use Monaco and it works there. JOEYTJE50TALKpull my finger 03:32, October 22, 2010 (UTC)

Comment - I don't really see how this would be useful. Not only that but users might not notice that this feature is enabled, and therefore might miss the hidden information. Furthermore i can't imagine this would be used to hide paragraphs worth of information, so it would only hide a line or two, and therefore save almost no space at all. kitty.pngPsycho Robot talkSilver bar.png 21:35, October 21, 2010 (UTC)

It does look like a quite long list, although it is relatively not very much indeed. and the miss part: Just add to the template: "hover over for extended quest requirements". Very simple, and i am surprised you didn't think of that. JOEYTJE50TALKpull my finger 03:32, October 22, 2010 (UTC)
I thought of that, but what is the point of hiding information that people need, thus necessitating an extra click to access it? Regardless, we shouldn't do something just because its neat, but because it benefits the clarity and completeness of our articles. It seems that this would actually hinder it. kitty.pngPsycho Robot talkSilver bar.png 08:02, October 22, 2010 (UTC)
It is not an extra click, it is just (like the forum name suggests) hovering over it. And it is not just because it is neat, it is also to reduce space taken. Also, this function could be used for other things. It can't do any harm. And even if only users are going to use it for own purposes, so what? what is the harm of that? Do you also oppose adding the function? JOEYTJE50TALKpull my finger 17:42, October 22, 2010 (UTC)
Ok fine, its not another click, but its still an extra motion and wasted time to save... a few lines of text? We don't need to save space at all, much less bad enough that we would hide parts of our information, even temporarily, to accomplish it. also I oppose now. kitty.pngPsycho Robot talkSilver bar.png 18:19, October 23, 2010 (UTC)
It is not "a few lines of text". It can grow to an enormous list at some quests. May i present you: the requirements for Recipe for Disaster/Defeating the Culinaromancer:
Which would have been the following size when using the method i suggest:
See the difference? i hope so. Also, with the current method you will think WOW!!! and it is unclear what the officially stated requirements are, and what the extended ones are. And don't say that Defeating the Culinaromancer is such a huge quest it is an exception, because of this:
And that is only the beginning, and the skill requirements aren't even included...
Also i want to repeat, what is wrong with adding the code? It can't do any harm, especially if it is not used on any mainspace articles without consensus. JOEYTJE50TALKpull my finger 03:50, October 24, 2010 (UTC)
I'm sorry, I must have accidentally said that "hover text is exactly the same as normal text". I must have if you would ask if I saw the difference. So I'll assure you that I do realise that there is a difference between the two! However I don't see the hover text as useful at all. I also don't see extended quest requirements as useful either. There are only a few quests have anywhere near enough requirements to necessitate a special method for displaying the information, and you've just now shown how its possible without having to enable any extra code - collapsed tables. kitty.pngPsycho Robot talkSilver bar.png 17:16, October 24, 2010 (UTC)
Try to put a collapsible table in a dotted list or a scentence. And what is against adding it to the css if it is not used on the quest pages? that is actually what i made this thread for, and as a reason why to add it i used this. Apparently no1 likes that idea despite my many reasons, but we could still add it and not use it on other things, for example sigs of users. JOEYTJE50TALKpull my finger 19:20, October 24, 2010 (UTC)
WHOA!!! WAIT, stop evryone, this is something we can't place on an article page without hover over text or any other way to hide it:
We must do something. The fate of the world is in our hands, guys. Psycho, still think it is just "a few lines of text"? JOEYTJE50TALKpull my finger 22:04, October 24, 2010 (UTC)
Sarcasm doesn't work over the internet. Quest.png Gaz Lloyd 7:^]Events!99s 22:38, October 24, 2010 (UTC)

Oppose - This really isn't useful or beneficial to the wiki. First of all, how will users know that they are supposed to hover over text to see additional information? They could miss critical information altogether if they don't put the mouse in the right spot. I think that we should have all of our information straight in their face. There is no need for fine print. --LiquidTalk 22:22, October 21, 2010 (UTC)

"how will users know that they are supposed to hover over text to see additional information" well, by adding "hover over for extended quest requirements" to Template:Quest details
"They could miss critical information altogether if they don't put the mouse in the right spot" well, it wasn't so critical the last 5 years... It wasn't even there...
"I think that we should have all of our information straight in their face" so you want a very long list? ok, but i don't like that very much. JOEYTJE50TALKpull my finger 03:32, October 22, 2010 (UTC)

Oppose - Incompatible with the Wikia skin is amongst This is my short list of things against hidden text (whether it is this code or the censor template). When this supports legacy skins but not the default skin is one reason to not to support this. This also provides no incentive to use anywhere on the wiki. I would not hide my signature or reason on opposition or approval of a certain action. To me, that makes no sense and looks more like vote counting than anything else if used in decision making roles, forums, and/or project namespace. Ryan PM 22:30, October 21, 2010 (UTC)

You don't have it in the Wikia.CSS do you? I still oppose based on my other points and those of other opposition. Ryan PM 22:38, October 21, 2010 (UTC)
It is not in the css, and what i propose is to add it to it actually. That's the whole point Wink That is why it doesn't work... try [[w:c:Joeytje50|My wiki]] if you wanna test this thing. JOEYTJE50TALKpull my finger 03:32, October 22, 2010 (UTC)
While it does the one thing I like (actually works on the Wikiaphone skin, but I'll wait until Wikia releases their Smartphone skin to see if it'll contain the usage for JS), I know how it works. I also like keeping my edits to this wiki, the Stellar Dawn Wiki, Community Central, and a personal test wiki (so I don't have to go and track down "X" Wiki for "y" edit). However, what I was not for it as I just dislike hidden text, albeit I use collapsible tables. However, collapsible tables don't work on the Wikiaphone skin, so I'd have to say that's the one advantage for me to use this CSS. On another note, we have things like: <span title="Ryan M's Userpage">'''Ryan'''</span> for hovering text, albeit not applicable for mobile users (and possibly screen readers, not sure though). Ryan PM 03:46, October 22, 2010 (UTC)
The hover over text you talk about(span title thing) does not support clickable links, and as seen on [[w:c:Joeytje50:Test|this page]] you can click on links with this function. JOEYTJE50TALKpull my finger 17:42, October 22, 2010 (UTC)
It does now, because it is changed to div instead of span. JOEYTJE50TALKpull my finger 03:54, October 24, 2010 (UTC)

Comment - The quest template is not the only thing we could do with it. I think the hover over thing would be useful anyway, so that's why i think it should be added, and it couldn't do any harm. JOEYTJE50TALKpull my finger 03:32, October 22, 2010 (UTC)

Comment - It doesn't work at all for me with either monaco or wikia, on either of the wikis that its supposed to work on - neither chrome or firefox on neither of windows 7 or vista. It does however work when I put the code in W3Schools Tryit HTML Editor. I looked around and I don't know whats wrong - seems likely that some other stylesheet is overriding it. Quest.png Gaz Lloyd 7:^]Events!99s 16:57, October 24, 2010 (UTC)

It must be something with your computer i think, because it works perfectly for me(and chicken7 ofcourse) and i haven't installed anything that supports extra code or something. From what year is your computer? JOEYTJE50TALKpull my finger 22:04, October 24, 2010 (UTC)
My vista computer is a little over 3 years old, my win7 one is barely 2 months old. Both chrome and firefox are fully up to date on both. Which is by the by as I've found the problem - the user agent styesheet was overriding them. So add !important to them all (also make sure to add the ;) and now it works. Quest.png Gaz Lloyd 7:^]Events!99s 22:38, October 24, 2010 (UTC)

Strong Oppose - Just not much use. HaloTalk 22:07, October 24, 2010 (UTC)

What's against it? not gonna be used often? and? what does it hurt? (this is about adding it to the .css; using it for quests might "hurt" but imo adding it can't hurt anything) JOEYTJE50TALKpull my finger 10:41, October 26, 2010 (UTC)

{{Comment}} JOEYTJE50TALKpull my finger 11:07, October 29, 2010 (UTC)

Oppose - Per above. bad_fetustalk 14:24, October 29, 2010 (UTC)

{{Closure|Discussion has died}} svco4bY.png3Gf5N2F.png 22:31, November 11, 2010 (UTC)

Closed - There is no consensus to implement this proposal. --LiquidTalk 00:15, November 12, 2010 (UTC)