This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
This article is within the scope of WikiProject Microsoft, a collaborative effort to improve the coverage of articles relating to Microsoft on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.MicrosoftWikipedia:WikiProject MicrosoftTemplate:WikiProject MicrosoftMicrosoft articles
This article is within the scope of WikiProject Microsoft Windows, a collaborative effort to improve the coverage of Microsoft Windows on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.Microsoft WindowsWikipedia:WikiProject Microsoft WindowsTemplate:WikiProject Microsoft WindowsMicrosoft Windows articles
This article links to one or more target anchors that no longer exist.
[[Windows 11 version history#Version 21H2 (original release)|original release of Windows 11]] The anchor (#Version 21H2 (original release)) is no longer available because it was deleted by a user before.
Please help fix the broken anchors. You can remove this template after fixing the problems. | Reporting errors
This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.
The reason for this request has something to do with the article's size. I C this being applied to similar pages including windows 11 version history. In any case, there won't be any visual changes, just for the sake of decreasing the size of the page. Here are the changes:
Replace <br/> and <br /> tags, wherever appearing, with <br> tags (removing spaces and slashes).
Replace scope="col" parameters, wherever appearing, with scope=col (omitting quotation marks).
Delete spaces before or after double equal signs (==) or triple equal signs (===) wherever appearing.
When I tested the changes in the WP:SANDBOX there were a total of 806 bytes removed (eight hundred and six). Moreover, when other users add patches to the end of tables, they would copy the last patch added above them, including the <br /> tags, before making modifications. Using <br> tags has four bytes, whereas <br /> has six bytes. If my request for changes gets discarded again then the size of the page will continue to increase greatly over time with the excessive use of unwanted spaces and quotation marks.197.238.159.62 (talk) 06:30, 18 May 2023 (UTC)Reply[reply]
Wikimedia hosts a lots of severs.... as you know. If such small spaces become huge burden, oh, their reports on finical should be carefully reviewed. -Lemonaka 12:06, 18 May 2023 (UTC)Reply[reply]
It seems that U users don't seem to understand my points. I had to explain in details. The page gets updated twice every month, with the six-byte tag, <br />, being copied and pasted at one line after the other. If we have 2 six-byte tags added in one month then we have 12 bytes added. On the other hand, if we have 2 four-byte tags, <br>, added in one month then we have 8 bytes added. Thus, preventing the article to grow darn quickly in the future. How hard is this to understand? They have nothing to do with such irrelevant and invalid info about how wikimedia's servers operate.197.238.159.62 (talk)
callmemirela, I clearly do understand that whichever method works. However, do U editors care about the size of this page? If U scroll to the top of this talk page U would realize the page was previously considered for deletion by georgia guy back in June 2018 due to the rapid growth of the article, in which nosebagbear and samboy suggested that the article be split, which eventually did happen.
The other problem is the amount of extra spaces and punctuations, which is the whole point of my doggone request, have been overused from time to time. A former editor, theTwoEyedMan, was the only user who came up with solutions to decrease the page size. Here ®️ some of its contributions to the article:
The above changes cleared over two kilobytes that time without even making any single visual change.197.244.236.124 (talk)
Please stop removing spaces on the talk page. Consensus right now, from users engaging into the conversation, is based on MOS, spaces are naturally to be included. There is no valid reason or policy to obsess over the size of the article. Additionally, please read WP:CANVASS; it is not a method to get your way. Callmemirela 🍁 19:59, 20 May 2023 (UTC)Reply[reply]
Then please stop going against multiple consensus which have been reached multiple times. We cannot change the structure of the article secretly without starting another consensus. I understand that when a consensus is reached, those rules have to be observed indefinitely, unless there's another consensus which would attempt to reverse the previous consensus. Also, I am not WP:CANVASSing.197.244.236.124 (talk) 20:49, 20 May 2023 (UTC)Reply[reply]
This diff says otherwise. Consensus with this thread is that the current MOS remains, per three editors. Structure is not being changed secretly; I have no idea what tangent you're on with this. The discussion is open to the public. Furthermore, consensus is not set in stone. Callmemirela 🍁 21:30, 20 May 2023 (UTC)Reply[reply]
Seriously? The structure is not being changed secretly U typed? If U ®️n't kidding me, then please explain how did those <br> tags were restored back to the original <br /> tags and how those deleted spaces before or after double or triple equal signs got added back. What I also understand is that WP:VEing does not allow an editor to change the code of WP:TEMPLATEs, WP:TAGs, WP:WIKITABLEs and etc. the user wishes to add, which is one of the reasons I prefer source editing instead.197.238.245.211 (talk) 22:01, 20 May 2023 (UTC)Reply[reply]
Excuse me? Please go through and consider my relevant points before alleging the fact that I am editing with bad faith.197.238.245.211 (talk) 23:44, 20 May 2023 (UTC)Reply[reply]
|-valign=top
|style=background:#fef8c6|10.0.19044.3208<br /><ref name="1904x3208">((cite web|url=https://support.microsoft.com/help/5028166|title=July 11, 2023—KB5028166 (OS Builds 19044.3208 and 19045.3208)|website=Microsoft Support|publisher=[[Microsoft]]|access-date=July 12, 2023))</ref>
|KB5028166
|'''Release Preview Channel and public release:'''<br />July 11, 2023
|
The user should have added what editions are eligible to receive that patch. In this case, it is more relevant to have the above lines changed to the below lines:
|-valign=top
|style=background:#fef8c6|10.0.19044.3208<br><ref name="1904x3208">((cite web|url=https://support.microsoft.com/help/5028166|title=July 11, 2023—KB5028166 (OS Builds 19044.3208 and 19045.3208)|website=Microsoft Support|publisher=[[Microsoft]]|access-date=July 12, 2023))</ref>
|KB5028166
|'''Release Preview Channel and public release:'''<br>July 11, 2023
|''This update is available for Education, Enterprise, IoT Enterprise, Enterprise LTSC and IoT Enterprise LTSC only.''
Because, according to the website attached above, the Home edition and respective Pro editions of 21H2 are no longer supported after 13 of June, 2023. Beginning July 2023, patches are available for all other editions I mentioned inside the above quote.
Also, in this revision, the user added the below lines:
|style=background:#d4f4b4|'''10.0.19044.3208'''<br />((r|1904x3208))
|KB5028166
|'''Release Preview Channel and public release:'''<br />July 11, 2023
which have to be replaced with the below lines:
|style=background:#d4f4b4|'''10.0.19045.3208'''<br>((r|1904x3208))
|KB5028166
|'''Release Preview Channel and public release:'''<br>July 11, 2023
because 22H2 does not have the 10.0.19044 build no., that's for 21H2 instead. Its build no. is actually 10.0.19045.
No mention of the major design changes which occurred between versions of Windows 10[edit]
I visited this page because I wished to known what versions of Windows 10 added the background blur effect, fluent design, OOBE and layout changes, etc. I was unable to find any mention of those things here. -A Fluffy Kitteh | FluffyKittehz User Profile Page 16:46, 31 October 2023 (UTC)Reply[reply]
You are welcome to add them if you find a reliable source. Jtrevor99 (talk) 19:06, 31 October 2023 (UTC)Reply[reply]