This task is IE-related, and IE is no longer supported. You can close this as invalid. Oh, and I don't have an Edge in my computer.

Not just archived discussions, the "[reply]" button also appears in old revisions of discussion venues and talk pages. I'll provide links if necessary.

Somehow, the search icon of the sticky header is working right now. I don't know how, but.... Ah well. I'll reopen if this reoccurs.

Maybe anyone can adjust any browser's window size, e.g. Chrome's, to better reproduce the issue?

When will this be deployed? I still see the issue as of date.

@Aklapper I used the safemode in both Chrome, Safari and Firefox. As I'm afraid, it's also happening there, even on macOS Big Sur. I even tried using the developer tool (F12), aka "Inspect" via right-click toggle menu on Google Chrome. Somehow, the sticky header doesn't appear while using the tool.

No longer limited to Google Chrome. The problem also extends to Apple Safari, but I'm unsure whether the patch can work also for Safari. My Safari version is 15.3.

This file (https://en.wikipedia.org/wiki/File:Bend_Me,_Shape_Me_-_The_American_Breed.jpg) wasn't appearing in categories as well, so I had to re-edit the source page to redo its categorization.

When will the patch be deployed? The old player still hasn't appeared yet on Chrome mobile.

Strangely, the old player still works on Safari mobile.

Right now the old/legacy media player is not appearing on Mobile View via Chrome mobile 97.0.4692.98 on a Samsung Galaxy phone.

no longer using Koboton per T269522#7269221

Now that Kobiton is no longer used, I think the task description needs an update. Also, what about remaining tasks related to Kobiton?

Per T266866, the support for Firefox 10-14 has been dropped. Declining this task is long overdue.

Per MusikAnimal, maybe there are other ways besides pop-up feature to expose temporarily watched pages. I guess relying a lot on Notifications isn't a good idea. Meanwhile, I realize that this task would be reincarnated into a smaller or better written task, so I'm closing the task I created as "declined" for now.

In other words, going to Special:EditWatchlist is adequate enough? If so, then a user would have to very frequently watch over the list many, many times, right?

Hi, where exactly? Which page are we talking about? Any, like using the Notifications system?

Using Firefox 84.0.1 (latest to this date), I am able to reproduce method A:

1. Go to "Editing" section of user settings
2. De-check "Temporarily disable the visual editor while it is in beta" option if checkmarked
3. Select "Show me both editor tabs" in the Editing mode menu
4. Go to "Beta features" tab and checkmark/enable "New wikitext mode"
5. Click "Save" button
6. Go to https://www.mediawiki.org/wiki/Extension:Graph/Demo/IndexChart
7. Click the "≡" (triple bar) icon on the upper-right corner of Firefox
8. Open "Inspector" from "Web developer" sub-menu
9. Click the "Edit source" tab of the page
10. The source editor loads well
11. Then click "Edit" (to open VisualEditor)
12. Somehow, the chart doesn't appear, and NWE's toolbar appears in the VisualEditor
13. In Inspector, you'll see the following pink message: Uncaught TypeError: spec.data[0].values is undefined and load.php:753:885

the least I have done was clicking "older 50" and then click "newer 50" instead of clicking "back" button on a browser. That's how I was able to see newer contributions more effectively, though this method is annoying.

The action=watch url is more convenient than the other (editing source) method honestly. However, I have to go from page to page to implement the time expiry change on every individual article, which annoys me more.

Just in case: https://www.mediawiki.org/wiki/Topic:Vtjrwacu2jqn4rzq

Have you considered stalling this task? Do default Android browsers and IE11 share the same codes that other browsers (mobile and/or desktop) do?

@Krinkle In response to a table chart on T178356#6632565, Microsoft said the support for Edge on Windows 7 will end on at least July 2021:

We will continue to support Microsoft Edge on Windows 7 and Windows Server 2008 R2 until July 15, 2021. These operating systems are out of support and Microsoft recommends you move to a supported operating system such as Windows 10.

Previously, Google planned to end support for Windows 7 on that same period. Thankfully, it's been extended to January 2022.

How many more use cases, like past project closure proposals here?

In T233322#6660536, @kerberizer wrote:

That's also an option, indeed. Though, to be honest, I probably prefer simply hiding the content—if possible, of course. But maybe we could do both, too.

By the way, can you ask for temp adminship and then delete the problematic content? I'll give more list if necessary. Here you go…

Almost forgot: no transfer to any other project unless a project will clean up and revdel content as promised

I discussed this onwiki with LangCom (diff). The LangCom seems reluctant to delete the wiki at this time. The stewards couldn't do much about the articles copying other sources. I'm almost out of options. I hate to see the task closed (or indefinitely stalled), but I guess I can't persuade them any longer.

To note, iOS 12 still receives updates--just security ones--like the latest update released this month, for devices running iOS 12 but could not update to latest iOS version.

The current Android version of Nexus 7 is 6.0.1 (Marshmallow). Shall the task description be updated to reflect that?

Shall this task be reopened, or must I create a new task? I didn't think until moments ago that this task has existed. I still don't know why it's marked "Resolved" while this issue with the workboards on mobile devices still persists.

@Aklapper If you're looking for steps while using an iPad:

By the way, I don't know what steps I can reproduce the issue. I tried Safari's developer tools connecting a MacBook and an iPad via a USB-A cable, but the tools run slowly and are complicated for me to use. I don't know whether Chrome's devtools can connect to an iPad or another tablet.

I'm using iPadOS 14.1, and here are what I captured from Safari (iPadOS):

Splitting into separate tasks: T266122, T266132, T266142

I was able to change the punctuation settings from curvy apostrophe to straighter one (') on the iPad. Indeed, I learned from both sources (this one and that one) that I can go to the Settings app on an iPad. Then I should go to the General menu, press "Keyboards" and then disable "Smart punctuations" option. Speaking of which, the quotation mark became straighter again (").