Module talk:Clade - Revision history

Anomalocaris:

2024-05-01T21:23:20Z

<code? → <code>

← Previous revision		Revision as of 21:23, 1 May 2024
Line 198:		Line 198:
	: Another reason the appearance in mobile is poor is that it changes the line-heights and font sizes and seems to overide those set by the template. — <span style="font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> [[User:Jts1882\|Jts1882]] \|[[User talk:Jts1882\| talk]] </span> 17:47, 28 February 2024 (UTC)		: Another reason the appearance in mobile is poor is that it changes the line-heights and font sizes and seems to overide those set by the template. — <span style="font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> [[User:Jts1882\|Jts1882]] \|[[User talk:Jts1882\| talk]] </span> 17:47, 28 February 2024 (UTC)
	::I've added an outer div to all clade elements with a class for CSS styling. I use module code to delete the classes in the nested clade so the CSS only applies to the outer one clade element. I'm only applying the overflow to the Vector-2022 skin, as the overflow causes other problems. It causes the overflow when next to a floated right image or infobox and squeezes the cladogram in, whereas the default behaviour is to move the whole cladogram down and use the screen width. What is needed is an overflow that only happens when at the right edge of the screen and not when next to an infobox or image. I don't know if this is possible with CSS.		::I've added an outer div to all clade elements with a class for CSS styling. I use module code to delete the classes in the nested clade so the CSS only applies to the outer one clade element. I'm only applying the overflow to the Vector-2022 skin, as the overflow causes other problems. It causes the overflow when next to a floated right image or infobox and squeezes the cladogram in, whereas the default behaviour is to move the whole cladogram down and use the screen width. What is needed is an overflow that only happens when at the right edge of the screen and not when next to an infobox or image. I don't know if this is possible with CSS.
	::As for mobile that has a lot more issues. It sets a larger font size rather than use inherit, which meant thaat the labels (nodes in cladogram) and terminals had different font-sizes. This I think I have fixed. The mobile view also uses <code>!important</code> to block floating of tables (e.g. the responsive behaviour of {{tl\|clade gallery}}), so the panels appear vertically instead of horizontally. This can be fixed by using floating div elements or using <code?!important</code> (which I'd rather not) but there are some other mobile changes that make this more complicated (line spacing that affects the panel heights and some things I've yet to work out). — <span style="font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> [[User:Jts1882\|Jts1882]] \|[[User talk:Jts1882\| talk]] </span> 08:53, 29 March 2024 (UTC)		::As for mobile that has a lot more issues. It sets a larger font size rather than use inherit, which meant thaat the labels (nodes in cladogram) and terminals had different font-sizes. This I think I have fixed. The mobile view also uses <code>!important</code> to block floating of tables (e.g. the responsive behaviour of {{tl\|clade gallery}}), so the panels appear vertically instead of horizontally. This can be fixed by using floating div elements or using <code>!important</code> (which I'd rather not) but there are some other mobile changes that make this more complicated (line spacing that affects the panel heights and some things I've yet to work out). — <span style="font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> [[User:Jts1882\|Jts1882]] \|[[User talk:Jts1882\| talk]] </span> 08:53, 29 March 2024 (UTC)
	:::This change appears to have caused a few syntax errors in rare places where the newly modified elements were wrapped with span tags, since span tags generally can't wrap div tags. I have found and fixed all of the pages that turned up on Linter error reports, but a few more may trickle in. Generally, the fix is to replace the span-based wrapping elements with div-based elements. – [[User:Jonesey95\|Jonesey95]] ([[User talk:Jonesey95\|talk]]) 04:24, 2 April 2024 (UTC)		:::This change appears to have caused a few syntax errors in rare places where the newly modified elements were wrapped with span tags, since span tags generally can't wrap div tags. I have found and fixed all of the pages that turned up on Linter error reports, but a few more may trickle in. Generally, the fix is to replace the span-based wrapping elements with div-based elements. – [[User:Jonesey95\|Jonesey95]] ([[User talk:Jonesey95\|talk]]) 04:24, 2 April 2024 (UTC)

Jonesey95: /* Non-responsiveness leads to overlap on width less than 1280x */ wrapping

