Tech:Table of contents makes too much whitespace - Revision history

Rein N.: Reverted edits by 70.87.136.2 (Talk); changed back to last version by Peterfitzgerald

2009-05-26T14:53:48Z

Reverted edits by 70.87.136.2 (Talk); changed back to last version by Peterfitzgerald

70.87.136.2 at 11:33, 26 May 2009

2009-05-26T11:33:36Z

Peterfitzgerald: Reverted edits by 114.127.246.36 (Talk); changed back to last version by Cacahuate

2009-05-21T23:20:26Z

Reverted edits by 114.127.246.36 (Talk); changed back to last version by Cacahuate

114.127.246.36 at 22:06, 21 May 2009

2009-05-21T22:06:38Z

Cacahuate: fixed... if any bugs persist, create a new tech request for them

2008-09-04T04:16:49Z

fixed... if any bugs persist, create a new tech request for them

76.203.51.14 at 01:16, 21 August 2007

2007-08-21T01:16:45Z

76.203.51.14 at 01:11, 21 August 2007

2007-08-21T01:11:49Z

Cacahuate: /* What should happen */ strike 2 of the items that Evan fixed... but others remain

2007-07-15T04:52:20Z

‎What should happen: strike 2 of the items that Evan fixed... but others remain

Gorilla Jones: /* How to fix it */

2007-07-13T01:48:28Z

‎How to fix it

Gorilla Jones: /* How to fix it */

2007-07-01T21:47:26Z

‎How to fix it

@@ Line 1: / Line 1: @@
 ''Moved from [[:en:Wikitravel:Bug reports]] by [[User:Evan|Evan]]''
@@ Line 84: / Line 41: @@
 ::::IMO, the ToC displayed at http://wikitravel.org/review/Munich is aesthetically an improvement on the current version but a leap backwards in so far as it does not allow the position to be customised. I think that you need to be realistic and recognise that, since beauty is in the eye of the beholder, a humna will usually do a more elegant job of placement than an algorithm.
-::::My suggestion would be to have the ToC appear automatically by default in a position to the right of the left hand margin (ie where it is in the Paris example) BUT immediately below the heading of the first section [ie NOT competing with the introduction (and often an infobox)] but then also allow its position to be customized by specific intelligent human placement if that default position produces ugliness or excessive white space on the page. ...[[User:Gaimhreadhan|<font color="green">Gaimhreadhan</font><sup> <font color="brown"><small>(kiwiexile at DMOZ)</small></font></sup>]]  â¢ 00:43, 24 March 2007 GMT
+::::My suggestion would be to have the ToC appear automatically by default in a position to the right of the left hand margin (ie where it is in the Paris example) BUT immediately below the heading of the first section [ie NOT competing with the introduction (and often an infobox)] but then also allow its position to be customized by specific intelligent human placement if that default position produces ugliness or excessive white space on the page. ...[[User:Gaimhreadhan|<font color="green">Gaimhreadhan</font><sup> <font color="brown"><small>(kiwiexile at DMOZ)</small></font></sup>]]  • 00:43, 24 March 2007 GMT
 :::::Thoughts:
@@ Line 124: / Line 81: @@
 '''3) Do a bit of future-proofing for clever stuff to come.'''
-If you follow my suggestion, then you will have substantially eliminated the need for customised ToC placement! <br />...[[User:Gaimhreadhan|<font color="green">Gaimhreadhan</font><sup> <font color="brown"><small>(kiwiexile at DMOZ)</small></font></sup>]]  â¢ 22:43, 25 March 2007 BST
+If you follow my suggestion, then you will have substantially eliminated the need for customised ToC placement! <br />...[[User:Gaimhreadhan|<font color="green">Gaimhreadhan</font><sup> <font color="brown"><small>(kiwiexile at DMOZ)</small></font></sup>]]  • 22:43, 25 March 2007 BST
@@ Line 186: / Line 143: @@
 :d) Default to fully expanded on both display and print but initiate a user-settable preference under "skin" (perhaps label it the "treesaver" skin), that hides the ToC when printing.<br />
 :e) make sure that the appearance of the [+] (expand) and [-] (contract) symbols changes when a user hovers the mouse over them. My suggestion would be to have them slightly smaller in appearance to begin with and then slightly enlarge and in bold font when they are mouse-overed...
