Here are the release notes for Fandom's code release scheduled for February 25, 2019:
- FIXED: We will fix an issue that could cause Blog:Recent posts to stop listing the newest posts on particularly busy wikis.
- NOTABLE: We will be updating the Ace editor to version 1.4.2. This is the code editor used on CSS, JS, Infobox and Lua pages. This update should allow proper functionality across more devices.
Additionally, a number of features have been added to Portable Infoboxes:
- <infobox type="foo"> will add an HTML class of
type-foo
to the infobox output. This is intended so that what an infobox is describing can be more logically identified, rather than using themes designed for how it looks. So, for example, all infoboxes describing a Pokémon (with the CSS selector.type-pokemon
) can share a layout from CSS, regardless of whether they are.pi-theme-fire
,.pi-theme-water
, etc. - All Portable Infobox elements that have an input of source will now render in HTML with that parameter name in a data-attribute, such as data-source="ATK". This will allow you to write CSS or jQuery selectors such as
.pi-item[data-source="ATK"]
to style and identify individual items. Used in combination with type, this should eliminate the need for nth-of-type style selection and opens up other possibilities for design and interactivity. - The new name parameter allows explicit selection of elements whether they accept a source input or not, including identification of <title>, <group>, <data>, <header>, <image>, and <navigation>. Much like the data-source data-attribute, <data name="bar"> can be selected as
.pi-item[data-item-name="bar"]
. - Data items and groups can now be structured in tabbed panels, which allow more flexibility and smarter data display on desktop and mobile views. Each <panel> — as a child of the root <infobox> element — can be labeled (with <label>) and one or more <section> elements to make a tab set. Any element that could otherwise be a child of <infobox> can be a child of <section>. This should reduce clutter and the necessity for groups of infoboxes on pages, while structuring infoboxes in more dynamic ways. An example can be found on Forgotten Realms Wiki.