TLS 1.3 is not as big of a issue for Android as with iOS. Chrome 71 and Firefox 68 (both released 5 years ago) are compatible with Android 4.1 and above. These browsers support TLS 1.3.
Android 4.1 is 12 years old. However, iOS Safari 10-11, which are 7-8 years old, don't support TLS 1.3. Apple only managed to implement TLS 1.3 in iOS Safari 12.2, which is six years old.

I mentioned that CSS Grid Layout and #rrggbbaa/#rgba hex notation need this version bump. Both are very useful.

Usually better to use our own stats.

I clarified that TLS 1.3 supports Safari macOS 12.1+ (on macOS Mojave and later) and Safari iOS 12.2+.

Let's give a update to market share:

• Chrome 49: 0.02%
• Chrome 50: 0.01%
• Chrome 53: 0.01%
• Chrome 56: 0.02%
• Chrome 66: 0.02%
• Chrome 69: 0.08%
• Firefox 52: 0.04%
• Firefox 56: 0.01%
• Safari 12.1: 0.01%
• Safari 13.1: 0.06%
• Safari iOS 10.2: 0.01%
• Safari iOS 10.3: 0.04%
• Safari iOS 11.2: 0.16%
• Safari iOS 11.4: 0.01%
• Safari iOS 12.1: 0.01%

TLS 1.3 is also available in Safari 12.1 and later. Full support in macOS Mojave and later, and iOS.

I agree it would be ideal to move to a rolling window like Grade A for simplicity, but in practice Grade C is meant to capture a much wider net of readers which doesn't always correspond to a specific timeframe. Like I suggested in T380344#10349484, if there's no specific product/feature that needs this version bump we should probably wait to see how T367821 develops because it might make 7 years not even applicable.

Additionally, MediaWiki would feature new CSS features as time progresses.

Timeframe is useful as market share for older versions of browsers drop as time progress.

Why 7 years and not 6 or 8? Why introduce a timeframe?

#rrggbbaa hex color notation is very useful as it is easier to create translucent colors which having to resort to rgba(). Let's say if you want to create green color with 60% opacity, you only need to type #00800099 instead of rgba(0, 128, 0, 0.6). It uses nine bytes instead of 20, so it can use less data. Additionally #RGBA is even smaller, at only 5 bytes.

Here are the new HTML/CSS properties when going from Chrome 49/Safari 10/Firefox 49 to last 7 years' versions.

The v6 module loads the CodeMirror lib (ext.CodeMirror.v6.lib) at the same time as the visualeditor module. In v5, it is loaded after VE and the toolbar have loaded. I'm fairly sure that's the problem. It may have something to do with the fact that ext.CodeMirror.v6 needs the library upfront, while ext.CodeMirror does not. Simply adjusting extension.json (adding ext.CodeMirror.v6.lib as a dependency, etc.) and even adding some mw.loader.using() blocks doesn't seem to reliably fix the issue.

Tried Narrator on Microsoft Edge (Chromium) 109 on Windows 7. Somehow, it doesn't read Edge's web content, apparently. Nonetheless, at least Chromium Edge has its own Immersive Reader, which reads content aloud.

Almost forgot: I read some thread about Microsoft Narrator being incompatible with Google Chrome but works well with Chromium(?) Edge. And the thread is early this year, NOT years ago. As I can assume, this is concerning Windows 10 or 11.

I can confirm in Firefox 131.0 and I cannot reproduce in Chromium (which is also smart to linebreak between . and <).

September 2024 report from pl.wikipedia - need to confirm about:config settings of the reporter

Sorry to have bothered you:
it wasn't any of the extensions but clearing the cookies helped.

Firefox does load VE for me, so it's presumably something specific to your environment.

Which Firefox version do you use? You may want to disable some browser addons like AdBlock Plus or Greasemonkey in order to test the bug.

Firefox supports break-inside: avoid; since January 2020 (just one month before this ticket was created) and break-inside: avoid-column; since September 2021 (i.e. at a later time). See compatibility table.

Change #268316 abandoned by Jforrester:

[VisualEditor/VisualEditor@master] IME tests: Add failing Korean IME test

https://gerrit.wikimedia.org/r/268316

LGTM

This ticket documents the behaviour exactly as we implemented so not a bug.

The first two things are intentional changes, for the third item see all the questions in my previous comment

I think you might need to check your stats based on UserAgent (if that is possible). You might need to check with tool and bot authors which might be using outdated software. This is important because a single connection once a day by some tool might be used by thousands of users.

Not, it's just automatic. Sorry about that. No need to announce.