Creating Talk:Main Page

Jump to navigation Jump to search
Archives: Sections of this page older than three days are automatically relocated to the newest archive.

001 002 003 004 005 006 007 008 009 010 011 012 013 014 015 016 017 018 019 020 021 022 023 024 025 026 027 028 029 030 031 032 033 034 035 036 037 038 039 040 041 042 043 044 045 046 047 048 049 050 051 052 053 054 055 056 057 058 059 060 061 062 063 064 065 066 067 068 069 070 071 072 073 074 075 076 077 078 079 080 081 082 083 084 085 086 087 088 089 090 091 092 093 094 095 096 097 098 099 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207

Main Page error reports

[edit]

To report an error in content currently or imminently on the Main Page, use the appropriate section below.

  • Where is the error? An exact quotation of the text in question helps.
  • Offer a correction if possible.
  • References are helpful, especially when reporting an obscure factual or grammatical error.
  • Time zones. The Main Page runs on Coordinated Universal Time (UTC, currently 01:34 on 13 June 2024) and is not adjusted to your local time zone.
  • Can you resolve the problem yourself? If the error lies primarily in the content of an article linked from the Main Page, fix the problem there before reporting it here. Text on the Main Page generally defers to the articles with bolded links. Upcoming content on the Main Page is usually only protected from editing beginning 24 hours before its scheduled appearance. Before that period, you can be bold and fix any issues yourself.
  • Do not use {{edit fully-protected}} on this page, which will not get a faster response. It is unnecessary, because this page is not protected, and causes display problems. (See the bottom of this revision for an example.)
  • No chit-chat. Lengthy discussions should be moved to a suitable location elsewhere, such as the talk page of the relevant article or project.
  • Respect other editors. Another user wrote the text you want changed, or reported an issue they see in something you wrote. Everyone's goal should be producing the best Main Page possible. The compressed time frame of the Main Page means sometimes action must be taken before there has been time for everyone to comment. Be civil to fellow users.
  • Reports are removed when resolved. Once an error has been addressed or determined not to be an error, or the item has been rotated off the Main Page, the report will be removed from this page. Check the revision history for a record of any discussion or action taken; no archives are kept.

Errors in the summary of the featured article

[edit]
Please do not remove this invisible timestamp. See WT:ERRORS and WP:SUBSCRIBE. - Dank (push to talk) 01:24, 29 September 2022 (UTC)[reply]
  • Caption — Not a factual error, but Wreckage from the Battle of Villers-Bocage seems unduly vague. Suggest change to "Wreckage of a British Cromwell tank at the Battle of Villers-Bocage." – Sca (talk) 00:34, 13 June 2024 (UTC)[reply]
Will expanding the caption increase the portion of the main page taken up by the TFA?--Wehwalt (talk) 00:41, 13 June 2024 (UTC)[reply]
@Wehwalt, I suggest that this is a useful addition. I've just read the item and had the exact same uncertainty; is it the tank that we are talking about? If there's an imbalance of the main page as a result, that is easily fixed by adding or deleting something at OTD. In fact, I've just done so. It happens routinely. Balance concerns should never stop us from removing ambiguity. Schwede66 00:47, 13 June 2024 (UTC)[reply]
Looks like it'll fit. Photo file says yes it's a Cromwell. I suppose "the Battle of" could be dropped from the caption for space, since the text begins with "The Battle of Villers-Bocage." – Sca (talk) 00:47, 13 June 2024 (UTC)[reply]

Errors with "In the news"

[edit]
  • StarlinerThe Boeing Starliner spacecraft conducts its first crewed flight.... – Not a factual error, but "conducts" seems too anthropomorphic. Suggest change to "completes." – Sca (talk) 01:04, 13 cJune 2024 (UTC)

Errors in "Did you know ..."

[edit]

among the 10 most challenged books in the United States in 2023 there should be some hyperlink (or something) explaining what a challenged book is. ꧁Zanahary꧂ 01:28, 13 June 2024 (UTC)[reply]

Errors in "On this day"

