Currently, there are open phabtickets proposing that the use of the HistMerge tool be logged at the target article in addition to the source article. Several proposals have been made:
Option 1a: When using Special:MergeHistory, a null edit should be placed in both the merge target and merge source's page's histories stating that a history merge took place.
(phab:T341760: Special:MergeHistory should place a null edit in the page's history describing the merge, authored Jul 13 2023)
Option 1b: When using Special:MergeHistory, add a log entry recorded for the articles at the both HistMerge target and source that records the existence of a history merge.
(phab:T118132: Merging pages should add a log entry to the destination page, authored Nov 8 2015)
Option 2: Do not log the use of the Special:MergeHistory tool at the merge target, maintaining the current status quo.
Should the use of the HistMerge tool be explicitly logged? If so, should the use be logged via an entry in the page history or should it instead be held in a dedicated log? — Red-tailed hawk(nest)15:51, 20 November 2024 (UTC)
There has been an initiative to change the interface so that the gray header at the top of the table "follows around" as you scroll down. See: {{sticky header}}. Which of the choices below (A-E) do you prefer? What other ideas do you have?
The header is now 2 lines tall. What Timeshifter is now proposing (scroll down this example) is a narrow one-line sticky header with a link from the "Status" column head back to the "Legend" section of the article. And a link from the "Sources" column head back to the "Sources" section of the article. Notes explain this just above the table. He states this allows new users of the table to quickly return to the table TOC, or to quickly find the meaning of the legend icons.
An issue in any skin other than the default Vector 2022: When you use the horizontal table TOC, or if you follow ("jump to") an anchored link within the table such as WP:FORBESCON, the top line of the note in the row you jump to would be covered by the narrow sticky header. 2 lines are covered by the 2-line header. Template discussions have not found a way to fix this. Timeshifter does not believe this is a serious problem. Others do. One solution (see E below) is to add a line's worth of blank padding at the top of each row.
A: No sticky header, same style (2-line) header as before.
Add the tag {{rfc|xxx}} at the top of a talk page section, where "xxx" is the category abbreviation. The different category abbreviations that should be used with {{rfc}} are listed above in parenthesis. Multiple categories are separated by a vertical pipe. For example, {{rfc|xxx|yyy}}, where "xxx" is the first category and "yyy" is the second category.