-:[[User:Gaimhreadhan|<font color="green">Gaimhreadhan</font><sup> <font color="brown"><small>(kiwiexile at DMOZ)</small></font></sup>]]  â¢  08:32, 6 April 2007 (EDT)
+:[[User:Gaimhreadhan|<font color="green">Gaimhreadhan</font><sup> <font color="brown"><small>(kiwiexile at DMOZ)</small></font></sup>]]  •  08:32, 6 April 2007 (EDT)
 ::Responses here: 1) good idea. 2a) I think that expanding the ToC fully by default would take up too much space, without much benefit. It's not crucially important that newbies who aren't familiar with twist-down tree controls (which is a pretty small segment of the computer-using population) click directly to second-level headings. If someone can't figure out how to click to "By boat", they'll still be able to click to "Get in". 2b) I'm not excited about having the whole ToC collapsible. In a split-pages scenario ([[Tech:Optionally split long guides into one page per section]]), the ToC becomes essential navigation between pages, and hiding it is a bad idea. 2c) I'm going to make it so that the ToC never shows up in print, so this is unnecessary. 2d) same. 2e) I'll try, but again I don't think it's a tragedy if a novice user can't expand the ToC.
@@ Line 229: / Line 186: @@
 :So, you shouldn't see bullets ''at all''. Can you force-reload a page so you get the new version of the CSS file? --[[User:Evan|Evan]] 12:38, 10 May 2007 (EDT)
-:: I think he does not speak about bullets ''in'' the TOC but ''next'' to it. See [[:de:MÃ¼nchen]]. If your browser window is wide enough the bullet list in the first paragraph will be next to the TOC. The bullets are too much on the left. Make your browser windows smaller so the list will move under the TOC, then you can see how it should look like. If you want, I could make a screenshot. --[[User:Flip666|Flip666]] [[User_talk:Flip666|<sup>writeme!</sup>]] &bull; 12:46, 10 May 2007 (EDT)
+:: I think he does not speak about bullets ''in'' the TOC but ''next'' to it. See [[:de:München]]. If your browser window is wide enough the bullet list in the first paragraph will be next to the TOC. The bullets are too much on the left. Make your browser windows smaller so the list will move under the TOC, then you can see how it should look like. If you want, I could make a screenshot. --[[User:Flip666|Flip666]] [[User_talk:Flip666|<sup>writeme!</sup>]] &bull; 12:46, 10 May 2007 (EDT)
 ::: Ah. Yeah, could you? I'm not seeing it. --[[User:Evan|Evan]] 13:21, 10 May 2007 (EDT)
@@ Line 261: / Line 218: @@
 :::d) Have the following phrase in blue and smaller font and centred just below this: "<font color="blue">(hide for printing)</font>" If you do this then you will remove the need for custom ToC placement altogether since experienced and/or perceptive users will twig that they can save paper by hiding the ToC before printing<br />
-:::If you follow my suggestions, then you will have substantially eliminated the need for customised ToC placement! <br />...[[User:Gaimhreadhan|<font color="green">Gaimhreadhan</font><sup> <font color="brown"><small>(kiwiexile at DMOZ)</small></font></sup>]]  â¢ 19:43, 20 May 2007 BST
+:::If you follow my suggestions, then you will have substantially eliminated the need for customised ToC placement! <br />...[[User:Gaimhreadhan|<font color="green">Gaimhreadhan</font><sup> <font color="brown"><small>(kiwiexile at DMOZ)</small></font></sup>]]  • 19:43, 20 May 2007 BST
 :'''Strongly disagree''' with TOC being expanded by default. It being collapsed is the '''best''' thing about the new TOC... and solves the whole problem we're addressing in the first place... the excess of whitespace. &ndash; [[User:Cacahuate|<font color="green">cacahuate</font>]]  <sup><small>[[User talk:Cacahuate|<font color="blue">talk</font>]]</small></sup> 02:37, 23 May 2007 (EDT)

@@ Line 1: / Line 1: @@
 ''Moved from [[:en:Wikitravel:Bug reports]] by [[User:Evan|Evan]]''
@@ Line 41: / Line 84: @@
 ::::IMO, the ToC displayed at http://wikitravel.org/review/Munich is aesthetically an improvement on the current version but a leap backwards in so far as it does not allow the position to be customised. I think that you need to be realistic and recognise that, since beauty is in the eye of the beholder, a humna will usually do a more elegant job of placement than an algorithm.