[edit]
  • 13 June 1881 - at "came to an end when the USS Jeannette" pls italicise Jeannette JennyOz (talk) 07:51, 12 June 2024 (UTC)[reply]
     DoneSchwede66 00:38, 13 June 2024 (UTC)[reply]
  • 1996 – After an 81-day standoff ... group Montana Freemen surrendered to the FBI. - Article (correctly) gives date as June 14 and Ref 9 NYT dated 14 June has "The last 16 members of the Freemen anti-Government group handed themselves over to Federal agents tonight, ... After 81 days of resistance, the members of the right-wing group simply climbed into Government vans..."
This item last appeared on OTD on 13 June 2012 at which time it didn't actually have a date. June 14 was added here on 21 June 2012. JennyOz (talk) 07:51, 12 June 2024 (UTC)[reply]
I've moved this to the "eligible" section of the 14 June set. Schwede66 00:38, 13 June 2024 (UTC)[reply]
[edit]
(June 14, tomorrow)
(June 17)
[edit]

General discussion

[edit]

header broken in monobook

[edit]
Resolved
 – Primary issue resolved, minor tweaks may be possible still. — xaosflux Talk 19:40, 24 May 2024 (UTC)[reply]
2024-05-23 problems

Haven't been able to check this yet, possible WP:THURSDAY issue? In monobook, the page layout is broken now, see example - with the "welcome to wikipedia" being moved, a "," on a line by itself, bad font/size as well. — xaosflux Talk 09:34, 23 May 2024 (UTC)[reply]

@Izno: just in case you are working on this via Wikipedia:Main Page/styles.css. — xaosflux Talk 09:35, 23 May 2024 (UTC)[reply]
Fixed the comma break by moving the comma in to the h1 element; not seeing that causing breaks on vector or vector22. The h1 styling here seem to be the primary problem now. — xaosflux Talk 09:44, 23 May 2024 (UTC)[reply]
Seems to be styles associated with the mw-heading1 div around that h1.. — xaosflux Talk 10:11, 23 May 2024 (UTC)[reply]
I'm seeing the same issue - it looks very ugly. Thanks for looking into this! Modest Genius talk 11:15, 23 May 2024 (UTC)[reply]
The gap between Welcome to Wikipedia and "the free encyclopedia that anyone can edit." is too big on Monobook. The line at the top cuts off the bottom of the P. I suggest you do "Welcome to" in smaller letters at the top and then just Wikipedia in large. "Welcome" looks a bit silly being that big.♦ Dr. Blofeld 11:23, 23 May 2024 (UTC)[reply]
  • Getting these reset may be enough:
body.page-Main_Page #mw-heading1
border-bottom: none;
margin-bottom: none;
font-size: 100%;
xaosflux Talk 12:02, 23 May 2024 (UTC)[reply]
 Doing... font size fix first, waiting for sync. — xaosflux Talk 12:30, 23 May 2024 (UTC)[reply]
 Done font size fixed in MediaWiki:Monobook.css; margin/border to do. — xaosflux Talk 12:36, 23 May 2024 (UTC)[reply]
 Doing... border/margin - waiting for sync. — xaosflux Talk 13:24, 23 May 2024 (UTC)[reply]
 Done I'm not sure I love these CSS hacks though. Suggestions for improvement (here or upstream) are more than welcome. — xaosflux Talk 13:28, 23 May 2024 (UTC)[reply]