2024-04-02T04:24:38Z

Non-responsiveness leads to overlap on width less than 1280x: wrapping

← Previous revision		Revision as of 04:24, 2 April 2024
Line 199:		Line 199:
	::I've added an outer div to all clade elements with a class for CSS styling. I use module code to delete the classes in the nested clade so the CSS only applies to the outer one clade element. I'm only applying the overflow to the Vector-2022 skin, as the overflow causes other problems. It causes the overflow when next to a floated right image or infobox and squeezes the cladogram in, whereas the default behaviour is to move the whole cladogram down and use the screen width. What is needed is an overflow that only happens when at the right edge of the screen and not when next to an infobox or image. I don't know if this is possible with CSS.		::I've added an outer div to all clade elements with a class for CSS styling. I use module code to delete the classes in the nested clade so the CSS only applies to the outer one clade element. I'm only applying the overflow to the Vector-2022 skin, as the overflow causes other problems. It causes the overflow when next to a floated right image or infobox and squeezes the cladogram in, whereas the default behaviour is to move the whole cladogram down and use the screen width. What is needed is an overflow that only happens when at the right edge of the screen and not when next to an infobox or image. I don't know if this is possible with CSS.
	::As for mobile that has a lot more issues. It sets a larger font size rather than use inherit, which meant thaat the labels (nodes in cladogram) and terminals had different font-sizes. This I think I have fixed. The mobile view also uses <code>!important</code> to block floating of tables (e.g. the responsive behaviour of {{tl\|clade gallery}}), so the panels appear vertically instead of horizontally. This can be fixed by using floating div elements or using <code?!important</code> (which I'd rather not) but there are some other mobile changes that make this more complicated (line spacing that affects the panel heights and some things I've yet to work out). — <span style="font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> [[User:Jts1882\|Jts1882]] \|[[User talk:Jts1882\| talk]] </span> 08:53, 29 March 2024 (UTC)		::As for mobile that has a lot more issues. It sets a larger font size rather than use inherit, which meant thaat the labels (nodes in cladogram) and terminals had different font-sizes. This I think I have fixed. The mobile view also uses <code>!important</code> to block floating of tables (e.g. the responsive behaviour of {{tl\|clade gallery}}), so the panels appear vertically instead of horizontally. This can be fixed by using floating div elements or using <code?!important</code> (which I'd rather not) but there are some other mobile changes that make this more complicated (line spacing that affects the panel heights and some things I've yet to work out). — <span style="font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> [[User:Jts1882\|Jts1882]] \|[[User talk:Jts1882\| talk]] </span> 08:53, 29 March 2024 (UTC)
			:::This change appears to have caused a few syntax errors in rare places where the newly modified elements were wrapped with span tags, since span tags generally can't wrap div tags. I have found and fixed all of the pages that turned up on Linter error reports, but a few more may trickle in. Generally, the fix is to replace the span-based wrapping elements with div-based elements. – [[User:Jonesey95\|Jonesey95]] ([[User talk:Jonesey95\|talk]]) 04:24, 2 April 2024 (UTC)

Jts1882: /* Non-responsiveness leads to overlap on width less than 1280x */ edit response

2024-03-29T08:57:38Z

Non-responsiveness leads to overlap on width less than 1280x: edit response