-::::My suggestion would be to have the ToC appear automatically by default in a position to the right of the left hand margin (ie where it is in the Paris example) BUT immediately below the heading of the first section [ie NOT competing with the introduction (and often an infobox)] but then also allow its position to be customized by specific intelligent human placement if that default position produces ugliness or excessive white space on the page. ...[[User:Gaimhreadhan|<font color="green">Gaimhreadhan</font><sup> <font color="brown"><small>(kiwiexile at DMOZ)</small></font></sup>]]  • 00:43, 24 March 2007 GMT
+::::My suggestion would be to have the ToC appear automatically by default in a position to the right of the left hand margin (ie where it is in the Paris example) BUT immediately below the heading of the first section [ie NOT competing with the introduction (and often an infobox)] but then also allow its position to be customized by specific intelligent human placement if that default position produces ugliness or excessive white space on the page. ...[[User:Gaimhreadhan|<font color="green">Gaimhreadhan</font><sup> <font color="brown"><small>(kiwiexile at DMOZ)</small></font></sup>]]  â¢ 00:43, 24 March 2007 GMT
 :::::Thoughts:
@@ Line 81: / Line 124: @@
 '''3) Do a bit of future-proofing for clever stuff to come.'''
-If you follow my suggestion, then you will have substantially eliminated the need for customised ToC placement! <br />...[[User:Gaimhreadhan|<font color="green">Gaimhreadhan</font><sup> <font color="brown"><small>(kiwiexile at DMOZ)</small></font></sup>]]  • 22:43, 25 March 2007 BST
+If you follow my suggestion, then you will have substantially eliminated the need for customised ToC placement! <br />...[[User:Gaimhreadhan|<font color="green">Gaimhreadhan</font><sup> <font color="brown"><small>(kiwiexile at DMOZ)</small></font></sup>]]  â¢ 22:43, 25 March 2007 BST
@@ Line 143: / Line 186: @@
 :d) Default to fully expanded on both display and print but initiate a user-settable preference under "skin" (perhaps label it the "treesaver" skin), that hides the ToC when printing.<br />
 :e) make sure that the appearance of the [+] (expand) and [-] (contract) symbols changes when a user hovers the mouse over them. My suggestion would be to have them slightly smaller in appearance to begin with and then slightly enlarge and in bold font when they are mouse-overed...
-:[[User:Gaimhreadhan|<font color="green">Gaimhreadhan</font><sup> <font color="brown"><small>(kiwiexile at DMOZ)</small></font></sup>]]  •  08:32, 6 April 2007 (EDT)
+:[[User:Gaimhreadhan|<font color="green">Gaimhreadhan</font><sup> <font color="brown"><small>(kiwiexile at DMOZ)</small></font></sup>]]  â¢  08:32, 6 April 2007 (EDT)
 ::Responses here: 1) good idea. 2a) I think that expanding the ToC fully by default would take up too much space, without much benefit. It's not crucially important that newbies who aren't familiar with twist-down tree controls (which is a pretty small segment of the computer-using population) click directly to second-level headings. If someone can't figure out how to click to "By boat", they'll still be able to click to "Get in". 2b) I'm not excited about having the whole ToC collapsible. In a split-pages scenario ([[Tech:Optionally split long guides into one page per section]]), the ToC becomes essential navigation between pages, and hiding it is a bad idea. 2c) I'm going to make it so that the ToC never shows up in print, so this is unnecessary. 2d) same. 2e) I'll try, but again I don't think it's a tragedy if a novice user can't expand the ToC.
@@ Line 186: / Line 229: @@
 :So, you shouldn't see bullets ''at all''. Can you force-reload a page so you get the new version of the CSS file? --[[User:Evan|Evan]] 12:38, 10 May 2007 (EDT)
-:: I think he does not speak about bullets ''in'' the TOC but ''next'' to it. See [[:de:München]]. If your browser window is wide enough the bullet list in the first paragraph will be next to the TOC. The bullets are too much on the left. Make your browser windows smaller so the list will move under the TOC, then you can see how it should look like. If you want, I could make a screenshot. --[[User:Flip666|Flip666]] [[User_talk:Flip666|<sup>writeme!</sup>]] &bull; 12:46, 10 May 2007 (EDT)
+:: I think he does not speak about bullets ''in'' the TOC but ''next'' to it. See [[:de:MÃ¼nchen]]. If your browser window is wide enough the bullet list in the first paragraph will be next to the TOC. The bullets are too much on the left. Make your browser windows smaller so the list will move under the TOC, then you can see how it should look like. If you want, I could make a screenshot. --[[User:Flip666|Flip666]] [[User_talk:Flip666|<sup>writeme!</sup>]] &bull; 12:46, 10 May 2007 (EDT)
 ::: Ah. Yeah, could you? I'm not seeing it. --[[User:Evan|Evan]] 13:21, 10 May 2007 (EDT)