Specifically I'm not liking that the parser is building the ID from the content and including "," in the element id now. (That is the one thing that will affect all skins). — xaosflux Talk 13:31, 23 May 2024 (UTC)[reply]
Xaosflux Fixing this in Monobook.css was not appropriate (fixing it in WP:Main Page/styles.css is sufficient), nor was I believe moving the comma necessary. The relevant change is phab:T363597. It will be coming to the other skins Soon so we will need to fix it for all skins. Please remove the Monobook.css styles and revert your main page change so we can fix this correctly. Monobook being broken for a day or two is not a reason to... hack. Izno (talk) 16:44, 23 May 2024 (UTC)[reply]
@Izno looks like phab:T363597 is going to be 2 weeks out? Do you have a fix for /styles.css ready to go, in which case certainly we can pull this out of monobook.css. Also, do you know what the "breaking" change # is for reference? — xaosflux Talk 17:23, 23 May 2024 (UTC)[reply]
I do not have such a change. I'm not going to work on it until you revert yourself. It's a pain to sort things out when you're starting from the wrong state. Izno (talk) 17:29, 23 May 2024 (UTC)[reply]
And no, it is definitely live in Monobook. Izno (talk) 17:30, 23 May 2024 (UTC)[reply]
@Izno OK, I've restored the broken version - we certainly shouldn't leave this broken for weeks though. — xaosflux Talk 17:32, 23 May 2024 (UTC)[reply]
I will take care of it today. :) Izno (talk) 17:34, 23 May 2024 (UTC)[reply]
Thanks! Semantically, not sure about that comma - it is floating between the header and the end of a div that encompasses the header - certainly not a big deal other than the header handling breaking it there. — xaosflux Talk 17:37, 23 May 2024 (UTC)[reply]
This is fixed. Padding/margin between the top of the box and the welcome line looks off so that needs some investigation. I'll take a look later to see if that's just my imagination.
The comma is outside for the same reason you felt gross about it being on the inside earlier, except it matters for screen readers. IDK how the comma inside would even sound but it would probably be awkward. Izno (talk) 17:40, 23 May 2024 (UTC)[reply]
I got here from T363597 – looks like this was resolved in this edit: [1]. Thanks for fixing it. Matma Rex talk 18:54, 24 May 2024 (UTC)[reply]
Archives: Sections of this page older than three days are automatically relocated to the newest archive.

001 002 003 004 005 006 007 008 009 010 011 012 013 014 015 016 017 018 019 020 021 022 023 024 025 026 027 028 029 030 031 032 033 034 035 036 037 038 039 040 041 042 043 044 045 046 047 048 049 050 051 052 053 054 055 056 057 058 059 060 061 062 063 064 065 066 067 068 069 070 071 072 073 074 075 076 077 078 079 080 081 082 083 084 085 086 087 088 089 090 091 092 093 094 095 096 097 098 099 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207

Main Page error reports

[edit]

To report an error in content currently or imminently on the Main Page, use the appropriate section below.

  • Where is the error? An exact quotation of the text in question helps.
  • Offer a correction if possible.
  • References are helpful, especially when reporting an obscure factual or grammatical error.
  • Time zones. The Main Page runs on Coordinated Universal Time (UTC, currently 01:34 on 13 June 2024) and is not adjusted to your local time zone.
  • Can you resolve the problem yourself? If the error lies primarily in the content of an article linked from the Main Page, fix the problem there before reporting it here. Text on the Main Page generally defers to the articles with bolded links. Upcoming content on the Main Page is usually only protected from editing beginning 24 hours before its scheduled appearance. Before that period, you can be bold and fix any issues yourself.
  • Do not use {{edit fully-protected}} on this page, which will not get a faster response. It is unnecessary, because this page is not protected, and causes display problems. (See the bottom of this revision for an example.)
  • No chit-chat. Lengthy discussions should be moved to a suitable location elsewhere, such as the talk page of the relevant article or project.
  • Respect other editors. Another user wrote the text you want changed, or reported an issue they see in something you wrote. Everyone's goal should be producing the best Main Page possible. The compressed time frame of the Main Page means sometimes action must be taken before there has been time for everyone to comment. Be civil to fellow users.
  • Reports are removed when resolved. Once an error has been addressed or determined not to be an error, or the item has been rotated off the Main Page, the report will be removed from this page. Check the revision history for a record of any discussion or action taken; no archives are kept.

Errors in the summary of the featured article

[edit]
Please do not remove this invisible timestamp. See WT:ERRORS and WP:SUBSCRIBE. - Dank (push to talk) 01:24, 29 September 2022 (UTC)[reply]
  • Caption — Not a factual error, but Wreckage from the Battle of Villers-Bocage seems unduly vague. Suggest change to "Wreckage of a British Cromwell tank at the Battle of Villers-Bocage." – Sca (talk) 00:34, 13 June 2024 (UTC)[reply]
