User talk:Waldyrious/global.css

From Meta, a Wikimedia project coordination wiki

Next up:

  • icon tabs (like the watch tab). Can it be done in pure css? maybe...
  • .wikiEditor-ui { border: solid silver 1px; } (in common.css)
  • can we properly size the edit summary box?

To do (Javascript):

  • 6 tabs-like tab groups
  • move sidebar toolbox into tabs (tabs = page tools, sidebar = site tools)
    • any chance to do this with css only? the js tab rearrangement code might not like it, but we'll see.
  • Add links on each section to go back to top (js)
  • Fade in the shadow (make it invisible when page is not scrolled)
  • User:Krinkle/Scripts/InsertWikiEditorButton

Bugs:

  • fix display of move tab (& other extra ones)
  • wiktionary displays a gap between the tabs and the header. investigate.
  • anchor issues:
    • references, both up and down (needs to be done via javascript, to change the target of the anchors to the <a> elements inside the <li>s rather than the <li>s themselves...)
    • bugzilla:31932 will also break this for headings...
    • anchors in preferences
    • unwatch notice
    • pretty much any anchored element (e.g. shortcuts, etc.)
    • potential solutions/hacks:
      • a workaround in pure css might not be possible, even if the body and html tags are displaced...
      • what if we use the :target selector to provide the padding? but then it doesn't disappear once one scrolls away... javascript? :(
  • scrolling of sidebar and main content seem to be coupled for some browsers.
    • Tested on FF 9.0 @ Ubuntu 11.04 and both mouse scrollbar and keyboard arrows (after proper focus is provided) work well
  • #firstHeader should be 100% of #content, not <body>. or maybe #content needs to be changed to box-sizing:content-box.
  • sidebar scrollbar should not displace its contents when it appears/disappears. perhaps check how gmail does this. Also might be relevant: Google gmail on iPad: how do they scroll just the right hand side of the page? (StackOverflow)
  • the title element, when overflow happens, wraps around and obscures content below.

Stuff to actually change in the core vector skin (submit to bugzilla):

  • #mw-page-base and #mw-head-base need to have more descriptive names
  • #mw-usercsspreview is redundant with div.previewnote
  • pre fixes (font size, wrap, overflow & solid border)
  • #editpage-specialchars>select shouldn't float (much less using inline styles!)
  • #contentSub should be at the same level as #firstHeading (i.e, outside #bodyContent)
  • edit summary box style should match other text boxes
  • cursor should be automatically placed in edit box when editing pages
  • does the edit window get bigger than it should? maybe because of the borders? check it out.
  • should div.wm-content-ltr have an extra, non-directional dependent class so it can be styled (e.g. contentbody)?

Misc.

  • Designing Gmail’s new left navigation (Gmail blog) — "One of our goals for Gmail's new look was to make Gmail feel more like a native application with independently scrolling panels rather than a website that scrolls as a single page. This design approach brings with it many advantages: the search box and primary navigation are always in the same place, your inbox unread count is always visible, etc."


Comments