Wikipedia talk:Vector: Difference between revisions

Content deleted Content added

Inline

Revision as of 07:43, 14 May 2010

Banner placement

I'm not sure if anyone is watching this page, but it seems the most appropriate place to bring up the following issue. I have a sort of banner on my user page that is supposed to cover the page title. However, when I'm using this vector beta skin, it's moved down on the page and is nowhere near where it should be. This occurs in both Firefox and Internet Explorer. Is there any way to make it appear over the page title for both the default monobook skin and for the vector skin? Tim meh (review me) 23:56, 9 August 2009 (UTC)[reply]

They've changed the underlying page structure. CSS positioning code embedded in pages as part of the wiki text might use absolute positioning and they have changed what the "containing block" is. In layman's terms, the top of the page has moved down. In technical terms the div-element with the ID of "content" has the CSS position property set to relative in monobook and the new beta has the div with the ID "bodyContent" set to "relative". The first div has an origin just above and to the left of the page header (the W in Wikipedia...) while the second div lives further down under the header. This sucks. Jack Merridew 11:32, 10 August 2009 (UTC)[reply]

Do you think you'd be able to fix the problem on my userpage? Tim meh (review me) 15:03, 10 August 2009 (UTC)[reply]

The problem with what they've done is that there is not a way to do such things that will work for both the old and the new way; they've broken the page model. Go yell at them (wherever they are). Sorry, Jack Merridew 15:09, 10 August 2009 (UTC)[reply]

Oh well. Hopefully they'll either cancel this beta or make it the default skin sometime soon. Tim meh (review me) 15:17, 10 August 2009 (UTC)[reply]

You can yell at them, but they won't listen :D. The CSS hacks are indeed HACKS. The top title icons are somewhat standardized, and will work across several skins, but anything that uses inline CSS styles to do the positioning, will always fail in all the skins that the original user is not using. This is well known, and not a bug. It is simply not supported, because the developers have no time to spend on everyone's personal CSS hack. —TheDJ (talk • contribs) 19:27, 10 August 2009 (UTC)[reply]

It seems there must be a way to have it work in both skins. See User:The Transhumanist. Those tabs are in the same position regardless of the skin being used. Tim meh (review me) 19:48, 10 August 2009 (UTC)[reply]

Nevermind, I figured it out. Thanks guys. Tim meh (review me) 19:58, 10 August 2009 (UTC)[reply]

minor and New flags are not bold on Special:Contributions

The m and N flags on Special:Contributions are not bold as they were in monobook and are in article histories. Is this intentional or could someone please look into this? —Ost (talk) 20:12, 11 August 2009 (UTC)[reply]

I'll investigate. —TheDJ (talk • contribs) 20:40, 11 August 2009 (UTC)[reply]

bugzilla:20183, thanks for reporting ! —TheDJ (talk • contribs) 20:51, 11 August 2009 (UTC)[reply]

Own buttons from personal monobook

Is there any way how to incorporate my own buttons, which I have in my own monobook.js, now vector.js, into the enhanced editing toolbar? Or do I have to choose, whether I will use the old toolbar with my own buttons, or the "enhanced" one without them? Thank you. Jan.Kamenicek (talk) 09:24, 23 August 2009 (UTC)[reply]

Yes and no. Yes, theoretically, it can be done. No, implementing that at this time would be a huge waste of time, because it is difficult to do, and an updated toolbar will be coming this month, which will make it much easier to add buttons. —TheDJ (talk • contribs) 10:54, 23 August 2009 (UTC)[reply]

Thank you very much for the answer. --Jan.Kamenicek (talk) 12:47, 23 August 2009 (UTC)[reply]

Tabs on Special pages

Is there a way to have tabs or the drop-down arrow on Special pages? I used a tool to toggle certain edits on Special:Contributions, but the tab to access the tool doesn't show up in Vector. —Ost (talk) 18:52, 26 August 2009 (UTC)[reply]

Move button

I'm running the vector skin and I can't move a page since there is no "move" button at the top. I would have to temporarily switch back to the monobook skin to move pages. Will a move button get added to the vector skin? --NerdyScienceDude :) ^{(click here to talk to me)} 00:18, 17 December 2009 (UTC)[reply]

Mouseover the arrow next to the watchlist button and "move" should be the first option. Tim meh 00:59, 17 December 2009 (UTC)[reply]

Thanks! --NerdyScienceDude :) ^{(click here to talk to me)} 03:50, 17 December 2009 (UTC)[reply]

Namespace differentiation