@@ Line 218: / Line 261: @@
 :::d) Have the following phrase in blue and smaller font and centred just below this: "<font color="blue">(hide for printing)</font>" If you do this then you will remove the need for custom ToC placement altogether since experienced and/or perceptive users will twig that they can save paper by hiding the ToC before printing<br />
-:::If you follow my suggestions, then you will have substantially eliminated the need for customised ToC placement! <br />...[[User:Gaimhreadhan|<font color="green">Gaimhreadhan</font><sup> <font color="brown"><small>(kiwiexile at DMOZ)</small></font></sup>]]  • 19:43, 20 May 2007 BST
+:::If you follow my suggestions, then you will have substantially eliminated the need for customised ToC placement! <br />...[[User:Gaimhreadhan|<font color="green">Gaimhreadhan</font><sup> <font color="brown"><small>(kiwiexile at DMOZ)</small></font></sup>]]  â¢ 19:43, 20 May 2007 BST
 :'''Strongly disagree''' with TOC being expanded by default. It being collapsed is the '''best''' thing about the new TOC... and solves the whole problem we're addressing in the first place... the excess of whitespace. &ndash; [[User:Cacahuate|<font color="green">cacahuate</font>]]  <sup><small>[[User talk:Cacahuate|<font color="blue">talk</font>]]</small></sup> 02:37, 23 May 2007 (EDT)

@@ Line 1: / Line 1: @@
 ''Moved from [[:en:Wikitravel:Bug reports]] by [[User:Evan|Evan]]''
@@ Line 42: / Line 41: @@
 ::::IMO, the ToC displayed at http://wikitravel.org/review/Munich is aesthetically an improvement on the current version but a leap backwards in so far as it does not allow the position to be customised. I think that you need to be realistic and recognise that, since beauty is in the eye of the beholder, a humna will usually do a more elegant job of placement than an algorithm.
-::::My suggestion would be to have the ToC appear automatically by default in a position to the right of the left hand margin (ie where it is in the Paris example) BUT immediately below the heading of the first section [ie NOT competing with the introduction (and often an infobox)] but then also allow its position to be customized by specific intelligent human placement if that default position produces ugliness or excessive white space on the page. ...[[User:Gaimhreadhan|<font color="green">Gaimhreadhan</font><sup> <font color="brown"><small>(kiwiexile at DMOZ)</small></font></sup>]]  â¢ 00:43, 24 March 2007 GMT
+::::My suggestion would be to have the ToC appear automatically by default in a position to the right of the left hand margin (ie where it is in the Paris example) BUT immediately below the heading of the first section [ie NOT competing with the introduction (and often an infobox)] but then also allow its position to be customized by specific intelligent human placement if that default position produces ugliness or excessive white space on the page. ...[[User:Gaimhreadhan|<font color="green">Gaimhreadhan</font><sup> <font color="brown"><small>(kiwiexile at DMOZ)</small></font></sup>]]  • 00:43, 24 March 2007 GMT
 :::::Thoughts:
@@ Line 82: / Line 81: @@
 '''3) Do a bit of future-proofing for clever stuff to come.'''
-If you follow my suggestion, then you will have substantially eliminated the need for customised ToC placement! <br />...[[User:Gaimhreadhan|<font color="green">Gaimhreadhan</font><sup> <font color="brown"><small>(kiwiexile at DMOZ)</small></font></sup>]]  â¢ 22:43, 25 March 2007 BST
+If you follow my suggestion, then you will have substantially eliminated the need for customised ToC placement! <br />...[[User:Gaimhreadhan|<font color="green">Gaimhreadhan</font><sup> <font color="brown"><small>(kiwiexile at DMOZ)</small></font></sup>]]  • 22:43, 25 March 2007 BST
@@ Line 144: / Line 143: @@
 :d) Default to fully expanded on both display and print but initiate a user-settable preference under "skin" (perhaps label it the "treesaver" skin), that hides the ToC when printing.<br />
 :e) make sure that the appearance of the [+] (expand) and [-] (contract) symbols changes when a user hovers the mouse over them. My suggestion would be to have them slightly smaller in appearance to begin with and then slightly enlarge and in bold font when they are mouse-overed...
