Wikibooks:Reading room/Archives/2022/June

Relocating the table of contents
The table of contents for book chapters have been pulled out of the body recently :( and are turning up at the bottom of the navigation column where the are unseen and, IMHO, irrelevant. How can I return the table of contents back to the body of the chapter so that it is inline with the rest of the text?  Or, failing that, how can I move the table to the top of the navigation column above the site material? Larsnooden (discuss • contribs) 11:36, 30 April 2022 (UTC)


 * Please see WB:TOC, it should explain what you need to do. -- Jules (Mrjulesd) 11:48, 30 April 2022 (UTC)


 * I have seen that, thanks, but it does not address the problem I see. The link's text does not say more than, "With , it is placed at the same position where this code is placed".  I do have the magic word  in several chapters and that setting is still overridden and the TOC still ends up off to the bottom left in the navigation column and not where the magic word is placed. Larsnooden (discuss • contribs) 12:00, 30 April 2022 (UTC)


 * Can you provide some examples? One tip that might be helpful is the template Clear which clears floating elements such as TOCs from other elements, and might help with placements. -- Jules (Mrjulesd) 12:10, 30 April 2022 (UTC)


 * Sure. The chapter on  Proxies and Jump Hosts has the magic  word in place but the TOC is still shown down below the site navigation menu instead of inline.  Most of the other chapters, such the one on  Certificate-based Authentication, do not have  and have the same problem. --  Larsnooden (discuss • contribs) 12:18, 30 April 2022 (UTC)


 * Ah I think it might be a problem your end. On Certificate-based Authentication the TOC appears to me as coming after the first two paragraphs. On   Proxies and Jump Hosts it comes after the first sentence. Tested on Firefox and Chrome browsers on a Windows 7 system. -- Jules  (Mrjulesd) 12:54, 30 April 2022 (UTC)


 * No. The problem is definitely in the wikibook site.  I have not changed anything on my end recently nor have the  markers been moved.  Something broke there and needs to be repaired.  Thanks.  -- Larsnooden (discuss • contribs) 12:59, 30 April 2022 (UTC)


 * If that's the case, can you explain to me why I can't replicate the problem on my system? One thing you could try is to bypass your cache. -- Jules (Mrjulesd) 13:35, 30 April 2022 (UTC)


 * Dunno. I can't condone the use of Vista7 in any context, so I don't run it. But back to the problem here, I have cleared the cache, again, no luck.  The problem rendering seems to be with Firefox 91.8.0esr-1 for Debian/Devuan om amd64 and maybe other versions of Firefox.  Strangely, if I fetch the page using wget 1.21.3-1+b1 or curl 7.82.0-2 and then open the resulting file with Firefox, it renders as it should.  Otherwise, lynx 2.9.0dev.10-1, Chromium 101.0.4951.41-2, and Brave 1.38.109 (all on amd64) all render the page correctly.  Just Firefox is the exception.  So maybe that narrows the possibilities? -- Larsnooden (discuss • contribs) 04:03, 1 May 2022 (UTC)
 * I saved the page via Firefox and did a diff with files saved via the other web clients. There are a lot of differences so it seems that Firefox is getting served a very different page than the others, contrary to that which is expected.  I haven't drilled down into all the deviations, but the second line differs in that Firefox gets the vector-sticky-header-enabled class, the others don't.  -- Larsnooden (discuss • contribs) 07:09, 1 May 2022 (UTC)


 * Pretty curious. Just tested those pages on Android using Firefox and Chrome, and they render correctly. So none of my devices or browsers have this problem.
 * So it's not a wikitext coding problem on the pages in question anyway, but could be some kind of bug going on, but whether it is client or server side is difficult to say.
 * Have you tried to w:WP:PURGE the pages in question using your problematic Firefox browser? If you are running the gadget LiveUTC clock, clicking on the clock time does this automatically.
 * Otherwise, it's possible the folks at w:WP:VPT might be able shed more light on this. -- Jules (Mrjulesd) 08:19, 1 May 2022 (UTC)
 * It seems tied somehow to Firefox (in this case 91.9.0esr-1) because Chromium and its derivative, Brave, render the table of contents in the correct location. Like mentioned above, maybe the server is delivering very different content to each type of browser.  Though a cursory attempt at using a user-agent switching plug-in seemed to make no difference.  --  Larsnooden (discuss • contribs) 18:29, 21 May 2022 (UTC)
 * Any suggestions on solutions or work-arounds? The problem is still present in Firefox.  The problem is not present in Curl, Wget, Lynx, Dillo, TBB, Chromium, or Brave.  I don't have too many other browsers to test aside from those.  It is interesting that Curl and Wget can fetch a page which can be rendered properly by Firefox.  So, again, it looks like the site might be serving broken material to Firefox and only Firefox.  -- Larsnooden (discuss • contribs) 03:28, 4 June 2022 (UTC)
 * have you tried w:WP:VPT? I don't think anyone here knows of a worakaound, but there are a lot of clever users there that might be able to help. -- Jules (Mrjulesd) 21:46, 4 June 2022 (UTC)

Proposal on how to keep the Authors and Contributors page of every book that has one up to date
Hi everyone, I have done quite a lot of editing in incubator.wikimedia (before Middle English Wikipedia was deleted), and there there’s a button in every test wiki “check test wiki activity”. It works based on the prefix of the test wiki, but it can also be used to inspect prefixes in other WMF wikis including Wikibooks. I have used it to update Minecraft resource gathering/Authors & Contributors (see special:MobileDiff/4071172). A more experienced user can implement a bot to do this task automatically (btw I’m interested in learning how wiki bots work). Here’s the tool. You can type the name of your book. - 🇺🇦 Слава🇺🇦Україні 🇺🇦 Героям🇺🇦Слава🇺🇦 (talk)🇺🇦 10:31, 6 June 2022 (UTC)

Desktop Improvements update
Hello. I wanted to give you an update about the Desktop Improvements project, which the Wikimedia Foundation Web team has been working on for the past few years. Our work is almost finished! 🎉
 * Making this the new default

We would love to see these improvements become the default for readers and editors across all wikis. In the coming weeks, we will begin conversations on more wikis, including yours. 🗓️ We will gladly read your suggestions!

The goals of the project are to make the interface more welcoming and comfortable for readers and useful for advanced users. The project consists of a series of feature improvements which make it easier to read and learn, navigate within the page, search, switch between languages, use article tabs and the user menu, and more. The improvements are already visible by default for readers and editors on more than 30 wikis, including Wikipedias in French, Portuguese, and Persian.

The changes apply to the [ Vector] skin only, although it will always be possible to revert to the previous version on an individual basis. [ Monobook] or [ Timeless] users will not notice any changes.


 * The newest features
 * Table of contents - our version is easier to reach, gain context of the page, and navigate throughout the page without needing to scroll. It is currently tested across our pilot wikis. It is also available for editors who have opted into the Vector 2022 skin.
 * Page tools - now, there are two types of links in the sidebar. There are actions and tools for individual pages (like Related changes) and links of the wiki-wide nature (like Recent changes). We are going to separate these into two intuitive menus.
 * How to enable/disable the improvements
 * It is possible to opt-in individually in the appearance tab within the preferences by selecting "". Also, it is possible to opt-in on all wikis using the global preferences.
 * On wikis where the changes are visible by default for all, logged-in users can always opt-out to the Legacy Vector. There is an easily accessible link in the sidebar of the new Vector.


 * Learn more and join our events

If you would like to follow the progress of our project, you can subscribe to our newsletter. You can read the pages of the project, check our FAQ, write on the project talk page, and join an online meeting with us.

Thank you! SGrabarczuk (WMF) (talk) 16:59, 21 June 2022 (UTC)

Giancoli Physics
I am working on a physics textbook based on Giancoli Physics Principles with applications WalkingRadiance (discuss • contribs) 20:05, 26 June 2022 (UTC)


 * I have a draft at Physics Principles with Applications.
 * I have requested express copyright permission from Douglas Giancoli WalkingRadiance (discuss • contribs) 20:06, 26 June 2022 (UTC)