Will expanding the caption increase the portion of the main page taken up by the TFA?--Wehwalt (talk) 00:41, 13 June 2024 (UTC)[reply]
@Wehwalt, I suggest that this is a useful addition. I've just read the item and had the exact same uncertainty; is it the tank that we are talking about? If there's an imbalance of the main page as a result, that is easily fixed by adding or deleting something at OTD. In fact, I've just done so. It happens routinely. Balance concerns should never stop us from removing ambiguity. Schwede66 00:47, 13 June 2024 (UTC)[reply]
Looks like it'll fit. Photo file says yes it's a Cromwell. I suppose "the Battle of" could be dropped from the caption for space, since the text begins with "The Battle of Villers-Bocage." – Sca (talk) 00:47, 13 June 2024 (UTC)[reply]

Errors with "In the news"

[edit]
  • StarlinerThe Boeing Starliner spacecraft conducts its first crewed flight.... – Not a factual error, but "conducts" seems too anthropomorphic. Suggest change to "completes." – Sca (talk) 01:04, 13 cJune 2024 (UTC)

Errors in "Did you know ..."

[edit]

among the 10 most challenged books in the United States in 2023 there should be some hyperlink (or something) explaining what a challenged book is. ꧁Zanahary꧂ 01:28, 13 June 2024 (UTC)[reply]

Errors in "On this day"

[edit]
  • 13 June 1881 - at "came to an end when the USS Jeannette" pls italicise Jeannette JennyOz (talk) 07:51, 12 June 2024 (UTC)[reply]
     DoneSchwede66 00:38, 13 June 2024 (UTC)[reply]
  • 1996 – After an 81-day standoff ... group Montana Freemen surrendered to the FBI. - Article (correctly) gives date as June 14 and Ref 9 NYT dated 14 June has "The last 16 members of the Freemen anti-Government group handed themselves over to Federal agents tonight, ... After 81 days of resistance, the members of the right-wing group simply climbed into Government vans..."
This item last appeared on OTD on 13 June 2012 at which time it didn't actually have a date. June 14 was added here on 21 June 2012. JennyOz (talk) 07:51, 12 June 2024 (UTC)[reply]
I've moved this to the "eligible" section of the 14 June set. Schwede66 00:38, 13 June 2024 (UTC)[reply]
[edit]
(June 14, tomorrow)
(June 17)
[edit]

General discussion

[edit]

header broken in monobook

[edit]
Resolved
 – Primary issue resolved, minor tweaks may be possible still. — xaosflux Talk 19:40, 24 May 2024 (UTC)[reply]
2024-05-23 problems

Haven't been able to check this yet, possible WP:THURSDAY issue? In monobook, the page layout is broken now, see example - with the "welcome to wikipedia" being moved, a "," on a line by itself, bad font/size as well. — xaosflux Talk 09:34, 23 May 2024 (UTC)[reply]

@Izno: just in case you are working on this via Wikipedia:Main Page/styles.css. — xaosflux Talk 09:35, 23 May 2024 (UTC)[reply]
Fixed the comma break by moving the comma in to the h1 element; not seeing that causing breaks on vector or vector22. The h1 styling here seem to be the primary problem now. — xaosflux Talk 09:44, 23 May 2024 (UTC)[reply]
Seems to be styles associated with the mw-heading1 div around that h1.. — xaosflux Talk 10:11, 23 May 2024 (UTC)[reply]
I'm seeing the same issue - it looks very ugly. Thanks for looking into this! Modest Genius talk 11:15, 23 May 2024 (UTC)[reply]
The gap between Welcome to Wikipedia and "the free encyclopedia that anyone can edit." is too big on Monobook. The line at the top cuts off the bottom of the P. I suggest you do "Welcome to" in smaller letters at the top and then just Wikipedia in large. "Welcome" looks a bit silly being that big.♦ Dr. Blofeld 11:23, 23 May 2024 (UTC)[reply]
  • Getting these reset may be enough:
body.page-Main_Page #mw-heading1
border-bottom: none;
margin-bottom: none;
font-size: 100%;
xaosflux Talk 12:02, 23 May 2024 (UTC)[reply]
 Doing... font size fix first, waiting for sync. — xaosflux Talk 12:30, 23 May 2024 (UTC)[reply]
 Done font size fixed in MediaWiki:Monobook.css; margin/border to do. — xaosflux Talk 12:36, 23 May 2024 (UTC)[reply]
 Doing... border/margin - waiting for sync. — xaosflux Talk 13:24, 23 May 2024 (UTC)[reply]
 Done I'm not sure I love these CSS hacks though. Suggestions for improvement (here or upstream) are more than welcome. — xaosflux Talk 13:28, 23 May 2024 (UTC)[reply]
Specifically I'm not liking that the parser is building the ID from the content and including "," in the element id now. (That is the one thing that will affect all skins). — xaosflux Talk 13:31, 23 May 2024 (UTC)[reply]
Xaosflux Fixing this in Monobook.css was not appropriate (fixing it in WP:Main Page/styles.css is sufficient), nor was I believe moving the comma necessary. The relevant change is phab:T363597. It will be coming to the other skins Soon so we will need to fix it for all skins. Please remove the Monobook.css styles and revert your main page change so we can fix this correctly. Monobook being broken for a day or two is not a reason to... hack. Izno (talk) 16:44, 23 May 2024 (UTC)[reply]
@Izno looks like phab:T363597 is going to be 2 weeks out? Do you have a fix for /styles.css ready to go, in which case certainly we can pull this out of monobook.css. Also, do you know what the "breaking" change # is for reference? — xaosflux Talk 17:23, 23 May 2024 (UTC)[reply]
I do not have such a change. I'm not going to work on it until you revert yourself. It's a pain to sort things out when you're starting from the wrong state. Izno (talk) 17:29, 23 May 2024 (UTC)[reply]
And no, it is definitely live in Monobook. Izno (talk) 17:30, 23 May 2024 (UTC)[reply]
@Izno OK, I've restored the broken version - we certainly shouldn't leave this broken for weeks though. — xaosflux Talk 17:32, 23 May 2024 (UTC)[reply]
I will take care of it today. :) Izno (talk) 17:34, 23 May 2024 (UTC)[reply]
Thanks! Semantically, not sure about that comma - it is floating between the header and the end of a div that encompasses the header - certainly not a big deal other than the header handling breaking it there. — xaosflux Talk 17:37, 23 May 2024 (UTC)[reply]
This is fixed. Padding/margin between the top of the box and the welcome line looks off so that needs some investigation. I'll take a look later to see if that's just my imagination.
The comma is outside for the same reason you felt gross about it being on the inside earlier, except it matters for screen readers. IDK how the comma inside would even sound but it would probably be awkward. Izno (talk) 17:40, 23 May 2024 (UTC)[reply]
I got here from T363597 – looks like this was resolved in this edit: [1]. Thanks for fixing it. Matma Rex talk 18:54, 24 May 2024 (UTC)[reply]
Archives: Sections of this page older than three days are automatically relocated to the newest archive.

001 002 003 004 005 006 007 008 009 010 011 012 013 014 015 016 017 018 019 020 021 022 023 024 025 026 027 028 029 030 031 032 033 034 035 036 037 038 039 040 041 042 043 044 045 046 047 048 049 050 051 052 053 054 055 056 057 058 059 060 061 062 063 064 065 066 067 068 069 070 071 072 073 074 075 076 077 078 079 080 081 082 083 084 085 086 087 088 089 090 091 092 093 094 095 096 097 098 099 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207

Main Page error reports

[edit]

To report an error in content currently or imminently on the Main Page, use the appropriate section below.

  • Where is the error? An exact quotation of the text in question helps.
  • Offer a correction if possible.
  • References are helpful, especially when reporting an obscure factual or grammatical error.
  • Time zones. The Main Page runs on Coordinated Universal Time (UTC, currently 01:34 on 13 June 2024) and is not adjusted to your local time zone.
  • Can you resolve the problem yourself? If the error lies primarily in the content of an article linked from the Main Page, fix the problem there before reporting it here. Text on the Main Page generally defers to the articles with bolded links. Upcoming content on the Main Page is usually only protected from editing beginning 24 hours before its scheduled appearance. Before that period, you can be bold and fix any issues yourself.
  • Do not use {{edit fully-protected}} on this page, which will not get a faster response. It is unnecessary, because this page is not protected, and causes display problems. (See the bottom of this revision for an example.)
  • No chit-chat. Lengthy discussions should be moved to a suitable location elsewhere, such as the talk page of the relevant article or project.
  • Respect other editors. Another user wrote the text you want changed, or reported an issue they see in something you wrote. Everyone's goal should be producing the best Main Page possible. The compressed time frame of the Main Page means sometimes action must be taken before there has been time for everyone to comment. Be civil to fellow users.
  • Reports are removed when resolved. Once an error has been addressed or determined not to be an error, or the item has been rotated off the Main Page, the report will be removed from this page. Check the revision history for a record of any discussion or action taken; no archives are kept.