-:[[User:Gaimhreadhan|<font color="green">Gaimhreadhan</font><sup> <font color="brown"><small>(kiwiexile at DMOZ)</small></font></sup>]]  â¢  08:32, 6 April 2007 (EDT)
+:[[User:Gaimhreadhan|<font color="green">Gaimhreadhan</font><sup> <font color="brown"><small>(kiwiexile at DMOZ)</small></font></sup>]]  •  08:32, 6 April 2007 (EDT)
 ::Responses here: 1) good idea. 2a) I think that expanding the ToC fully by default would take up too much space, without much benefit. It's not crucially important that newbies who aren't familiar with twist-down tree controls (which is a pretty small segment of the computer-using population) click directly to second-level headings. If someone can't figure out how to click to "By boat", they'll still be able to click to "Get in". 2b) I'm not excited about having the whole ToC collapsible. In a split-pages scenario ([[Tech:Optionally split long guides into one page per section]]), the ToC becomes essential navigation between pages, and hiding it is a bad idea. 2c) I'm going to make it so that the ToC never shows up in print, so this is unnecessary. 2d) same. 2e) I'll try, but again I don't think it's a tragedy if a novice user can't expand the ToC.
@@ Line 187: / Line 186: @@
 :So, you shouldn't see bullets ''at all''. Can you force-reload a page so you get the new version of the CSS file? --[[User:Evan|Evan]] 12:38, 10 May 2007 (EDT)
-:: I think he does not speak about bullets ''in'' the TOC but ''next'' to it. See [[:de:MÃ¼nchen]]. If your browser window is wide enough the bullet list in the first paragraph will be next to the TOC. The bullets are too much on the left. Make your browser windows smaller so the list will move under the TOC, then you can see how it should look like. If you want, I could make a screenshot. --[[User:Flip666|Flip666]] [[User_talk:Flip666|<sup>writeme!</sup>]] &bull; 12:46, 10 May 2007 (EDT)
+:: I think he does not speak about bullets ''in'' the TOC but ''next'' to it. See [[:de:München]]. If your browser window is wide enough the bullet list in the first paragraph will be next to the TOC. The bullets are too much on the left. Make your browser windows smaller so the list will move under the TOC, then you can see how it should look like. If you want, I could make a screenshot. --[[User:Flip666|Flip666]] [[User_talk:Flip666|<sup>writeme!</sup>]] &bull; 12:46, 10 May 2007 (EDT)
 ::: Ah. Yeah, could you? I'm not seeing it. --[[User:Evan|Evan]] 13:21, 10 May 2007 (EDT)
@@ Line 219: / Line 218: @@
 :::d) Have the following phrase in blue and smaller font and centred just below this: "<font color="blue">(hide for printing)</font>" If you do this then you will remove the need for custom ToC placement altogether since experienced and/or perceptive users will twig that they can save paper by hiding the ToC before printing<br />
-:::If you follow my suggestions, then you will have substantially eliminated the need for customised ToC placement! <br />...[[User:Gaimhreadhan|<font color="green">Gaimhreadhan</font><sup> <font color="brown"><small>(kiwiexile at DMOZ)</small></font></sup>]]  â¢ 19:43, 20 May 2007 BST
+:::If you follow my suggestions, then you will have substantially eliminated the need for customised ToC placement! <br />...[[User:Gaimhreadhan|<font color="green">Gaimhreadhan</font><sup> <font color="brown"><small>(kiwiexile at DMOZ)</small></font></sup>]]  • 19:43, 20 May 2007 BST
 :'''Strongly disagree''' with TOC being expanded by default. It being collapsed is the '''best''' thing about the new TOC... and solves the whole problem we're addressing in the first place... the excess of whitespace. &ndash; [[User:Cacahuate|<font color="green">cacahuate</font>]]  <sup><small>[[User talk:Cacahuate|<font color="blue">talk</font>]]</small></sup> 02:37, 23 May 2007 (EDT)