Is there any way to modify my vector.css by namespace? On Monobook, I have it set up so that the main namespace displays in serif font and all others in sans; I'd like to keep this behavior with Vector, but I'm not sure if there's a way to do it. —Scott5114 ↗ [EXACT CHANGE ONLY] 08:31, 6 April 2010 (UTC)[reply]

Just move this part of your monobook.css to your vector.css. —TheDJ (talk • contribs) 12:56, 9 April 2010 (UTC)[reply]

* serif font for page content */
.ns-0 * #content {
    font-family: serif;
}

This appears to not be working; when using Vector, everything is still shown in sans-serif. —Scott5114 ↗ [EXACT CHANGE ONLY] 10:44, 20 April 2010 (UTC)[reply]

Just left a rant in beta feedback concerning the size of the font used in Vector. I have adjusted the size of the font in my browser to what is comfortable for me to read. But Vector appears to be using a stylesheet containing #bodyContent { font-size:0.8em; };. What on earth is the justification for making the font size 20% smaller? I suggest that if the developers find 1em too large that they decrease the font sizes used by their own browsers and leave the rest of us alone. Was anyone with middle-aged eyes involved in such a bone-headed decision? Yes, it's bone-headed to make the project unusable to a huge and rapidly growing segement of the population. It's especially bone-headed to make it unusable under the banner of a "usability initiative"!

I can (and have) changed that #bodyContent setting in my personal space vector.css. That doesn't help anyone who tries to use the project without logging in, and I posit that it defeats "usability" to make every joe learn how to edit CSS before they can read the articles comfortably. --Kbh3^rd talk 02:21, 9 April 2010 (UTC)[reply]

It's raining men

Why are there men on every button I click? This new skin is dreadful Gnevin (talk) 11:12, 13 May 2010 (UTC)[reply]

I'm not sure I understand what is happening to you, but likely it has nothing to do with the new skin. Please provide details (browser, for example). Dodoïste (talk) 14:30, 13 May 2010 (UTC)[reply]

File:Rainingmen.GIF Gnevin (talk) 15:43, 13 May 2010 (UTC)[reply]

Open "tab" in new IE tab

I can't seem to rightclick and open the new Vector tabs in new IE tabs/windows anymore. When I'm looking at the article, I tried to right-click on "Discussion" so that I could open that in a new tab and see both article and talk page. The little popup menu doesn't give me that option, just "Save as background", etc. It works if you right-click the links at the top (My watchlist, etc). Is this a new "feature" of Vector, or is there a way I can fix this? I'm using IE 7. Karanacs (talk) 14:51, 13 May 2010 (UTC)[reply]

That is definitely weird behaviour from IE. Firefox and Chrome both give the "Open in new tab/window" option when you right click those tabs, but IE doesn't - I can't think why.
Here's something even more peculiar - in IE, move your mouse over the tab, right click - sure enough no "New Tab/Window" option.....
* But try this - move your mouse over the tab till the link underlines, then move it very slightly down, under the wording, but still on the tab, and try right clicking again - if you did it "right" - there's the correct "new window/tab" option !!!
It could be because the "label" is in a <span> tag inside the <a> tag and IE doesn't give the option for right clicking the span, while the other browsers recognise it's contained in an <a> tag - so they do - gotta love IE and its quirky ways ! Begoon (talk) 21:23, 13 May 2010 (UTC)[reply]

I tried moving it slightly and wasn't able to see the menu, so I've reverted to monobook. Someone else filed a bug report on this [1], and it looks like you are right about the cause. Karanacs (talk) 21:28, 13 May 2010 (UTC)[reply]

I'm not surprised you couldn't get the menu - it's too fiddly to do to be useful - I actually filed a bug after posting above, which was marked as a duplicate of the one you note above - I should search better before bug reporting... Begoon (talk) 21:44, 13 May 2010 (UTC)[reply]

As a "partial workaround", from https://bugzilla.wikimedia.org/show_bug.cgi?id=23490

--- Comment #4 from Derk-Jan Hartman 2010-05-14 02:34:34 CEST --- For users looking for a workaround. If you have a middle mouse button and use that to click, the page is opened in a new tab.
Begoon (talk) 00:56, 14 May 2010 (UTC)[reply]

Search box in left sidebar

I like Vector - but I was also very fond of the Search box being in the left sidebar. So I did a hack in my personal user vector.css to move it back. The code is at User:Begoon/vector.css
If anyone would like to copy it, feel free to put it in your own User:xxxxxxx/vector.css. Note: After saving, you have to bypass your browser's cache to see the changes.
Just be aware I haven't tested it on every page yet - but it seems to be working so far for me. Begoon (talk) 14:57, 13 May 2010 (UTC)[reply]

