Content deleted Content added
SMcCandlish (talk | contribs) |
|||
Line 1,335:
Hey SMcCandlish, I'm fixing {{tl|Xtn}}'s appearance in dark mode, and I'm not sure I understand the hidden comment left there. Does {{tl|Xtn/sandbox}} work? [[User:Snowmanonahoe|Snowmanonahoe]] ([[User talk:Snowmanonahoe|talk]] '''·''' [[Special:Contributions/Snowmanonahoe|contribs]] '''·''' [[User:Snowmanonahoe/Typos|typos]]) 17:52, 7 July 2024 (UTC)
:{{ping|Snowmanonahoe}} Well, the HTML comment seems to indicate that without
::See [[mw:Reading/Web/Accessibility for reading/Updates/2024-04]] for more information on dark mode. It's not on Vector legacy. As for the hidden comment, the part I don't understand is what "consistent link-coloring behavior" means. [[User:Snowmanonahoe|Snowmanonahoe]] ([[User talk:Snowmanonahoe|talk]] '''·''' [[Special:Contributions/Snowmanonahoe|contribs]] '''·''' [[User:Snowmanonahoe/Typos|typos]]) 03:13, 8 July 2024 (UTC)
:::Not sure what's unclear about it. It means links will not be colored consistently. At this distant a remove, I'm not certain under what conditions that problem arose (i.e. whether it was consistently between templates in that group, or consistently from context to context using the same template). But it did arise, and thus the fix was implemented.<p>I would think the thing to do would be to have <code>color: initial</code> applied by default, and override it selectively for particular conditions in which whatever custom result you want to apply under those particular conditions has been well-tested.</p><p>I'm highly skeptical that a specific color such as <code>color: black</code> should ever be set, since it incorrectly presupposes that the conditions of the surrounding block will be known at all times and will be consistent from one context to another, which is not correct (though when it is wrong will probably not be very often). While we can be certain that general running text in an article is going to look a particular way, we have no way to predict what a particular templated condition is going to look like (various templates colorize blocks of text as to background, text color, or both). And these xt-type templates aren't for article text anyway, but generally for use in internal documentation.</p><p>When <code>initial</code> is assigned to a non-inherited propery, like <code>display</code>, it defaults to the CSS spec's default. When <code>initial</code> is assigned to an inherited property like <code>color</code>, it inherits the value most recently defined for that context in the stylesheet stack (if there is one, otherwise it gets the CSS-spec default or perhaps the browser default, if they different, and depending on the browser). There must have been a specific reason that both unset and <code>inherit</code> were not getting the job done properly in this case, but I wouldn't recall what the specifics were after so long. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''']] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] 😼 </span> 13:12, 8 July 2024 (UTC)</p>
== Help:Searching ==
| |||