@@ Line 1: / Line 1: @@
 ''Moved from [[:en:Wikitravel:Bug reports]] by [[User:Evan|Evan]]''
@@ Line 41: / Line 42: @@
 ::::IMO, the ToC displayed at http://wikitravel.org/review/Munich is aesthetically an improvement on the current version but a leap backwards in so far as it does not allow the position to be customised. I think that you need to be realistic and recognise that, since beauty is in the eye of the beholder, a humna will usually do a more elegant job of placement than an algorithm.
-::::My suggestion would be to have the ToC appear automatically by default in a position to the right of the left hand margin (ie where it is in the Paris example) BUT immediately below the heading of the first section [ie NOT competing with the introduction (and often an infobox)] but then also allow its position to be customized by specific intelligent human placement if that default position produces ugliness or excessive white space on the page. ...[[User:Gaimhreadhan|<font color="green">Gaimhreadhan</font><sup> <font color="brown"><small>(kiwiexile at DMOZ)</small></font></sup>]]  • 00:43, 24 March 2007 GMT
+::::My suggestion would be to have the ToC appear automatically by default in a position to the right of the left hand margin (ie where it is in the Paris example) BUT immediately below the heading of the first section [ie NOT competing with the introduction (and often an infobox)] but then also allow its position to be customized by specific intelligent human placement if that default position produces ugliness or excessive white space on the page. ...[[User:Gaimhreadhan|<font color="green">Gaimhreadhan</font><sup> <font color="brown"><small>(kiwiexile at DMOZ)</small></font></sup>]]  â¢ 00:43, 24 March 2007 GMT
 :::::Thoughts:
@@ Line 81: / Line 82: @@
 '''3) Do a bit of future-proofing for clever stuff to come.'''
-If you follow my suggestion, then you will have substantially eliminated the need for customised ToC placement! <br />...[[User:Gaimhreadhan|<font color="green">Gaimhreadhan</font><sup> <font color="brown"><small>(kiwiexile at DMOZ)</small></font></sup>]]  • 22:43, 25 March 2007 BST
+If you follow my suggestion, then you will have substantially eliminated the need for customised ToC placement! <br />...[[User:Gaimhreadhan|<font color="green">Gaimhreadhan</font><sup> <font color="brown"><small>(kiwiexile at DMOZ)</small></font></sup>]]  â¢ 22:43, 25 March 2007 BST
@@ Line 143: / Line 144: @@
 :d) Default to fully expanded on both display and print but initiate a user-settable preference under "skin" (perhaps label it the "treesaver" skin), that hides the ToC when printing.<br />
 :e) make sure that the appearance of the [+] (expand) and [-] (contract) symbols changes when a user hovers the mouse over them. My suggestion would be to have them slightly smaller in appearance to begin with and then slightly enlarge and in bold font when they are mouse-overed...
-:[[User:Gaimhreadhan|<font color="green">Gaimhreadhan</font><sup> <font color="brown"><small>(kiwiexile at DMOZ)</small></font></sup>]]  •  08:32, 6 April 2007 (EDT)
+:[[User:Gaimhreadhan|<font color="green">Gaimhreadhan</font><sup> <font color="brown"><small>(kiwiexile at DMOZ)</small></font></sup>]]  â¢  08:32, 6 April 2007 (EDT)
 ::Responses here: 1) good idea. 2a) I think that expanding the ToC fully by default would take up too much space, without much benefit. It's not crucially important that newbies who aren't familiar with twist-down tree controls (which is a pretty small segment of the computer-using population) click directly to second-level headings. If someone can't figure out how to click to "By boat", they'll still be able to click to "Get in". 2b) I'm not excited about having the whole ToC collapsible. In a split-pages scenario ([[Tech:Optionally split long guides into one page per section]]), the ToC becomes essential navigation between pages, and hiding it is a bad idea. 2c) I'm going to make it so that the ToC never shows up in print, so this is unnecessary. 2d) same. 2e) I'll try, but again I don't think it's a tragedy if a novice user can't expand the ToC.
@@ Line 186: / Line 187: @@
 :So, you shouldn't see bullets ''at all''. Can you force-reload a page so you get the new version of the CSS file? --[[User:Evan|Evan]] 12:38, 10 May 2007 (EDT)