That is exactly how it should be man. Or atleast, the box should expand to the left showing the long titles in full. I'm working on a 20" widescreen that is 1600 pixels wide and Wikipedia shows my query suggestions in like 3% of my screen space. Who designs these things anyway? - Karunyan, 06:09, 14 May 2010 (UTC)[reply]

If you just want it wider, then put something like:

#simpleSearch input#searchInput {width:27em;}

in User:Karunyans/vector.css

That will make it 3 times as wide as it is now (9em) - adjust to suit...Begoon (talk) 06:30, 14 May 2010 (UTC)[reply]

Thanks for your quick reply man. Your suggestion worked really well but I'm not using it for a few reasons:
1) I have other problems with the skin.
2) I don't usually log in when I read or even when I edit.

Now my question is, can you make it like the old searchbox that was just as small but expands when you type a long title, and when the title is still too long, you get a tooltip by pointing at it...? -- Karunyan, 07:00, 14 May 2010 (UTC)[reply]

lol...:) Not without an awful lot of changes to custom css and javascript, and probably not this side of Xmas at the speed I'd work it out. With that much hacking of the search box, and the point you so rightly make that all of this only works if you're logged in - I think I'd be back with monobook if it was that important to me. I'm happy enough to have it back in the left sidebar where I like it. Begoon (talk) 07:27, 14 May 2010 (UTC)[reply]

Hey you have any idea who is responsible for all this techie stuff on Wikipedia? I'd like to talk to them. -- Karunyan, 07:43, 14 May 2010 (UTC)[reply]

Other wikis

Is it possible to use the Vector skin on other MediaWiki wikis? Is it included as an option in a future MediaWiki upgrade or does it have to be installed manually somehow? --90.196.43.19 (talk) 16:15, 13 May 2010 (UTC)[reply]

Vector will be in the 1.16 release. 1.16beta2 is already available for download and includes Vector. --Catrope (talk) 17:50, 13 May 2010 (UTC)[reply]

Thanks. --90.196.43.19 (talk) 21:12, 13 May 2010 (UTC)[reply]

Language options

The one thing I miss from the old MonoBook layout was the ability to see an article in different languages. It was helpful because I could look up the word on English Wikipedia and click on the language(s) that I want to see the article in. Now I have to find out what the page title is in that language, and then type in the address (or sometimes search for the English word if it's in the article). Is there any chance that this feature will be added back (maybe as a drop-down menu to reduce clutter for people who have no need for it)? 76.205.67.36 (talk) 22:10, 13 May 2010 (UTC)[reply]

~~Yeah. Seriously. I don't see why they'd simply blindly make this the default layout without thinking about how much they're subtracting!~~ - Karunyan, 06:14, 14 May 2010 (UTC)[reply]

Sorry, my bad. - Karunyan, 06:19, 14 May 2010 (UTC)[reply]

List of tools missing in the edit window that were in the old skin

<math> tag
horizontal line
<s> tag
comment
<blockquote> tag
Ctrl+Z capability after clicking tools.

Honestly this was too early to make this thing default. -- Karunyan, 07:33, 14 May 2010 (UTC)[reply]

@@ Line 80: / Line 80: @@
 :Thanks for your quick reply man. Your suggestion worked really well but I'm not using it for a few reasons:<br />1) I have other problems with the skin.<br />2) I don't usually log in when I read or even when I edit.<br /><br />Now my question is, can you make it like the old searchbox that was just as small but ''expands'' when you type a long title, and when the title is still too long, you get a tooltip by pointing at it...? --[[User_talk:Karunyans| Karunyan]],  07:00, 14 May 2010 (UTC)
 :: lol...:) Not without an awful lot of changes to custom css and javascript, and probably not this side of Xmas at the speed I'd work it out. With that much hacking of the search box, and the point you so rightly make that all of this only works if you're logged in - I think I'd be back with monobook if it was that important to me. I'm happy enough to have it back in the left sidebar where I like it. [[User:Begoon|Begoon]] ([[User talk:Begoon|talk]]) 07:27, 14 May 2010 (UTC)
+:Hey you have any idea who is responsible for all this techie stuff on Wikipedia? I'd like to talk to them. --[[User_talk:Karunyans| Karunyan]],  07:43, 14 May 2010 (UTC)
 == Other wikis ==