Errors in the summary of the featured article

[edit]
Please do not remove this invisible timestamp. See WT:ERRORS and WP:SUBSCRIBE. - Dank (push to talk) 01:24, 29 September 2022 (UTC)[reply]
  • Caption — Not a factual error, but Wreckage from the Battle of Villers-Bocage seems unduly vague. Suggest change to "Wreckage of a British Cromwell tank at the Battle of Villers-Bocage." – Sca (talk) 00:34, 13 June 2024 (UTC)[reply]
Will expanding the caption increase the portion of the main page taken up by the TFA?--Wehwalt (talk) 00:41, 13 June 2024 (UTC)[reply]
@Wehwalt, I suggest that this is a useful addition. I've just read the item and had the exact same uncertainty; is it the tank that we are talking about? If there's an imbalance of the main page as a result, that is easily fixed by adding or deleting something at OTD. In fact, I've just done so. It happens routinely. Balance concerns should never stop us from removing ambiguity. Schwede66 00:47, 13 June 2024 (UTC)[reply]
Looks like it'll fit. Photo file says yes it's a Cromwell. I suppose "the Battle of" could be dropped from the caption for space, since the text begins with "The Battle of Villers-Bocage." – Sca (talk) 00:47, 13 June 2024 (UTC)[reply]

Errors with "In the news"

[edit]
  • StarlinerThe Boeing Starliner spacecraft conducts its first crewed flight.... – Not a factual error, but "conducts" seems too anthropomorphic. Suggest change to "completes." – Sca (talk) 01:04, 13 cJune 2024 (UTC)

Errors in "Did you know ..."

[edit]

among the 10 most challenged books in the United States in 2023 there should be some hyperlink (or something) explaining what a challenged book is. ꧁Zanahary꧂ 01:28, 13 June 2024 (UTC)[reply]

Errors in "On this day"

[edit]
  • 13 June 1881 - at "came to an end when the USS Jeannette" pls italicise Jeannette JennyOz (talk) 07:51, 12 June 2024 (UTC)[reply]
     DoneSchwede66 00:38, 13 June 2024 (UTC)[reply]
  • 1996 – After an 81-day standoff ... group Montana Freemen surrendered to the FBI. - Article (correctly) gives date as June 14 and Ref 9 NYT dated 14 June has "The last 16 members of the Freemen anti-Government group handed themselves over to Federal agents tonight, ... After 81 days of resistance, the members of the right-wing group simply climbed into Government vans..."
This item last appeared on OTD on 13 June 2012 at which time it didn't actually have a date. June 14 was added here on 21 June 2012. JennyOz (talk) 07:51, 12 June 2024 (UTC)[reply]
I've moved this to the "eligible" section of the 14 June set. Schwede66 00:38, 13 June 2024 (UTC)[reply]
[edit]
(June 14, tomorrow)
(June 17)
[edit]

General discussion

[edit]

header broken in monobook

[edit]
Resolved
 – Primary issue resolved, minor tweaks may be possible still. — xaosflux Talk 19:40, 24 May 2024 (UTC)[reply]
2024-05-23 problems

Haven't been able to check this yet, possible WP:THURSDAY issue? In monobook, the page layout is broken now, see example - with the "welcome to wikipedia" being moved, a "," on a line by itself, bad font/size as well. — xaosflux Talk 09:34, 23 May 2024 (UTC)[reply]

