Page MenuHomePhabricator

Invert "limited-width" setting to be a "full-width" setting
Open, LowPublic

Description

Description

The default experience for Vector 2022 is a limited article width. Therefore I don't think there should be a setting called "Enable limited width mode" (as there is currently). Rather there should be a setting called "Enable full-width mode", which should be off by default.

CurrentUpdated
Screen Shot 2023-01-16 at 2.20.06 PM.png (749×1 px, 325 KB)
Screen Shot 2023-01-16 at 2.20.55 PM.png (749×1 px, 324 KB)

Event Timeline

@alexhollender technically this would be a pretty disruptive change, as if we invert it, everyone's preferences no longer will work. To counter that we'd need to run some migration script (which don't always work as we found out when we split Vector into two skins). We generally make preferences recommendations (see also Enable page previews and Enable responsive mode) so inverting this might confuse people to think they need to tick the box to get the recommended features. Could you elaborate on the problem we want to solve here, and perhaps I can suggest other more lightweight solutions.

If we go with the risky disruptive change, Is this worth the time investment?

PS. I'm also a bit worried about terminology- Edward was confused whether "limited width" was the same as "max width" - can we align on what we call this?

@Jdlrobson I defer to @ovasileva regarding the importance of this change, and how much work is worth putting into it.
In case it wasn't clear, my thinking was just that: optional preferences are off by default, and then turning one on should modify the default experience (like the preference right above, "Enable responsive mode"). But perhaps that's overthinking it...maybe it's fine for some preferences to be on by default.

ovasileva triaged this task as Medium priority.Jan 27 2023, 4:31 PM
ovasileva moved this task from Not ready to estimate to Groomed on the Web-Team-Backlog board.

@Jdlrobson I defer to @ovasileva regarding the importance of this change, and how much work is worth putting into it.
In case it wasn't clear, my thinking was just that: optional preferences are off by default, and then turning one on should modify the default experience (like the preference right above, "Enable responsive mode"). But perhaps that's overthinking it...maybe it's fine for some preferences to be on by default.

Yeah, I also feel like "enable" makes it sound like something different than the default, which could be confusing. Wouldn't say it's urgent though, maybe something we can consider for the future

@Jdlrobson I defer to @ovasileva regarding the importance of this change, and how much work is worth putting into it.
In case it wasn't clear, my thinking was just that: optional preferences are off by default, and then turning one on should modify the default experience (like the preference right above, "Enable responsive mode"). But perhaps that's overthinking it...maybe it's fine for some preferences to be on by default.

Right, but for the majority of our preferences we tick them by default - page previews, responsive and limited width are web preferences and all ticked/enabled by default. I think if we change one we should change all of them to be consistent. This is what the default state looks like:

Screen Shot 2023-01-27 at 9.59.55 AM.png (716×1 px, 181 KB)

So I think if we're changing this one we need to think more holistically and change others too.

What if we dropped the word "enable" or reworded them?

Jdlrobson lowered the priority of this task from Medium to Low.Apr 11 2023, 6:01 PM
Jdlrobson removed a project: Web-Team-Backlog.

Per grooming meeting not a priority right now.