← Previous revision		Revision as of 08:57, 29 March 2024
Line 197:		Line 197:
	: Oops, I missed this response. That is much simpler than what I was trying to describe (and failing to). In fact the templatestyles for the clade template does something similar for the table width (auto for the outer table, and 100% for nested tables).		: Oops, I missed this response. That is much simpler than what I was trying to describe (and failing to). In fact the templatestyles for the clade template does something similar for the table width (auto for the outer table, and 100% for nested tables).
	: Another reason the appearance in mobile is poor is that it changes the line-heights and font sizes and seems to overide those set by the template. — <span style="font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> [[User:Jts1882\|Jts1882]] \|[[User talk:Jts1882\| talk]] </span> 17:47, 28 February 2024 (UTC)		: Another reason the appearance in mobile is poor is that it changes the line-heights and font sizes and seems to overide those set by the template. — <span style="font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> [[User:Jts1882\|Jts1882]] \|[[User talk:Jts1882\| talk]] </span> 17:47, 28 February 2024 (UTC)
	::I've added an outer div to all clade elements with a class for CSS styling. I delete the classes in the nested clade ~~elements~~ in the ~~module~~. I'm only applying the overflow to the Vector-2022 skin, as the overflow causes other problems. It causes the overflow when next to an floated right image or infobox and squeezes the cladogram in, whereas the default behaviour is to move the whole cladogram ~~table~~ down and use the screen width. What is needed is an overflow that only happens when at the right edge of the screen and not when next to an infobox or image. I don't know if this is possible with CSS.		::I've added an outer div to all clade elements with a class for CSS styling. I use module code to delete the classes in the nested clade so the CSS only applies to the outer one clade element. I'm only applying the overflow to the Vector-2022 skin, as the overflow causes other problems. It causes the overflow when next to a floated right image or infobox and squeezes the cladogram in, whereas the default behaviour is to move the whole cladogram down and use the screen width. What is needed is an overflow that only happens when at the right edge of the screen and not when next to an infobox or image. I don't know if this is possible with CSS.
	::As for mobile that has a lot more issues. It sets a larger font size rather than use inherit, which meant thaat the labels (nodes in cladogram) and terminals had different font-sizes. This I think I have fixed. The mobile view also uses <code?!important</code> to block floating of tables (e.g. the responsive behaviour of {{tl\|clade gallery}}), so the panels appear vertically instead of horizontally. This can be fixed by floating div elements or using <code?!important</code> (which I'd rather not) but there are some other mobile changes that make this more complicated. — <span style="font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> [[User:Jts1882\|Jts1882]] \|[[User talk:Jts1882\| talk]] </span> 08:53, 29 March 2024 (UTC)		::As for mobile that has a lot more issues. It sets a larger font size rather than use inherit, which meant thaat the labels (nodes in cladogram) and terminals had different font-sizes. This I think I have fixed. The mobile view also uses <code>!important</code> to block floating of tables (e.g. the responsive behaviour of {{tl\|clade gallery}}), so the panels appear vertically instead of horizontally. This can be fixed by using floating div elements or using <code?!important</code> (which I'd rather not) but there are some other mobile changes that make this more complicated (line spacing that affects the panel heights and some things I've yet to work out). — <span style="font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> [[User:Jts1882\|Jts1882]] \|[[User talk:Jts1882\| talk]] </span> 08:53, 29 March 2024 (UTC)

Jts1882: /* Non-responsiveness leads to overlap on width less than 1280x */ overflow applied to vector-2022

2024-03-29T08:53:14Z

Non-responsiveness leads to overlap on width less than 1280x: overflow applied to vector-2022

← Previous revision		Revision as of 08:53, 29 March 2024
Line 197:		Line 197:
	: Oops, I missed this response. That is much simpler than what I was trying to describe (and failing to). In fact the templatestyles for the clade template does something similar for the table width (auto for the outer table, and 100% for nested tables).		: Oops, I missed this response. That is much simpler than what I was trying to describe (and failing to). In fact the templatestyles for the clade template does something similar for the table width (auto for the outer table, and 100% for nested tables).
	: Another reason the appearance in mobile is poor is that it changes the line-heights and font sizes and seems to overide those set by the template. — <span style="font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> [[User:Jts1882\|Jts1882]] \|[[User talk:Jts1882\| talk]] </span> 17:47, 28 February 2024 (UTC)		: Another reason the appearance in mobile is poor is that it changes the line-heights and font sizes and seems to overide those set by the template. — <span style="font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> [[User:Jts1882\|Jts1882]] \|[[User talk:Jts1882\| talk]] </span> 17:47, 28 February 2024 (UTC)
			::I've added an outer div to all clade elements with a class for CSS styling. I delete the classes in the nested clade elements in the module. I'm only applying the overflow to the Vector-2022 skin, as the overflow causes other problems. It causes the overflow when next to an floated right image or infobox and squeezes the cladogram in, whereas the default behaviour is to move the whole cladogram table down and use the screen width. What is needed is an overflow that only happens when at the right edge of the screen and not when next to an infobox or image. I don't know if this is possible with CSS.
			::As for mobile that has a lot more issues. It sets a larger font size rather than use inherit, which meant thaat the labels (nodes in cladogram) and terminals had different font-sizes. This I think I have fixed. The mobile view also uses <code?!important</code> to block floating of tables (e.g. the responsive behaviour of {{tl\|clade gallery}}), so the panels appear vertically instead of horizontally. This can be fixed by floating div elements or using <code?!important</code> (which I'd rather not) but there are some other mobile changes that make this more complicated. — <span style="font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> [[User:Jts1882\|Jts1882]] \|[[User talk:Jts1882\| talk]] </span> 08:53, 29 March 2024 (UTC)

Jts1882: /* Non-responsiveness leads to overlap on width less than 1280x */ belated reply

2024-02-28T17:47:42Z

Non-responsiveness leads to overlap on width less than 1280x: belated reply

← Previous revision		Revision as of 17:47, 28 February 2024
Line 195:		Line 195:
	</syntaxhighlight>		</syntaxhighlight>
	? This would incidentally "fix" the fact it can overflow out of the page even on Vector and other "scroll-right infinitely" skins. [[User:Izno\|Izno]] ([[User talk:Izno\|talk]]) 18:47, 23 February 2024 (UTC)		? This would incidentally "fix" the fact it can overflow out of the page even on Vector and other "scroll-right infinitely" skins. [[User:Izno\|Izno]] ([[User talk:Izno\|talk]]) 18:47, 23 February 2024 (UTC)
			: Oops, I missed this response. That is much simpler than what I was trying to describe (and failing to). In fact the templatestyles for the clade template does something similar for the table width (auto for the outer table, and 100% for nested tables).
			: Another reason the appearance in mobile is poor is that it changes the line-heights and font sizes and seems to overide those set by the template. — <span style="font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> [[User:Jts1882\|Jts1882]] \|[[User talk:Jts1882\| talk]] </span> 17:47, 28 February 2024 (UTC)

Izno: /* Non-responsiveness leads to overlap on width less than 1280x */ adj

2024-02-23T18:48:44Z

Non-responsiveness leads to overlap on width less than 1280x: adj

← Previous revision		Revision as of 18:48, 23 February 2024
Line 194:		Line 194:
	.clade-container .clade-container { overflow-x: initial }		.clade-container .clade-container { overflow-x: initial }
	</syntaxhighlight>		</syntaxhighlight>
	? [[User:Izno\|Izno]] ([[User talk:Izno\|talk]]) 18:47, 23 February 2024 (UTC)		? This would incidentally "fix" the fact it can overflow out of the page even on Vector and other "scroll-right infinitely" skins. [[User:Izno\|Izno]] ([[User talk:Izno\|talk]]) 18:47, 23 February 2024 (UTC)

Izno: /* Non-responsiveness leads to overlap on width less than 1280x */ ?

2024-02-23T18:47:53Z

Non-responsiveness leads to overlap on width less than 1280x: ?

← Previous revision		Revision as of 18:47, 23 February 2024
Line 188:		Line 188:
	:::: One ugly method that should work is to add a div element with appropriate CSS to all uses of the template and then delete the styling from all nested templates. This would leave an unstyled div on nested elements and only apply the scrolling to the outer table. It might be possible to remove the divs totally, but the "regex" for that will be difficult because people add all sorts of HTML elements to the labels and terminals. From experience, there's always something unaccounted for.		:::: One ugly method that should work is to add a div element with appropriate CSS to all uses of the template and then delete the styling from all nested templates. This would leave an unstyled div on nested elements and only apply the scrolling to the outer table. It might be possible to remove the divs totally, but the "regex" for that will be difficult because people add all sorts of HTML elements to the labels and terminals. From experience, there's always something unaccounted for.
	:::: The CSS styling would be moved to templatestyles, so a <code>class clade-overflow</code> could be restricted to Vector 22 and narrow screens with the appropriate css. — <span style="font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> [[User:Jts1882\|Jts1882]] \|[[User talk:Jts1882\| talk]] </span> 09:40, 23 February 2024 (UTC)		:::: The CSS styling would be moved to templatestyles, so a <code>class clade-overflow</code> could be restricted to Vector 22 and narrow screens with the appropriate css. — <span style="font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> [[User:Jts1882\|Jts1882]] \|[[User talk:Jts1882\| talk]] </span> 09:40, 23 February 2024 (UTC)
			{{tq\|appropriate CSS to all uses of the template and then delete the styling from all nested templates}} We have a few templates that do this (fmbox and navbox both do it off the cuff). I think it would just be:

			<syntaxhighlight lang=css>
			.clade-container { overflow-x: scroll }
			.clade-container .clade-container { overflow-x: initial }
			</syntaxhighlight>
			? [[User:Izno\|Izno]] ([[User talk:Izno\|talk]]) 18:47, 23 February 2024 (UTC)

Jts1882: /* Long cladograms cause layout issues on mobile devices when switching to the landscape mode */ fix link to old version for test

2024-02-23T15:09:42Z

Long cladograms cause layout issues on mobile devices when switching to the landscape mode: fix link to old version for test

← Previous revision		Revision as of 15:09, 23 February 2024
Line 165:		Line 165:
	: I can make a general comment. These cladograms are just nested HTML tables and the appearance depends on how the browser renders the table. There has been a long-standing issue with different presentation using Safari. Chrome used to render as Safari, but now renders same as Firefox. (see [[Template_talk:Clade#Browser_differences_-_Chrome_vs._Firefox]].		: I can make a general comment. These cladograms are just nested HTML tables and the appearance depends on how the browser renders the table. There has been a long-standing issue with different presentation using Safari. Chrome used to render as Safari, but now renders same as Firefox. (see [[Template_talk:Clade#Browser_differences_-_Chrome_vs._Firefox]].
	: It might be possible to do something with the CSS in templatestyles, but there is nothing I can do without an example of the problem to test on. — <span style="font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> [[User:Jts1882\|Jts1882]] \|[[User talk:Jts1882\| talk]] </span> 16:15, 15 August 2022 (UTC)		: It might be possible to do something with the CSS in templatestyles, but there is nothing I can do without an example of the problem to test on. — <span style="font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> [[User:Jts1882\|Jts1882]] \|[[User talk:Jts1882\| talk]] </span> 16:15, 15 August 2022 (UTC)
	:: I think I now can see issue under discussion. However, I don't think it has anything to do with the clade module. It is a general problem with the handling of elements such as tables or images that overflow the content width. Take a look at https://en.m.wikipedia.org/~~wiki~~/User:Jts1882/blank, a table with a long word that doesn't break.		:: I think I now can see issue under discussion. However, I don't think it has anything to do with the clade module. It is a general problem with the handling of elements such as tables or images that overflow the content width. Take a look at [https://en.m.wikipedia.org/w/index.php?title=User:Jts1882/blank&oldid=1104720978 User:Jts1882/blank], a table with a long word that doesn't break.
	:: With the window not maximized, gradually reduce the width. At some point the table overflows the paragraph width (at about 770px). The horizontal scroll bar appears at the bottom of the whole window and creates scrolling showing white space to the right of the paragraph. This is I believe a demonstration of the issue under discussion.		:: With the window not maximized, gradually reduce the width. At some point the table overflows the paragraph width (at about 770px). The horizontal scroll bar appears at the bottom of the whole window and creates scrolling showing white space to the right of the paragraph. This is I believe a demonstration of the issue under discussion.
	:: Now further reduce the width of the window. At a paragraph with of about 595px, the scroll bar switches to from the whole window to the table element. Would the correct behaviour would be to see the scroll bar on the table as soon as it overflowed?		:: Now further reduce the width of the window. At a paragraph with of about 595px, the scroll bar switches to from the whole window to the table element. Would the correct behaviour would be to see the scroll bar on the table as soon as it overflowed?
	— <span style="font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> [[User:Jts1882\|Jts1882]] \|[[User talk:Jts1882\| talk]] </span> 14:54, 16 August 2022 (UTC)		::— <span style="font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> [[User:Jts1882\|Jts1882]] \|[[User talk:Jts1882\| talk]] </span> 14:54, 16 August 2022 (UTC)

	== Why concacenate strings? ==		== Why concacenate strings? ==

Jts1882: /* Non-responsiveness leads to overlap on width less than 1280x */ possible solution

2024-02-23T09:40:03Z

Non-responsiveness leads to overlap on width less than 1280x: possible solution

← Previous revision		Revision as of 09:40, 23 February 2024
Line 185:		Line 185:
	:::Your "other skin" is probably Vector 22 based on a known bug with transcluding special pages causing the default skin (which is V22) to display whether you like it or not.		:::Your "other skin" is probably Vector 22 based on a known bug with transcluding special pages causing the default skin (which is V22) to display whether you like it or not.
	:::{{tq\|The best place to put the overflow is in one of the container templates (e.g. {{tl\|clade gallery}} or {{tl\|clade box}} or {{tl\|cladogram}}) but these are not used in most uses of the template.}} I was afraid of that, based on what I could see of what was happening in the module. [[User:Izno\|Izno]] ([[User talk:Izno\|talk]]) 08:20, 23 February 2024 (UTC)		:::{{tq\|The best place to put the overflow is in one of the container templates (e.g. {{tl\|clade gallery}} or {{tl\|clade box}} or {{tl\|cladogram}}) but these are not used in most uses of the template.}} I was afraid of that, based on what I could see of what was happening in the module. [[User:Izno\|Izno]] ([[User talk:Izno\|talk]]) 08:20, 23 February 2024 (UTC)
			:::: I've added a parameter {{para\|overflow\|yes}} to wrap a div with <code>style="overflow:auto;"</code>. This works if added to the outer clade template (see [[Squamata]]. This alone doesn't help as it must be added to each cladogram. Adding it to every clade template is a mess as expected as scrollbars appear nested within the whole cladogram.
			:::: One ugly method that should work is to add a div element with appropriate CSS to all uses of the template and then delete the styling from all nested templates. This would leave an unstyled div on nested elements and only apply the scrolling to the outer table. It might be possible to remove the divs totally, but the "regex" for that will be difficult because people add all sorts of HTML elements to the labels and terminals. From experience, there's always something unaccounted for.
			:::: The CSS styling would be moved to templatestyles, so a <code>class clade-overflow</code> could be restricted to Vector 22 and narrow screens with the appropriate css. — <span style="font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> [[User:Jts1882\|Jts1882]] \|[[User talk:Jts1882\| talk]] </span> 09:40, 23 February 2024 (UTC)

Izno: /* Non-responsiveness leads to overlap on width less than 1280x */ Reply

2024-02-23T08:20:12Z

Non-responsiveness leads to overlap on width less than 1280x: Reply

← Previous revision		Revision as of 08:20, 23 February 2024
Line 182:		Line 182:
	:: Is Vector 2022 the default skin here on English Wikipedia? If so we need this fixed as well.		:: Is Vector 2022 the default skin here on English Wikipedia? If so we need this fixed as well.
	:: Incidentally, I'm getting some other skin forced on me at [[Module:Clade]], which narrows the code window, despite being logged on. This also occurs on some other modules, but not all. — <span style="font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> [[User:Jts1882\|Jts1882]] \|[[User talk:Jts1882\| talk]] </span> 07:26, 23 February 2024 (UTC)		:: Incidentally, I'm getting some other skin forced on me at [[Module:Clade]], which narrows the code window, despite being logged on. This also occurs on some other modules, but not all. — <span style="font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> [[User:Jts1882\|Jts1882]] \|[[User talk:Jts1882\| talk]] </span> 07:26, 23 February 2024 (UTC)
			:::Yes, Vector 22 is our current default, but of course as you've observed above this module probably also doesn't work too well on mobile today.
			:::Your "other skin" is probably Vector 22 based on a known bug with transcluding special pages causing the default skin (which is V22) to display whether you like it or not.
			:::{{tq\|The best place to put the overflow is in one of the container templates (e.g. {{tl\|clade gallery}} or {{tl\|clade box}} or {{tl\|cladogram}}) but these are not used in most uses of the template.}} I was afraid of that, based on what I could see of what was happening in the module. [[User:Izno\|Izno]] ([[User talk:Izno\|talk]]) 08:20, 23 February 2024 (UTC)