@Izno: just in case you are working on this via Wikipedia:Main Page/styles.css. — xaosflux Talk 09:35, 23 May 2024 (UTC)[reply]
Fixed the comma break by moving the comma in to the h1 element; not seeing that causing breaks on vector or vector22. The h1 styling here seem to be the primary problem now. — xaosflux Talk 09:44, 23 May 2024 (UTC)[reply]
Seems to be styles associated with the mw-heading1 div around that h1.. — xaosflux Talk 10:11, 23 May 2024 (UTC)[reply]
I'm seeing the same issue - it looks very ugly. Thanks for looking into this! Modest Genius talk 11:15, 23 May 2024 (UTC)[reply]
The gap between Welcome to Wikipedia and "the free encyclopedia that anyone can edit." is too big on Monobook. The line at the top cuts off the bottom of the P. I suggest you do "Welcome to" in smaller letters at the top and then just Wikipedia in large. "Welcome" looks a bit silly being that big.♦ Dr. Blofeld 11:23, 23 May 2024 (UTC)[reply]
  • Getting these reset may be enough:
body.page-Main_Page #mw-heading1
border-bottom: none;
margin-bottom: none;
font-size: 100%;
xaosflux Talk 12:02, 23 May 2024 (UTC)[reply]
 Doing... font size fix first, waiting for sync. — xaosflux Talk 12:30, 23 May 2024 (UTC)[reply]
 Done font size fixed in MediaWiki:Monobook.css; margin/border to do. — xaosflux Talk 12:36, 23 May 2024 (UTC)[reply]
 Doing... border/margin - waiting for sync. — xaosflux Talk 13:24, 23 May 2024 (UTC)[reply]
 Done I'm not sure I love these CSS hacks though. Suggestions for improvement (here or upstream) are more than welcome. — xaosflux Talk 13:28, 23 May 2024 (UTC)[reply]
Specifically I'm not liking that the parser is building the ID from the content and including "," in the element id now. (That is the one thing that will affect all skins). — xaosflux Talk 13:31, 23 May 2024 (UTC)[reply]
Xaosflux Fixing this in Monobook.css was not appropriate (fixing it in WP:Main Page/styles.css is sufficient), nor was I believe moving the comma necessary. The relevant change is phab:T363597. It will be coming to the other skins Soon so we will need to fix it for all skins. Please remove the Monobook.css styles and revert your main page change so we can fix this correctly. Monobook being broken for a day or two is not a reason to... hack. Izno (talk) 16:44, 23 May 2024 (UTC)[reply]
@Izno looks like phab:T363597 is going to be 2 weeks out? Do you have a fix for /styles.css ready to go, in which case certainly we can pull this out of monobook.css. Also, do you know what the "breaking" change # is for reference? — xaosflux Talk 17:23, 23 May 2024 (UTC)[reply]
I do not have such a change. I'm not going to work on it until you revert yourself. It's a pain to sort things out when you're starting from the wrong state. Izno (talk) 17:29, 23 May 2024 (UTC)[reply]
And no, it is definitely live in Monobook. Izno (talk) 17:30, 23 May 2024 (UTC)[reply]
@Izno OK, I've restored the broken version - we certainly shouldn't leave this broken for weeks though. — xaosflux Talk 17:32, 23 May 2024 (UTC)[reply]
I will take care of it today. :) Izno (talk) 17:34, 23 May 2024 (UTC)[reply]
Thanks! Semantically, not sure about that comma - it is floating between the header and the end of a div that encompasses the header - certainly not a big deal other than the header handling breaking it there. — xaosflux Talk 17:37, 23 May 2024 (UTC)[reply]
This is fixed. Padding/margin between the top of the box and the welcome line looks off so that needs some investigation. I'll take a look later to see if that's just my imagination.
The comma is outside for the same reason you felt gross about it being on the inside earlier, except it matters for screen readers. IDK how the comma inside would even sound but it would probably be awkward. Izno (talk) 17:40, 23 May 2024 (UTC)[reply]
I got here from T363597 – looks like this was resolved in this edit: [1]. Thanks for fixing it. Matma Rex talk 18:54, 24 May 2024 (UTC)[reply]
Cancel Editing help (opens in new window)