In T246419#6003142, @Niedzielski wrote:

@ovasileva, did we say that this work does not include touching content widths? (Sorry, I can't remember!) Would you mind updating the task description with the specifics as you see them?

In T248421#6002641, @dchen wrote:

@ovasileva
@phuedx
Is it possible to show this to just account/IP users who make edit(s)? If not, go ahead and show to everyone. Thanks!

Declined based on conversation above. For now, we will proceed without a feature branch, with extra care for minimizing risk such as additional review and QA.

Moving to editing QA and untagging Readers Web - feel free to add again if there's anything else we can do to help here

Checked on Chrome and Opera, seems to be Firefox only.

@JTannerWMF - review is done. Should we send this back to the Editing team for QA?

Report now published: https://www.mediawiki.org/wiki/Reading/Web/Desktop_Improvements/First_Prototype_Feedback_Report

Looks good!

@Tacsipacsi - We are currently slowing down our deployments over the next couple of weeks. As a result, we'll be pausing the work here for now. In the meantime, we would like answer some of the questions outlined above - in particular, we want to get an idea of the effects this change would have on moderation as well as solidify the designs. I will update this task once we have more info on this.

Moving this to blocked for now, see my comment in T211006: Add red link experience to empty search results on Minerva (JS version)

This seems risky to continue with right now. Let's discuss in standup.

In T247703#5971175, @Tnegrin wrote:

James says there's a tentative majority on this thread:
https://en.wikipedia.org/wiki/Wikipedia_talk:In_the_news#Crazy_idea%3A_dedicating_a_section_of_the_Main_Page_to_coronavirus_news
Can we geolocate content on this page? We have COVID19 articles in almost every language. @ovasileva -- can you please talk to your team and see what the options are?

In T247537#5966208, @Niedzielski wrote:

Quick status update: this fix is ready to go but is blocked on further technical refactor discussion. As I understand it, there are a few options:

• Merge the fix as it is. This maintains the status quo and eliminates the regression. This approach neither incurs nor eliminates technical debt.

+1 on this

In T247146#5962575, @Edtadros wrote:

@ovasileva I only tested IE11. This does not occur on the recent versions of Safari(Version 13.0.5 (15608.5.11)), Chrome (Version 80.0.3987.132), Edge(Version 80.0.361.57 ).

Looks good, thanks @Edtadros. Could see the more dropdown & you are correct, edit does not appear on the main page

In T245734#5957705, @Demian wrote:

In T245734#5949089, @alexhollender wrote:

[The TOC] I don't think we need to discuss it further as part of this task (though I totally understand why you brought it up here). Please lookout for discussions specifically regarding the TOC in the upcoming months, or I will try to remember to ping you once those tasks/explorations get created.

Thank you! It seemed reasonable to discuss the TOC before the sidebar where I believe it would be best placed. I'll follow up on further discussions. Note: the information circulating between developers about these plans (timeline, what will be done) is not available to us volunteers, so I'm sorry in advance for starting misplaced / mistimed discussions ;-)

Putting in triaged but future until work on the sidebar is completed.

Thanks @Edtadros - also asked this on the bugs themselves but just to be sure - these are only showing on old desktop browsers, right? Priority would probably increase if it was both desktop & mobile.

@Edtadros - to confirm, this is only happening on older desktop browsers?

Decided to go the epic route