Talk:MonoBook

From wikidev.net

The top of the page doesn't look right for me: the green bar goes right through the words. Screenshot (http://theory.cs.iitm.ernet.in/~arvindn/screenshots/davinci.png) --

Another thing: the green and blue vertical lines alternating in the left navbar doesn't look very good.

Arvindn 08:56, 21 Mar 2004 (CET)

Table of contents

1 Keyboard Shortcuts don't work (fixed) 2 Some stuff 3 Double clicking broken 4 More issues 5 Localized Shortcuts

Keyboard Shortcuts don't work (fixed)

Hi. On w2k, Firebird 0.7, the keyboard shortcuts used for back and forward navigation (Alt+Left and Alt+Right) don't work with this skin. :( --Sikilai

Seems to be caused by empty acceskeys, better to omit them -- gwicke

Done. Also alt-s now places the cursor in the search box. -- Gwicke 16:49, 26 Mar 2004 (CET)

Some stuff

• "Post a comment" link on talk page missing (could be a "post" tab)
• "Discussion" link should be red and lead to edit page if no talk page exists
• In Konqueror, a background image that is larger than the window resolution causes horizontal scrollbars to appear - can we fix that?
• I think the boxes should be structured differently. The top box should link to the most frequently accessed pages, while the bottom box should link to the less frequently accessed ones. I'd say the top box should link to Main Page, Recent changes, Upload file, Help, and the bottom box should link to Related changes, What links here, Special pages, Random page Donations.

--Eloquence 21:21, 6 Apr 2004 (CEST)

The scrollbar is actually a bug in khtml that's triggered by negative margins on floats. Many reports about this on the various css lists and forums, but no workaround. Red link is already noted.

I'm undecided on the post link. The tab metaphor might not be the best place for it because it really is just a subsection of the edit tab. It would be nice to have a reply button at the end of each post as well. -- Gwicke 21:40, 6 Apr 2004 (CEST)

I think posting would work well as a tab next to "edit" - it's not a subsection of the edit tab, because the behavior is actually different. There is no summary field, instead, the subject is prepended as a headline and re-used as an edit summary. Yes, reply links would be nice, but I haven't found a good way to implement this yet. Any ideas?--Eloquence 21:49, 6 Apr 2004 (CEST)

The idea is to make things easier to understand by grouping functionality into related areas. Reordering the links by popularity would break this. There are access keys specified on all often-used links, see the tooltips. -- Gwicke 21:47, 6 Apr 2004 (CEST)

If you want to group by functionality the current approach is not particularly logical. How is "Donations" a navigation link while "Help" is not? For a logical grouping I'd suggest the following: Browse: 1) Main Page, 2) Community Portal (optional) 3) Current events (optional) 4) Help, 5) Donations, 6) Contact us | Toolbox: 1) Recent changes, 2) What links here, 3) Related changes, 4) Special pages, 5) Upload file.--Eloquence 21:54, 6 Apr 2004 (CEST)

Hope you like the change from 'not particularly logical' to 'completely logical' ordering ;-) Note that you don't see portal and events because they are disabled in this install. 'Contact us' might be a good thing to put in the footer, saves one row in the main nav and is similar to 'about', 'disclaimers' etc. -- Gwicke 22:40, 6 Apr 2004 (CEST)

I still think Special:Randompage should be in the toolbox, particularly since all other pages there are now special pages, and all other pages in the top box are wiki pages.--Eloquence 09:43, 7 Apr 2004 (CEST)

Double clicking broken

In the MonoBook skin, double-clicking on page doesn't edit it, despite setting appropriate preference. Blarney 02:44, 7 Apr 2004 (CEST)

Guess the onload handler isn't attached from the js, shouldn't be in the skin really. There are some other things to be done in js (right-click on headline section editing event attached from js, '[edit]' link via dovument.write from js, possibly reply function for discussions), and i'm not really a js expert. Double-click should be fixable though. -- Gwicke 17:50, 7 Apr 2004 (CEST)

Fixed the plain way (by adding the same hardcoded ondblclick handler to body) -- Gwicke 01:08, 8 Apr 2004 (CEST)

More issues

• Subpage backlinks are not shown, see User:Eloquence/subpage test
• Category links are not shown, see category test on http://test.wikipedia.org (are shown in the standard skin)
• Footer message on anonymous talk pages is page-widening in Mozilla, see User talk:64.164.245.22 (why use PRE for it?)
• Discussion link does not go to edit page, but to "currently no text in this page", same for user name link.
• Horizontal lines run through tables in Mozilla, see http://test.wikipedia.org/wiki/Antigua_and_Barbuda
• Links in section titles are not displayed blue or red, but in black, which makes them invisible unless you hover (see linksection)

--Eloquence 20:17, 11 Apr 2004 (CEST)

• horizontal scrollbars at any resolution in Safari (v1.2.1)
  • Known khtml bug without known workaround, reported in the safari bug database.
• boxes in left sidebar lack margin-left's, look off-center
  • That's intentional. Give them some margin (div.portlet{ margin-left: 1em} or similar) in your user style if you prefer it.
• section edit links are too high above section headers, almost look like part of the previous section
• looks gorgeous otherwise, can't wait for 1.3 :)

--AnonymousCoward 03:42, 29, Apr 2004 (EST)

• the editor toolbar (buttons) deviates from the rest of the new style (ugly windows buttons are even shown under aqua/os x). if you would use button-tags (html 4), you could use native system buttons combined with the images.
• the "printable version" link is missing - should render links as plain text (undecorated) if re-integrated. the print preview looks nice, but another use is to save an article as plain html with images. now you must save the entire wikipedia page with side navigation and header.
• is it possible (in the final release) to switch the locale in user settings? i. e. can a german user switch to a german ui in the english wikipedia?
• an finally... a nice feature would be a possibility to remove a watched article from "my watchlist" (in the "my watchlist" view)

Malteser 23:20, 21 May 2004 (CEST)

Localized Shortcuts

I just noticed that the german Wikipedia has receiveed localized shortcuts (access keys). This is bad because it makes EVERY Wikipedia different to use! Please, please, please revert ALL Wikipedias to the SAME set of access keys. This feature is by far too useful to be crippled like that. --212.202.175.14 23:26, 28 May 2004 (CEST)