-:: I think he does not speak about bullets ''in'' the TOC but ''next'' to it. See [[:de:München]]. If your browser window is wide enough the bullet list in the first paragraph will be next to the TOC. The bullets are too much on the left. Make your browser windows smaller so the list will move under the TOC, then you can see how it should look like. If you want, I could make a screenshot. --[[User:Flip666|Flip666]] [[User_talk:Flip666|<sup>writeme!</sup>]] &bull; 12:46, 10 May 2007 (EDT)
+:: I think he does not speak about bullets ''in'' the TOC but ''next'' to it. See [[:de:MÃ¼nchen]]. If your browser window is wide enough the bullet list in the first paragraph will be next to the TOC. The bullets are too much on the left. Make your browser windows smaller so the list will move under the TOC, then you can see how it should look like. If you want, I could make a screenshot. --[[User:Flip666|Flip666]] [[User_talk:Flip666|<sup>writeme!</sup>]] &bull; 12:46, 10 May 2007 (EDT)
 ::: Ah. Yeah, could you? I'm not seeing it. --[[User:Evan|Evan]] 13:21, 10 May 2007 (EDT)
@@ Line 218: / Line 219: @@
 :::d) Have the following phrase in blue and smaller font and centred just below this: "<font color="blue">(hide for printing)</font>" If you do this then you will remove the need for custom ToC placement altogether since experienced and/or perceptive users will twig that they can save paper by hiding the ToC before printing<br />
-:::If you follow my suggestions, then you will have substantially eliminated the need for customised ToC placement! <br />...[[User:Gaimhreadhan|<font color="green">Gaimhreadhan</font><sup> <font color="brown"><small>(kiwiexile at DMOZ)</small></font></sup>]]  • 19:43, 20 May 2007 BST
+:::If you follow my suggestions, then you will have substantially eliminated the need for customised ToC placement! <br />...[[User:Gaimhreadhan|<font color="green">Gaimhreadhan</font><sup> <font color="brown"><small>(kiwiexile at DMOZ)</small></font></sup>]]  â¢ 19:43, 20 May 2007 BST
 :'''Strongly disagree''' with TOC being expanded by default. It being collapsed is the '''best''' thing about the new TOC... and solves the whole problem we're addressing in the first place... the excess of whitespace. &ndash; [[User:Cacahuate|<font color="green">cacahuate</font>]]  <sup><small>[[User talk:Cacahuate|<font color="blue">talk</font>]]</small></sup> 02:37, 23 May 2007 (EDT)

← Older revision		Revision as of 04:16, 4 September 2008
Line 278:		Line 278:
	: I'd really like to see this issue addressed. There are a few ideas above that have the support of several users (not the fly-by-night type, either) neatly summarized by Cacahaute - ideas that do not overturn the original goal of this change, to reduce the whitespace created by the old, long ToC. That Victoria article has gotten a work-around since I bumped it, but it was quite bad (check the history) and stayed that way without getting noticed for a while. And there are still a long list of high-traffic showpiece articles (particularly countries) that look poor and would look a lot better (without much extra whitespace) if those suggestions were to be implemented. [[User:Gorilla Jones\|Gorilla Jones]] 21:48, 12 July 2007 (EDT)		: I'd really like to see this issue addressed. There are a few ideas above that have the support of several users (not the fly-by-night type, either) neatly summarized by Cacahaute - ideas that do not overturn the original goal of this change, to reduce the whitespace created by the old, long ToC. That Victoria article has gotten a work-around since I bumped it, but it was quite bad (check the history) and stayed that way without getting noticed for a while. And there are still a long list of high-traffic showpiece articles (particularly countries) that look poor and would look a lot better (without much extra whitespace) if those suggestions were to be implemented. [[User:Gorilla Jones\|Gorilla Jones]] 21:48, 12 July 2007 (EDT)

−	{{~~openbug~~}}	+	{{fixedbug}}

@@ Line 267: / Line 267: @@
 + twisty still not expanding TOC headings in Konqueror (in KDE v.3.5.6 on Kubuntu) --[[User:Rogerhc|Rogerhc]] 19:39, 21 June 2007 (EDT)
 :It works '''once only''' then stops working. And only works this once after I purge the Wikitravel page in question's cache (by clicking ''history'' and then changing the word "history" to "purge" in the URL in browser location bar, hitting return and clicking that OK button). So the code is REALLY CLOSE to working. '''Don't give up''' :-). --[[User:Rogerhc|Rogerhc]] 20:14, 21 June 2007 (EDT)
-: I studied this today and found that Konqueror does not like the negative margin-left in this part of main.css:
+: I studied this + twisty still not expanding TOC headings in Konqueror (in KDE v.3.5.6 on Kubuntu) today and found that Konqueror does not like the negative margin-left in this part of main.css:
       a.toc-arrow {
          float: left;
@@ Line 273: / Line 273: @@
          text-decoration: none;
+      }
-: Looks like a bug in Konqueror. To make Konqueror happy the spacing might be accomplished some other way. --[[User:76.203.51.14|76.203.51.14]] 21:11, 20 August 2007 (EDT)
+: Looks like a bug in Konqueror. To make Konqueror happy the spacing might be accomplished some other way. --[[User:Rogerhc|Rogerhc]] 21:11, 20 August 2007 (EDT)
 [http://wikitravel.org/en/Victoria_%28British_Columbia%29 BUMP] again... [[User:Gorilla Jones|Gorilla Jones]] 17:47, 1 July 2007 (EDT)

@@ Line 237: / Line 237: @@
 * forcing all sections to stay below the TOC - see [[:en:Image:Africa toc example.png|how Africa looks]] in my browser
-* getting the + sign to twist down (not sure if it's working in other browsers, but it's definitely not in Safari or Konqueror).
+* <strike>getting the + sign to twist down (not sure if it's working in other browsers, but it's definitely not in Safari or Konqueror).</strike> '''done'''
 * move the "contents" heading inside the box, or better yet, remove it altogether
@@ Line 243: / Line 243: @@
 * getting the "bullets out of the margin", as Todd put it... but if you fix #1 above then I think this would become irrelavent
-* supress the TOC when viewing diffs (as it used to do), to avoid having to scroll right.
+* <strike>supress the TOC when viewing diffs (as it used to do), to avoid having to scroll right.</strike> '''done'''
 Hope I got em all &ndash; [[User:Cacahuate|<font color="green">cacahuate</font>]]  <sup><small>[[User talk:Cacahuate|<font color="blue">talk</font>]]</small></sup> 16:49, 4 June 2007 (EDT)

← Older revision		Revision as of 01:48, 13 July 2007
Line 269:		Line 269:

	:: [http://wikitravel.org/en/Victoria_%28British_Columbia%29 BUMP] again... [[User:Gorilla Jones\|Gorilla Jones]] 17:47, 1 July 2007 (EDT)		:: [http://wikitravel.org/en/Victoria_%28British_Columbia%29 BUMP] again... [[User:Gorilla Jones\|Gorilla Jones]] 17:47, 1 July 2007 (EDT)
		+
		+	::: I'd really like to see this issue addressed. There are a few ideas above that have the support of several users (not the fly-by-night type, either) neatly summarized by Cacahaute - ideas that do not overturn the original goal of this change, to reduce the whitespace created by the old, long ToC. That Victoria article has gotten a work-around since I bumped it, but it was quite bad (check the history) and stayed that way without getting noticed for a while. And there are still a long list of high-traffic showpiece articles (particularly countries) that look poor and would look a lot better (without much extra whitespace) if those suggestions were to be implemented. [[User:Gorilla Jones\|Gorilla Jones]] 21:48, 12 July 2007 (EDT)

	{{openbug}}		{{openbug}}

← Older revision		Revision as of 21:47, 1 July 2007
Line 268:		Line 268:
	:It works '''once only''' then stops working. And only works this once after I purge the Wikitravel page in question's cache (by clicking ''history'' and then changing the word "history" to "purge" in the URL in browser location bar, hitting return and clicking that OK button). So the code is REALLY CLOSE to working. '''Don't give up''' :-). --[[User:Rogerhc\|Rogerhc]] 20:14, 21 June 2007 (EDT)		:It works '''once only''' then stops working. And only works this once after I purge the Wikitravel page in question's cache (by clicking ''history'' and then changing the word "history" to "purge" in the URL in browser location bar, hitting return and clicking that OK button). So the code is REALLY CLOSE to working. '''Don't give up''' :-). --[[User:Rogerhc\|Rogerhc]] 20:14, 21 June 2007 (EDT)

		+	:: [http://wikitravel.org/en/Victoria_%28British_Columbia%29 BUMP] again... [[User:Gorilla Jones\|Gorilla Jones]] 17:47, 1 July 2007 (EDT)

	{{openbug}}		{{openbug}}